From owner-urn-ietf@LISTS.NETSOL.COM Wed May 9 10:40:28 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09180 for ; Wed, 9 May 2001 10:40:27 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id KAA25969; Wed, 9 May 2001 10:27:18 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 13353 for URN-IETF@LISTS.NETSOL.COM; Wed, 9 May 2001 10:26:43 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id JAA25748 for ; Wed, 9 May 2001 09:38:26 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06242; Wed, 9 May 2001 09:32:29 -0400 (EDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Message-ID: <200105091332.JAA06242@ietf.org> Date: Wed, 9 May 2001 09:32:29 -0400 Reply-To: Internet-Drafts@ietf.org Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-urn-rfc2611bis-03.txt To: URN-IETF@LISTS.NETSOL.COM --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names Working Group of the IETF. Title : URN Namespace Definition Mechanisms Author(s) : L. Daigle, D. van Gulik, R. Iannella, P. Faltstrom Filename : draft-ietf-urn-rfc2611bis-03.txt Pages : 18 Date : 08-May-01 The URN WG has defined a syntax for Uniform Resource Names (URNs) [RFC2141], as well as some proposed mechanisms for their resolution and use in Internet applications ([RFCXXXX], [RFCYYYY]). The whole rests on the concept of individual 'namespaces' within the URN structure. Apart from proof-of-concept namespaces, the use of existing identifiers in URNs has been discussed ([RFC2288]), and this document lays out general definitions of and mechanisms for establishing URN 'namespaces'. This document obsoletes RFC2611. Discussion of this document should be directed to urn-ietf@ietf.org A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-urn-rfc2611bis-03.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-urn-rfc2611bis-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-urn-rfc2611bis-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20010508152347.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-urn-rfc2611bis-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-urn-rfc2611bis-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010508152347.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-urn-ietf@LISTS.NETSOL.COM Wed May 9 11:40:26 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12653 for ; Wed, 9 May 2001 11:40:26 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA26545; Wed, 9 May 2001 11:28:04 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 13448 for URN-IETF@LISTS.NETSOL.COM; Wed, 9 May 2001 11:27:45 -0400 Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA26538 for ; Wed, 9 May 2001 11:27:43 -0400 (EDT) Received: from thinkingcat.com ([64.229.196.65]) by tomts13-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010509152123.NUAT25498.tomts13-srv.bellnexxia.net@thinkingcat.com>; Wed, 9 May 2001 11:21:23 -0400 X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 References: <200105091332.JAA06242@ietf.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Approved-By: Leslie Daigle Message-ID: <3AF95FC4.D36E6473@thinkingcat.com> Date: Wed, 9 May 2001 11:18:28 -0400 Reply-To: Leslie Daigle From: Leslie Daigle Organization: Thinking Cat Enterprises Subject: URN WG ready to publish draft-ietf-urn-rfc2611bis-03.txt To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit Howdy, The URN WG has reviewed this document, and considers it completed. We would therefore like to ask the IESG to publish it as a BCP RFC, to replace/obsolete RFC2611 for URN NID definition process. There is one outstanding editorial issue. The URL for the IANA URN namespace registry uses the "isi.edu" domain. I know that IANA is trying to move everything to iana.org, but that doesn't work at the moment. I sent a message to IANA 2 weeks ago asking what they'd like me to put in there, but haven't had a response. I think we're better off not delaying this any furhter, and if IANA responds in the next while, we can fix that with a note to the RFC-editor, in the worst case. Thanks, Leslie. Internet-Drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Uniform Resource Names Working Group of the IETF. > > Title : URN Namespace Definition Mechanisms > Author(s) : L. Daigle, D. van Gulik, R. Iannella, P. Faltstrom > Filename : draft-ietf-urn-rfc2611bis-03.txt > Pages : 18 > Date : 08-May-01 > > The URN WG has defined a syntax for Uniform Resource Names (URNs) > [RFC2141], as well as some proposed mechanisms for their resolution > and use in Internet applications ([RFCXXXX], [RFCYYYY]). The whole > rests on the concept of individual 'namespaces' within the URN > structure. Apart from proof-of-concept namespaces, the use of > existing identifiers in URNs has been discussed ([RFC2288]), and this > document lays out general definitions of and mechanisms for > establishing URN 'namespaces'. > This document obsoletes RFC2611. > Discussion of this document should be directed to urn-ietf@ietf.org > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-urn-rfc2611bis-03.txt > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-urn-rfc2611bis-03.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-urn-rfc2611bis-03.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. -- ------------------------------------------------------------------- "The best laid plans are written in pencil." -- ThinkingCat Leslie Daigle leslie@thinkingcat.com ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Wed May 9 18:06:19 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26841 for ; Wed, 9 May 2001 18:06:19 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id RAA28522; Wed, 9 May 2001 17:54:04 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 13570 for URN-IETF@LISTS.NETSOL.COM; Wed, 9 May 2001 17:53:52 -0400 Received: from tomts6-srv.bellnexxia.net (tomts6.bellnexxia.net [209.226.175.26]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id RAA28515 for ; Wed, 9 May 2001 17:53:51 -0400 (EDT) Received: from thinkingcat.com ([64.229.196.65]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010509214731.VAQJ7009.tomts6-srv.bellnexxia.net@thinkingcat.com> for ; Wed, 9 May 2001 17:47:31 -0400 X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 References: <200105091332.JAA06242@ietf.org> <3AF95FC4.D36E6473@thinkingcat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Approved-By: Leslie Daigle Message-ID: <3AF9BA44.BFB8417E@thinkingcat.com> Date: Wed, 9 May 2001 17:44:36 -0400 Reply-To: Leslie Daigle From: Leslie Daigle Organization: Thinking Cat Enterprises Subject: Re: URN WG ready to publish draft-ietf-urn-rfc2611bis-03.txt To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit FYI -- this note was addressed to our area directors, and cc'ed to the working group. For those who don't know/forgot, the mailing list reflector strips off all other addresses and makes the mailing list the sole recipient. Which is helpful at keeping addressee lists down, but sometimes makes the context inscrutable. Leslie. Leslie Daigle wrote: > > Howdy, > > The URN WG has reviewed this document, and considers it completed. > We would therefore like to ask the IESG to publish it as a BCP RFC, > to replace/obsolete RFC2611 for URN NID definition process. > > There is one outstanding editorial issue. The URL for the IANA URN > namespace registry uses the "isi.edu" domain. I know that IANA > is trying to move everything to iana.org, but that doesn't > work at the moment. I sent a message to IANA 2 weeks ago asking > what they'd like me to put in there, but haven't had a response. > I think we're better off not delaying this any furhter, and if > IANA responds in the next while, we can fix that with a note to the > RFC-editor, in the worst case. > > Thanks, > Leslie. > > Internet-Drafts@ietf.org wrote: > > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > This draft is a work item of the Uniform Resource Names Working Group of the IETF. > > > > Title : URN Namespace Definition Mechanisms > > Author(s) : L. Daigle, D. van Gulik, R. Iannella, P. Faltstrom > > Filename : draft-ietf-urn-rfc2611bis-03.txt > > Pages : 18 > > Date : 08-May-01 > > > > The URN WG has defined a syntax for Uniform Resource Names (URNs) > > [RFC2141], as well as some proposed mechanisms for their resolution > > and use in Internet applications ([RFCXXXX], [RFCYYYY]). The whole > > rests on the concept of individual 'namespaces' within the URN > > structure. Apart from proof-of-concept namespaces, the use of > > existing identifiers in URNs has been discussed ([RFC2288]), and this > > document lays out general definitions of and mechanisms for > > establishing URN 'namespaces'. > > This document obsoletes RFC2611. > > Discussion of this document should be directed to urn-ietf@ietf.org > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-urn-rfc2611bis-03.txt > > > > Internet-Drafts are also available by anonymous FTP. Login with the username > > "anonymous" and a password of your e-mail address. After logging in, > > type "cd internet-drafts" and then > > "get draft-ietf-urn-rfc2611bis-03.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-urn-rfc2611bis-03.txt". > > > > NOTE: The mail server at ietf.org can return the document in > > MIME-encoded form by using the "mpack" utility. To use this > > feature, insert the command "ENCODING mime" before the "FILE" > > command. To decode the response(s), you will need "munpack" or > > a MIME-compliant mail reader. Different MIME-compliant mail readers > > exhibit different behavior, especially when dealing with > > "multipart" MIME messages (i.e. documents which have been split > > up into multiple messages), so check your local documentation on > > how to manipulate these messages. > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > -- > > ------------------------------------------------------------------- > "The best laid plans > are written in pencil." > -- ThinkingCat > > Leslie Daigle > leslie@thinkingcat.com > ------------------------------------------------------------------- -- ------------------------------------------------------------------- "The best laid plans are written in pencil." -- ThinkingCat Leslie Daigle leslie@thinkingcat.com ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Thu May 10 19:13:47 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA09828 for ; Thu, 10 May 2001 19:13:47 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id TAA06167; Thu, 10 May 2001 19:01:16 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 14110 for URN-IETF@LISTS.NETSOL.COM; Thu, 10 May 2001 19:00:50 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from cuimail.unige.ch (cuimail.unige.ch [129.194.69.50]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id SAA06003 for ; Thu, 10 May 2001 18:37:19 -0400 (EDT) Received: from cuimail.unige.ch ([129.194.69.17]) by cuimail.unige.ch (PMDF V6.0-24 #44959) with ESMTP id <0GD500E6X58GYT@cuimail.unige.ch> for urn-ietf@lists.netsol.com; Fri, 11 May 2001 00:31:28 +0200 (MET DST) X-URL: http://cui.unige.ch/eao/www/Bertrand.html X-Face: $LChH{%os*16AP:(5pI<*1fqtXx?14aOqKLUfv{>&:+,G6Y+ei9aTSM:D,ie2w=~vr9nsSj FY4bH+)|=<_V|1@4";>_aJ}QxqfL['1]O3i`)wmc]#,^4Ny#&_|k?EEcrb7aIle|fs742v:5WjNM9# ufe5itBNu-z*[']\@b|ut#z,r8b#ax^CsUUku2I#bgvZ&XxZ/kc#7Gi{5OB%h88yly"YZG*u}jD^tL wUfdV#%YU.|hU|HEOfSCGxb MIME-version: 1.0 X-Mailer: exmh version 2.0.2 2/24/98 Content-type: text/plain; charset=us-ascii Message-ID: <0GD500E6Y58GYT@cuimail.unige.ch> Date: Fri, 11 May 2001 00:31:28 +0200 Reply-To: Bertrand.Ibrahim@CUI.UNIGE.CH From: Bertrand.Ibrahim@CUI.UNIGE.CH Subject: Bad URL in draft-ietf-urn-rfc2611bis-03.txt To: URN-IETF@LISTS.NETSOL.COM In draft-ietf-urn-rfc2611bis-03.txt, section 4.0 (URN Namespace Registration, Update, and NID Assignment Process) refers the reader to ftp://ftp.isi.edu/in-notes/iana/assignments/URN-namespaces/ for the official list of registered URN namespaces maintained by IANA. The correct URL should be ftp://ftp.isi.edu/in-notes/iana/assignments/urn-namespaces That is, the should not be a '/' at the end and all letters should be lower case. In addition, the abstract (on page 1) mentions that discussion of this document should be directed to urn-ietf@ietf.org, which is a bogus address (urn-ietf@lists.netsol.com might be the correct one, since the draft announcement was CC-ed to that address). Hope this helps. Bertrand Ibrahim. -------------------------------------------- Bertrand.Ibrahim@cui.unige.ch http://cui.unige.ch/eao/www/Bertrand.html PGP 6.0 Public Key fingerprint: F286 F29D E459 F0DC 4E92 D9CB C408 77D0 0CFD 47A8 From owner-urn-ietf@LISTS.NETSOL.COM Thu May 24 15:53:34 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19941 for ; Thu, 24 May 2001 15:53:33 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id PAA07717; Thu, 24 May 2001 15:47:13 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 0030 for URN-IETF@LISTS.NETSOL.COM; Thu, 24 May 2001 15:46:32 -0400 Received: from imo-d03.mx.aol.com (imo-d03.mx.aol.com [205.188.157.35]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id PAA07707 for ; Thu, 24 May 2001 15:46:31 -0400 (EDT) Received: from HalMeyer3@cs.com by imo-d03.mx.aol.com (mail_out_v30.22.) id 4.e2.152cf5c6 (25513) for ; Thu, 24 May 2001 15:40:07 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: CompuServe 2000 32-bit sub 122 Approved-By: HalMeyer3@CS.COM Message-ID: Date: Thu, 24 May 2001 15:40:07 EDT Reply-To: HalMeyer3@cs.com From: Hal Meyer Subject: DOMAINS-L To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit FYI, there is a listserver for the domain industry called DOMAINS-L. Thought you all might be interested. Have a look here==> http://DOMAINS-L.com Best, Hal Meyer From owner-urn-ietf@LISTS.NETSOL.COM Tue May 29 05:15:16 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA27694 for ; Tue, 29 May 2001 05:15:15 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id FAA07199; Tue, 29 May 2001 05:09:16 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 0758 for URN-IETF@LISTS.NETSOL.COM; Tue, 29 May 2001 05:08:44 -0400 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id FAA07182; Tue, 29 May 2001 05:08:41 -0400 (EDT) Message-ID: <200105290908.FAA07182@lists.netsol.com> Date: Tue, 29 May 2001 05:08:41 -0400 Reply-To: Ron Bennett From: Ron Bennett Subject: VeriSign COVER UP - Read All About it INSIDE! To: URN-IETF@LISTS.NETSOL.COM Interesting how VeriSign leaves up the mailing list URN-IETF that's received a whole 19 posts in the past three months along with full member list and archives, and yet VeriSign deleted the most active list, Domain-Policy claiming it was no longer needed. And even worse, VeriSign did this with no warning and in the process they deleted its respective member list and archives. And yet this very *slow* list is still up and running as usual. Looks like a cover up to me...how about to you? Read the story of how VeriSign very rudely and unprofessionally removed all traces of the Domain-Policy list below... http://slashdot.org/article.pl?sid=01/05/25/0223221&mode=thread Like to read the archives of the Domain-Policy list...they're now available at the following URLs: http://www.wyomissing.com/bennett/domainpolicyarchives.zip http://www.valuenames.com/bennett/domainpolicyarchives.zip Even older archives may now be available at Tucows - http://www.tucows.com/ Thank you for taking time to read this...assuming anyone reads this list anymore :-; From owner-urn-ietf@LISTS.NETSOL.COM Tue May 29 11:24:57 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03461 for ; Tue, 29 May 2001 11:24:56 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA09241; Tue, 29 May 2001 11:20:14 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 0903 for URN-IETF@LISTS.NETSOL.COM; Tue, 29 May 2001 11:19:40 -0400 Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA09223 for ; Tue, 29 May 2001 11:19:39 -0400 (EDT) Received: from thinkingcat.com ([64.229.201.102]) by tomts13-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010529151319.ZYFB25498.tomts13-srv.bellnexxia.net@thinkingcat.com>; Tue, 29 May 2001 11:13:19 -0400 X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 References: <200105290908.FAA07182@lists.netsol.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Approved-By: Leslie Daigle Message-ID: <3B13BC81.E0D28EB4@thinkingcat.com> Date: Tue, 29 May 2001 11:13:05 -0400 Reply-To: Leslie Daigle From: Leslie Daigle Organization: Thinking Cat Enterprises Subject: Re: VeriSign COVER UP - Read All About it INSIDE! To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit Howdy, This is the official mailing list of the IETF URN working group. See http://www.ietf.org/html.charters/urn-charter.html Low traffic reflects the fact that the WG is almost done, winding up last documents and waiting on the IESG to process our documents. Postings not concerned with WG work items are off topic. Please take that as notice that your posting is off-topic, and don't pursue this here. Thanks, Leslie Daigle. IETF URN WG Co-Chair. Ron Bennett wrote: > > Interesting how VeriSign leaves up the mailing list URN-IETF that's received > a whole 19 posts in the past three months along with full member list and > archives, and yet VeriSign deleted the most active list, Domain-Policy > claiming it was no longer needed. And even worse, VeriSign did this with no > warning and in the process they deleted its respective member list and > archives. > > And yet this very *slow* list is still up and running as usual. Looks like a > cover up to me...how about to you? > > Read the story of how VeriSign very rudely and unprofessionally removed all > traces of the Domain-Policy list below... > > http://slashdot.org/article.pl?sid=01/05/25/0223221&mode=thread > > Like to read the archives of the Domain-Policy list...they're now available > at the following URLs: > > http://www.wyomissing.com/bennett/domainpolicyarchives.zip > > http://www.valuenames.com/bennett/domainpolicyarchives.zip > > Even older archives may now be available at Tucows - http://www.tucows.com/ > > Thank you for taking time to read this...assuming anyone reads this list > anymore :-; -- ------------------------------------------------------------------- "The best laid plans are written in pencil." -- ThinkingCat Leslie Daigle leslie@thinkingcat.com ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Wed May 30 09:00:15 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA09016 for ; Wed, 30 May 2001 09:00:14 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id IAA23413; Wed, 30 May 2001 08:54:27 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 1127 for URN-IETF@LISTS.NETSOL.COM; Wed, 30 May 2001 08:53:50 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id GAA15121 for ; Wed, 30 May 2001 06:54:04 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05019; Wed, 30 May 2001 06:47:55 -0400 (EDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Message-ID: <200105301047.GAA05019@ietf.org> Date: Wed, 30 May 2001 06:47:55 -0400 Reply-To: Internet-Drafts@ietf.org Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-urn-net-procedures-08.txt To: URN-IETF@LISTS.NETSOL.COM --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names Working Group of the IETF. Title : Assignment Procedures for the URI Resolution using DNS Author(s) : M. Mealling Filename : draft-ietf-urn-net-procedures-08.txt Pages : 10 Date : 29-May-01 RFCYYYY defines a how DNS is used as a DDDS database that contains URI delegation rules (sometimes called resolution hints). That document specifies that the first step in that algorithm is to append 'URI.ARPA' to the URI scheme and retrieve the NAPTR record for that domain-name. I.e., the first step in resolving 'http://foo.com/' would be to look up a NAPTR record for the domain 'http.URI.ARPA'. URN resolution also follows a similar procedure but uses the 'URN.ARPA' zone as its root. This document describes the procedures for inserting a new rule into the 'URI.ARPA' and 'URN.ARPA' zones. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-urn-net-procedures-08.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-urn-net-procedures-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-urn-net-procedures-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20010529142344.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-urn-net-procedures-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-urn-net-procedures-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010529142344.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-urn-ietf@LISTS.NETSOL.COM Wed May 30 09:02:09 2001 Received: from lists.netsol.com ([216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA09090 for ; Wed, 30 May 2001 09:02:08 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id IAA23523; Wed, 30 May 2001 08:57:09 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 1131 for URN-IETF@LISTS.NETSOL.COM; Wed, 30 May 2001 08:57:06 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id GAA15109 for ; Wed, 30 May 2001 06:53:58 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04992; Wed, 30 May 2001 06:47:50 -0400 (EDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Message-ID: <200105301047.GAA04992@ietf.org> Date: Wed, 30 May 2001 06:47:49 -0400 Reply-To: Internet-Drafts@ietf.org Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-urn-dns-ddds-database-05.txt To: URN-IETF@LISTS.NETSOL.COM --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names Working Group of the IETF. Title : A DDDS Database Using The Domain Name System Author(s) : M. Mealling Filename : draft-ietf-urn-dns-ddds-database-05.txt Pages : 20 Date : 29-May-01 This document describes a Dynamic Delegation Discovery System Database using the Domain Name System as a distributed database of Rules. The Keys are domain-names and the Rules are encoded using the NAPTR Resource Record. Since this document officially obsoletes RFC 2168, it is the official specification for the NAPTR DNS Resource Record. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-urn-dns-ddds-database-05.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-urn-dns-ddds-database-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-urn-dns-ddds-database-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20010529142333.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-urn-dns-ddds-database-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-urn-dns-ddds-database-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010529142333.I-D@ietf.org> --OtherAccess-- --NextPart--