From owner-urn-ietf@LISTS.NETSOL.COM Mon Apr 15 15:55:59 2002 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04876 for ; Mon, 15 Apr 2002 15:55:59 -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 PAA27402; Mon, 15 Apr 2002 15:50:44 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 35593 for URN-IETF@LISTS.NETSOL.COM; Mon, 15 Apr 2002 15:50:00 -0400 Received: from pwrm.com (h139-142-65-9.pml.com [139.142.65.9]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id PAA27381 for ; Mon, 15 Apr 2002 15:49:59 -0400 (EDT) Received: from HERMES.canada.corp.powermeasurement.com ([10.1.32.4]) by pwrm.com with Microsoft SMTPSVC(5.0.2195.3779); Mon, 15 Apr 2002 12:43:47 -0700 Received: by HERMES.canada.corp.powermeasurement.com with Internet Mail Service (5.5.2655.55) id <2YKKRT15>; Mon, 15 Apr 2002 12:43:11 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 15 Apr 2002 19:43:47.0829 (UTC) FILETIME=[DC3D1A50:01C1E4B5] Approved-By: Ryan Fransen Message-ID: <3C552E6ED5B7DC4F8BF603C030BB70BF28BCEF@HERMES.canada.corp.powermeasurement.com> Date: Mon, 15 Apr 2002 12:43:09 -0700 Reply-To: Ryan Fransen From: Ryan Fransen Subject: rfc2141 - URN syntax question To: URN-IETF@LISTS.NETSOL.COM Section 2.1 of rfc2141 states: ::= [ 1,31 ] I am wondering what is specifically meant by: [ 1,31 ] Would I be correct in saying: The NID can contain between 1 and 31 characters, with a hyphen anywhere except the first character? Any help in my confusion is appreciated. Thanks for your time, Ryan Fransen ryan.fransen@pwrm.com http://www.pwrm.com From owner-urn-ietf@LISTS.NETSOL.COM Wed Apr 17 17:44:18 2002 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08855 for ; Wed, 17 Apr 2002 17:44:18 -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 RAA10517; Wed, 17 Apr 2002 17:38:56 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 36172 for URN-IETF@LISTS.NETSOL.COM; Wed, 17 Apr 2002 17:37:13 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from webweaving.org (IDENT:Chuck@adsl-66-124-87-42.dsl.snfc21.pacbell.net [66.124.87.42]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id QAA10332 for ; Wed, 17 Apr 2002 16:52:20 -0400 (EDT) Received: from dirkx (helo=localhost) by webweaving.org with local-esmtp (Exim 3.14 #1) id 16xx0q-0001bM-00; Wed, 17 Apr 2002 21:30:48 +0000 X-Sender: dirkx@router.ispra.webweaving.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-ID: Date: Wed, 17 Apr 2002 21:30:48 +0000 Reply-To: Dirk-Willem van Gulik From: Dirk-Willem van Gulik Subject: Re: rfc2141 - URN syntax question To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <3C552E6ED5B7DC4F8BF603C030BB70BF28BCEF@HERMES.canada.corp.powermeasurement.com> On Mon, 15 Apr 2002, Ryan Fransen wrote: > Section 2.1 of rfc2141 states: > > ::= [ 1,31 ] > > I am wondering what is specifically meant by: [ 1,31 ] > > Would I be correct in saying: The NID can contain between 1 and 31 > characters, with a hyphen anywhere except the first character? After having some debugging fun with recognizing an IP address (most stacks take '10' as '10.0.0.0' or accept any 32 bit number) I'd love to change that at some point just to make an implementors live easier. 1-32 chars a-z 0-9 first char no '-' or digit. Dw. From owner-urn-ietf@LISTS.NETSOL.COM Fri Apr 26 14:24:12 2002 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21472 for ; Fri, 26 Apr 2002 14:24:11 -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 OAA04776; Fri, 26 Apr 2002 14:20:27 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 38587 for URN-IETF@LISTS.NETSOL.COM; Fri, 26 Apr 2002 14:19:26 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from smtp-relay-2.adobe.com (smtp-relay-2.adobe.com [192.150.11.2]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id OAA04699 for ; Fri, 26 Apr 2002 14:05:51 -0400 (EDT) Received: from inner-relay-2.corp.adobe.com (inner-relay-2 [153.32.1.52]) by smtp-relay-2.adobe.com (8.12.3/8.12.3) with ESMTP id g3QHvI6J011046 for ; Fri, 26 Apr 2002 10:57:18 -0700 (PDT) Received: from mailsj-v1.corp.adobe.com (mailsj-dev.corp.adobe.com [153.32.1.192]) by inner-relay-2.corp.adobe.com (8.12.3/8.12.3) with ESMTP id g3QHvPei026343 for ; Fri, 26 Apr 2002 10:57:25 -0700 (PDT) Received: from larrypad ([153.32.31.229]) by mailsj-v1.corp.adobe.com (Netscape Messaging Server 4.15 v1 Jul 11 2001 16:32:57) with ESMTP id GV6SMG00.LOE; Fri, 26 Apr 2002 10:59:04 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Message-ID: <001a01c1ed4b$f7c3a9d0$e51f2099@larrypad> Date: Fri, 26 Apr 2002 10:58:27 -0700 Reply-To: LMM@acm.org From: Larry Masinter Subject: FW: I-D ACTION:draft-masinter-dated-uri-03.txt To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit I hope I've addressed the comments I've gotten on this. If you said something and think I ignored you, please let me know, I might have lost some comments. I picked "uri@w3.org" as the main list to discuss this draft on for public comments. -----Original Message----- From: nsyracus@cnri.reston.va.us On Behalf Of Internet-Drafts@ietf.org Sent: Friday, April 26, 2002 5:14 AM To: IETF-Announce: Subject: I-D ACTION:draft-masinter-dated-uri-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : 'duri' and 'tdb': URN namespaces based on dated URIs Author(s) : L. Masinter Filename : draft-masinter-dated-uri-03.txt Pages : 20 Date : 25-Apr-02 This document defines two namespaces of URNs, based on using a timestamp with an (encoded) URI. The results are namespaces in which names are readily assigned, offer the persistence of reference that is required by URNs, but do not require a stable authority to assign the name. The first namespace ('duri') is used to refer to URI- identified resources as they appeared at a particular time. The second namespace ('tdb') is useful as a way of creating URNs that refer to physical objects or even abstractions that are not themselves networked resources. The definition of these namespaces may reduce the need to define new URN namespaces merely for the purpose of creating stable identifiers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-masinter-dated-uri-03.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-masinter-dated-uri-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-masinter-dated-uri-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.