From owner-urn-ietf@Bunyip.Com  Thu Apr  1 08:14:36 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20978
	for <urn-archive@ietf.org>; Thu, 1 Apr 1999 08:14:35 -0500 (EST)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id HAA17135
	for urn-ietf-out; Thu, 1 Apr 1999 07:21:04 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id HAA17130
	for <urn-ietf@services.bunyip.com>; Thu, 1 Apr 1999 07:21:02 -0500 (EST)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id HAA22830
	for urn-ietf@services; Thu, 1 Apr 1999 07:21:01 -0500 (EST)
Received: from buzz.Bunyip.Com (buzz.Bunyip.Com [209.41.144.8])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id HAA22827;
	Thu, 1 Apr 1999 07:20:58 -0500 (EST)
Received: from localhost (leslie@localhost) by buzz.Bunyip.Com (8.6.9/8.6.10) with SMTP id HAA17802; Thu, 1 Apr 1999 07:20:58 -0500
X-Authentication-Warning: buzz.Bunyip.Com: leslie owned process doing -bs
Date: Thu, 1 Apr 1999 07:20:57 -0500 (EST)
From: Leslie Daigle <leslie@Bunyip.Com>
To: "Aaron E. Walsh" <aaron@mantiscorp.com>
cc: urn-ietf@Bunyip.Com
Subject: Re: [URN] status
In-Reply-To: <3702B7AB.C8C0DAAB@mantiscorp.com>
Message-ID: <Pine.SUN.3.95.990401071901.17797A-100000@buzz.Bunyip.Com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Leslie Daigle <leslie@Bunyip.Com>
Errors-To: owner-urn-ietf@Bunyip.Com

Howdy,

On Wed, 31 Mar 1999, Aaron E. Walsh wrote:
> I'm preparing now to register a few URN namespaces, and wonder if you or
> others could point me towards the proper documents to file? I understand
> this isn't as simple a process as simply submitting an online form, as
> we do for domains through InterNic, so want to make sure I'm heading in
> the right direction :)

The procedure is outlined in 

	draft-ietf-urn-nid-req-xx.txt

which is being finalized currently.  I.e., that document lays out the
mechanism, which should be "live" within the next little while.

Leslie.

------------------------------------------------------------------------------

  "Never confuse                               Leslie Daigle
     an appreciation of the simple                              
              for                              Bunyip Information Systems Inc.
     a lack of understanding of the complex."  +1 514 285 0088
                  -- ThinkingCat               leslie@bunyip.com
 
------------------------------------------------------------------------------



From owner-urn-ietf@Bunyip.Com  Fri Apr  2 04:51:10 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21280
	for <urn-archive@ietf.org>; Fri, 2 Apr 1999 04:51:09 -0500 (EST)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id DAA00272
	for urn-ietf-out; Fri, 2 Apr 1999 03:53:57 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id DAA00267
	for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 03:53:55 -0500 (EST)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id DAA26661
	for urn-ietf@services; Fri, 2 Apr 1999 03:53:54 -0500 (EST)
Received: from lis.yonsei.ac.kr (lis.yonsei.ac.kr [165.132.148.111])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id DAA26658
	for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 03:53:29 -0500 (EST)
Received: from lis.yonsei.ac.kr ([165.132.148.191])
	by lis.yonsei.ac.kr (8.9.1a-H1/8.9.1) with ESMTP id RAA28427
	for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 17:53:05 +0900 (KST)
Message-ID: <37048548.E1FD0156@lis.yonsei.ac.kr>
Date: Fri, 02 Apr 1999 17:52:25 +0900
From: lislee <lislee@lis.yonsei.ac.kr>
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: urn-ietf@Bunyip.Com
Subject: [URN] About RFC2168
Content-Type: multipart/alternative;
 boundary="------------A18DE0118ECBFE5131817667"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: lislee <lislee@lis.yonsei.ac.kr>
Errors-To: owner-urn-ietf@Bunyip.Com

--------------A18DE0118ECBFE5131817667
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'm a student interested in URN system, especially in URN resolution
system.
I am preparing for my master's thesis about URN system.

After reading   RFC2168(Resolution of Uniform Resource Identifiers using
the Domain Name System)  ,
and   Internet Draft(The Naming Authority Pointer (NAPTR) DNS Resource
Record)  , I can roughly understand how to resolve URN using NAPTR RR.

I have some question about RFC2168.
Anybody who knows about my question tell me some advice.

<In RFC2168>
Example 2
---------

   Consider a URN namespace based on MIME Content-Ids. The URN might
   look like this:

                 urn:cid:199606121851.1@mordred.gatech.edu

   (Note that this example is chosen for pedagogical purposes, and does
   not conform to the recently-approved CID URL scheme.)

   The first step in the resolution process is to find out about the CID

   namespace. The namespace identifier, cid, is extracted from the URN,
   prepended to urn.net, and the NAPTR for cid.urn.net looked up. It
   might return records of the form:

 cid.urn.net
  ;;       order pref flags service        regexp           replacement
   IN NAPTR 100   10   ""  ""  "/urn:cid:.+@([^\.]+\.)(.*)$/\2/i"    .

   We have only one NAPTR response, so ordering the responses is not a
   problem.  The replacement field is empty, so we check the regexp
   field and use the pattern provided there. We apply that regexp to the

   entire URN to see if it matches, which it does.  The \2 part of the
   substitution expression returns the string "gatech.edu". Since the
   flags field does not contain "s" or "a", the lookup is not terminal
   and our next probe to DNS is for more NAPTR records:
   lookup(query=NAPTR, "gatech.edu").
<In RFC2168>


The NAPTR record has a string 'cid', so 'cid.urn.net' is retrived at the
1st look-up.
But I guess 'cid' is not a resolver of that URN, only a NID.
So it has no flag value, and no replacement value, but has regexp value.

And 2nd NAPTR look-up is processed with the string 'gatech.edu'.
My first question is that why the 2nd look-up is processed with
'gatech.edu', not else string?
How does the \2 part of the substitution expression return the string
"gatech.edu"?
And when the replacement field has value, and when it doesn't have
value?


I can imagine that I'll make URN as like <urn:k-univ:yonsei:d/lis/99-1>.

'k-univ' means "Korean Universities", and 'yonsei' means "Yonsei
University".
And the resolver of this URN is yonsei., its URL is
<http://www.yonse.ac.kr>.
And 'k-univ' is not a resolver, it's URL is <http://www.k-univ.ac.kr>
But I register NID of this URN as 'k-univ', because all the URNs of each
university should be managed in
'k-univ'.

If 'k-univ' is a resolver of that URN, maybe the result of querying
'k-univ.urn.net' is as follow.

k-univ.urn.net
;;                 order   pref  flags
service                       regexp               replacement
IN NAPTR   100     10   "s"    "http+N2L+N2C+N2R"
''''             http.www.k-univ.ac.kr

And client can discover the resolver of that URN, and access it to
http.www.k-univ.ac.kr.

But 'k-univ' is not a resolver, so the result of querying
'k-univ.urn.net' is like that(it is my imagination)

k-univ.urn.net
;;                 order   pref   flags
service                     regexp                           replacement

IN NAPTR   100     10     ""              ""              "/urn:k-univ:
'^.*yonsei.*$/\?/?"            .

Because, 'k-univ is not a resolver of that URN, flags field has no
value, and replacement has no value, and
regexp has some value. (I don't know exactly what the value is. the
example is my free
expression.)

And record returned from the query on "yonsei" might look like:

yonsei IN NAPTR
  ;;              order pref flags
service                      regexp                  replacement
 IN NAPTR 100   10   "s"      " http+N2L+N2C+N2R"
.                http.www.yonse.ac.kr

And client can discover the resolver of that URN, and access it to
http.www.yonsei.ac.kr.


Is there any problem above my imagination?
When I make my URN, should not I use the character '/' which is a
reserved character in URN syntax(RFC2141).
Or should Iuse "%" encoding?


My 2nd question is like that:

I chance to meet the internet-draft,  Handle System: A Persistent Global
Name Service Overview and Syntax.
I think Handle System doesn't use RDS(Resolver Discovery Service),
instead it resolves handle(a kind of
URN) directly.

Anybody who knows the difference of NAPTR and Handle system tell me the
difference.
And in Handle System syntax, the character '/' is used.
I know that the character '/' is a reserved character in URN
syntax(RFC2141).


--------------A18DE0118ECBFE5131817667
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I'm a student interested in URN system, especially in URN resolution system.
<br>I am preparing for my master's thesis about URN system.
<p>After reading&nbsp;&nbsp; <a href="ftp://ftp.isi.edu/in-notes/rfc2168.txt">RFC2168(Resolution
of Uniform Resource Identifiers using the Domain Name System)</a>&nbsp;
,
<br>and&nbsp;&nbsp; <a href="http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.txt">Internet
Draft(The Naming Authority Pointer (NAPTR) DNS Resource Record)</a>&nbsp;
, I can roughly understand how to resolve URN using NAPTR RR.
<p>I have some question about RFC2168.
<br>Anybody who knows about my question tell me some advice.
<p>&lt;In RFC2168>
<br>Example 2
<br>---------
<p>&nbsp;&nbsp; Consider a URN namespace based on MIME Content-Ids. The
URN might
<br>&nbsp;&nbsp; look like this:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<A HREF="urn:cid:199606121851.1@mordred.gatech.edu">urn:cid:199606121851.1@mordred.gatech.edu</A>
<p>&nbsp;&nbsp; (Note that this example is chosen for pedagogical purposes,
and does
<br>&nbsp;&nbsp; not conform to the recently-approved CID URL scheme.)
<p>&nbsp;&nbsp; The first step in the resolution process is to find out
about the CID
<br>&nbsp;&nbsp; namespace. The namespace identifier, cid, is extracted
from the URN,
<br>&nbsp;&nbsp; prepended to urn.net, and the NAPTR for cid.urn.net looked
up. It
<br>&nbsp;&nbsp; might return records of the form:
<p>&nbsp;cid.urn.net
<br>&nbsp; ;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; order pref flags service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; replacement
<br>&nbsp;&nbsp; IN NAPTR 100&nbsp;&nbsp; 10&nbsp;&nbsp; ""&nbsp; ""&nbsp;
"/<A HREF="urn:cid:.+@([^\">urn:cid:.+@([^\</A>.]+\.)(.*)$/\2/i"&nbsp;&nbsp;&nbsp; .
<p>&nbsp;&nbsp; We have only one NAPTR response, so ordering the responses
is not a
<br>&nbsp;&nbsp; problem.&nbsp; The replacement field is empty, so we check
the regexp
<br>&nbsp;&nbsp; field and use the pattern provided there. We apply that
regexp to the
<br>&nbsp;&nbsp; entire URN to see if it matches, which it does.&nbsp;
<b><u>The \2 part of the</u></b>
<br><b><u>&nbsp;&nbsp; substitution expression returns the string "gatech.edu".</u></b>
Since the
<br>&nbsp;&nbsp; flags field does not contain "s" or "a", the lookup is
not terminal
<br>&nbsp;&nbsp; and our next probe to DNS is for more NAPTR records:
<br>&nbsp;&nbsp; lookup(query=NAPTR, "gatech.edu").
<br>&lt;In RFC2168>
<br>&nbsp;
<p>The NAPTR record has a string 'cid', so 'cid.urn.net' is retrived at
the 1st look-up.
<br>But I guess 'cid' is not a resolver of that URN, only a NID.
<br>So it has no flag value, and no replacement value, but has regexp value.
<br>And 2nd NAPTR look-up is processed with the string 'gatech.edu'.
<br>My first question is that why the 2nd look-up is processed with 'gatech.edu',
not else string?
<br>How does the \2 part of the substitution expression return the string
"gatech.edu"?
<br>And when the replacement field has value, and when it doesn't have
value?
<br>&nbsp;
<p>I can imagine that I'll make URN as like &lt;<A HREF="urn:k-univ:yonsei:d/lis/99-1">urn:k-univ:yonsei:d/lis/99-1</A>>.
<br>'k-univ' means "Korean Universities", and 'yonsei' means "Yonsei University".
<br>And the resolver of this URN is yonsei., its URL is &lt;<A HREF="http://www.yonse.ac.kr">http://www.yonse.ac.kr</A>>.
<br>And 'k-univ' is not a resolver, it's URL is &lt;<A HREF="http://www.k-univ.ac.kr">http://www.k-univ.ac.kr</A>>
<br>But I register NID of this URN as 'k-univ', because all the URNs of
each university should be managed in
<br>'k-univ'.
<p>If 'k-univ' is a resolver of that URN, maybe the result of querying
'k-univ.urn.net' is as follow.
<p>k-univ.urn.net
<br>;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
order&nbsp;&nbsp; pref&nbsp; flags&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
replacement
<br>IN NAPTR&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp; "s"&nbsp;&nbsp;&nbsp;
"http+N2L+N2C+N2R"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ''''&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http.www.k-univ.ac.kr
<p>And client can discover the resolver of that URN, and access it to http.www.k-univ.ac.kr.
<p>But 'k-univ' is not a resolver, so the result of querying 'k-univ.urn.net'
is like that(it is my imagination)
<p>k-univ.urn.net
<br>;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
order&nbsp;&nbsp; pref&nbsp;&nbsp; flags&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
replacement
<br>IN NAPTR&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;
""&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
""&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
"/urn:k-univ: '^.*yonsei.*$/\?/?"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--------------A18DE0118ECBFE5131817667--


From owner-urn-ietf@Bunyip.Com  Fri Apr  2 07:36:57 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22108
	for <urn-archive@ietf.org>; Fri, 2 Apr 1999 07:36:56 -0500 (EST)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id GAA01854
	for urn-ietf-out; Fri, 2 Apr 1999 06:46:57 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id GAA01849
	for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 06:46:55 -0500 (EST)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id GAA27043
	for urn-ietf@services; Fri, 2 Apr 1999 06:46:54 -0500 (EST)
Received: from lis.yonsei.ac.kr (lis.yonsei.ac.kr [165.132.148.111])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id GAA27040
	for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 06:46:47 -0500 (EST)
Received: from lis.yonsei.ac.kr ([165.132.148.191])
	by lis.yonsei.ac.kr (8.9.1a-H1/8.9.1) with ESMTP id UAA29299;
	Fri, 2 Apr 1999 20:46:15 +0900 (KST)
Message-ID: <3704ADDC.BEBC537@lis.yonsei.ac.kr>
Date: Fri, 02 Apr 1999 20:45:33 +0900
From: lislee <lislee@lis.yonsei.ac.kr>
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: urn-ietf@Bunyip.Com, lislee@lis.yonsei.ac.kr
Subject: [URN] about RFC2168
Content-Type: multipart/alternative;
 boundary="------------CCBACF9DD16F9659487608BE"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: lislee <lislee@lis.yonsei.ac.kr>
Errors-To: owner-urn-ietf@Bunyip.Com

--------------CCBACF9DD16F9659487608BE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I'm a student interested in URN system, especially in URN resolution
system.
I am preparing for my master's thesis about URN system.

After reading    RFC2168(Resolution of Uniform Resource Identifiers
using the Domain Name System)  ,
and    Internet Draft(The Naming Authority Pointer (NAPTR) DNS Resource
Record)   , I can roughly
understand how to resolve URN using NAPTR RR.

I have some question about RFC2168.
Anybody who knows about my question tell me some advice.

<In RFC2168>
Example 2
---------

   Consider a URN namespace based on MIME Content-Ids. The URN might
   look like this:

                 urn:cid:199606121851.1@mordred.gatech.edu

   (Note that this example is chosen for pedagogical purposes, and does
   not conform to the recently-approved CID URL scheme.)

   The first step in the resolution process is to find out about the CID

   namespace. The namespace identifier, cid, is extracted from the URN,
   prepended to urn.net, and the NAPTR for cid.urn.net looked up. It
   might return records of the form:

 cid.urn.net
  ;;       order pref flags service        regexp           replacement
   IN NAPTR 100   10   ""  ""  "/urn:cid:.+@([^\.]+\.)(.*)$/\2/i"    .

   We have only one NAPTR response, so ordering the responses is not a
   problem.  The replacement field is empty, so we check the regexp
   field and use the pattern provided there. We apply that regexp to the

   entire URN to see if it matches, which it does.  The \2 part of the
   substitution expression returns the string "gatech.edu". Since the
   flags field does not contain "s" or "a", the lookup is not terminal
   and our next probe to DNS is for more NAPTR records:
   lookup(query=NAPTR, "gatech.edu").
<In RFC2168>


The NAPTR record has a string 'cid', so 'cid.urn.net' is retrived at the
1st look-up.
But I guess 'cid' is not a resolver of that URN, only a NID.
So it has no flag value, and no replacement value, but has regexp value.

And 2nd NAPTR look-up is processed with the string 'gatech.edu'.
My first question is that why the 2nd look-up is processed with
'gatech.edu', not else string?
How does the \2 part of the substitution expression return the string
"gatech.edu"?
And when the replacement field has value, and when it doesn't have
value?


I can imagine that I'll make URN as like <urn:k-univ:yonsei:d/lis/99-1>.

'k-univ' means "Korean Universities", and 'yonsei' means "Yonsei
University".
And the resolver of this URN is yonsei., its URL is
<http://www.yonse.ac.kr>.
And 'k-univ' is not a resolver, it's URL is <http://www.k-univ.ac.kr>
But I register NID of this URN as 'k-univ', because all the URNs of each
university should be managed in
'k-univ'.

If 'k-univ' is a resolver of that URN, maybe the result of querying
'k-univ.urn.net' is as follow.

k-univ.urn.net
;;                 order   pref  flags
service                       regexp               replacement
IN NAPTR   100     10   "s"    "http+N2L+N2C+N2R"
''''             http.www.k-univ.ac.kr

And client can discover the resolver of that URN, and access it to
http.www.k-univ.ac.kr.

But 'k-univ' is not a resolver, so the result of querying
'k-univ.urn.net' is like that(it is my imagination)

k-univ.urn.net
;;                 order   pref   flags
service                     regexp                           replacement

IN NAPTR   100     10     ""              ""              "/urn:k-univ:
'^.*yonsei.*$/\?/?"            .

Because, 'k-univ is not a resolver of that URN, flags field has no
value, and replacement has no value, and
regexp has some value. (I don't know exactly what the value is. the
example is my free
expression.)

And record returned from the query on "yonsei" might look like:

yonsei IN NAPTR
  ;;              order pref flags
service                      regexp                  replacement
 IN NAPTR 100   10   "s"      " http+N2L+N2C+N2R"
.                http.www.yonse.ac.kr

And client can discover the resolver of that URN, and access it to
http.www.yonsei.ac.kr.


Is there any problem above my imagination?
When I make my URN, should not I use the character '/' which is a
reserved character in URN
syntax(RFC2141).
Or should Iuse "%" encoding?


My 2nd question is like that:

I chance to meet the internet-draft,   Handle System: A Persistent
Global Name Service Overview
and I think Handle System doesn't use RDS(Resolver Discovery Service),
instead it resolves handle(a kind of
URN) directly.

Anybody who knows the difference of NAPTR and Handle system tell me the
difference.
And in Handle System syntax, the character '/' is used.
I know that the character '/' is a reserved character in URN
syntax(RFC2141).

--------------CCBACF9DD16F9659487608BE
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>I'm a student interested in URN system, especially in URN resolution
system.
<br>I am preparing for my master's thesis about URN system.
<p>After reading&nbsp;&nbsp;&nbsp; <a href="ftp://ftp.isi.edu/in-notes/rfc2168.txt">RFC2168(Resolution
of Uniform Resource Identifiers using the Domain Name System)</a>&nbsp;
,
<br>and&nbsp;&nbsp;&nbsp; <a href="http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.txt">Internet
Draft(The Naming Authority Pointer (NAPTR) DNS Resource Record)</a>&nbsp;&nbsp;
, I can roughly
<br>understand how to resolve URN using NAPTR RR.
<p>I have some question about RFC2168.
<br>Anybody who knows about my question tell me some advice.
<p>&lt;In RFC2168>
<br>Example 2
<br>---------
<p>&nbsp;&nbsp; Consider a URN namespace based on MIME Content-Ids. The
URN might
<br>&nbsp;&nbsp; look like this:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<A HREF="urn:cid:199606121851.1@mordred.gatech.edu">urn:cid:199606121851.1@mordred.gatech.edu</A>
<p>&nbsp;&nbsp; (Note that this example is chosen for pedagogical purposes,
and does
<br>&nbsp;&nbsp; not conform to the recently-approved CID URL scheme.)
<p>&nbsp;&nbsp; The first step in the resolution process is to find out
about the CID
<br>&nbsp;&nbsp; namespace. The namespace identifier, cid, is extracted
from the URN,
<br>&nbsp;&nbsp; prepended to urn.net, and the NAPTR for cid.urn.net looked
up. It
<br>&nbsp;&nbsp; might return records of the form:
<p>&nbsp;cid.urn.net
<br>&nbsp; ;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; order pref flags service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; replacement
<br>&nbsp;&nbsp; IN NAPTR 100&nbsp;&nbsp; 10&nbsp;&nbsp; ""&nbsp; ""&nbsp;
"/<A HREF="urn:cid:.+@([^\">urn:cid:.+@([^\</A>.]+\.)(.*)$/\2/i"&nbsp;&nbsp;&nbsp; .
<p>&nbsp;&nbsp; We have only one NAPTR response, so ordering the responses
is not a
<br>&nbsp;&nbsp; problem.&nbsp; The replacement field is empty, so we check
the regexp
<br>&nbsp;&nbsp; field and use the pattern provided there. We apply that
regexp to the
<br>&nbsp;&nbsp; entire URN to see if it matches, which it does.&nbsp;
The \2 part of the
<br>&nbsp;&nbsp; substitution expression returns the string "gatech.edu".
Since the
<br>&nbsp;&nbsp; flags field does not contain "s" or "a", the lookup is
not terminal
<br>&nbsp;&nbsp; and our next probe to DNS is for more NAPTR records:
<br>&nbsp;&nbsp; lookup(query=NAPTR, "gatech.edu").
<br>&lt;In RFC2168>
<br>&nbsp;
<p>The NAPTR record has a string 'cid', so 'cid.urn.net' is retrived at
the 1st look-up.
<br>But I guess 'cid' is not a resolver of that URN, only a NID.
<br>So it has no flag value, and no replacement value, but has regexp value.
<br>And 2nd NAPTR look-up is processed with the string 'gatech.edu'.
<br>My first question is that why the 2nd look-up is processed with 'gatech.edu',
not else string?
<br>How does the \2 part of the substitution expression return the string
"gatech.edu"?
<br>And when the replacement field has value, and when it doesn't have
value?
<br>&nbsp;
<p>I can imagine that I'll make URN as like &lt;<A HREF="urn:k-univ:yonsei:d/lis/99-1">urn:k-univ:yonsei:d/lis/99-1</A>>.
<br>'k-univ' means "Korean Universities", and 'yonsei' means "Yonsei University".
<br>And the resolver of this URN is yonsei., its URL is &lt;<A HREF="http://www.yonse.ac.kr">http://www.yonse.ac.kr</A>>.
<br>And 'k-univ' is not a resolver, it's URL is &lt;<A HREF="http://www.k-univ.ac.kr">http://www.k-univ.ac.kr</A>>
<br>But I register NID of this URN as 'k-univ', because all the URNs of
each university should be managed in
<br>'k-univ'.
<p>If 'k-univ' is a resolver of that URN, maybe the result of querying
'k-univ.urn.net' is as follow.
<p>k-univ.urn.net
<br>;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
order&nbsp;&nbsp; pref&nbsp; flags&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
replacement
<br>IN NAPTR&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp; "s"&nbsp;&nbsp;&nbsp;
"http+N2L+N2C+N2R"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ''''&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http.www.k-univ.ac.kr
<p>And client can discover the resolver of that URN, and access it to http.www.k-univ.ac.kr.
<p>But 'k-univ' is not a resolver, so the result of querying 'k-univ.urn.net'
is like that(it is my imagination)
<p>k-univ.urn.net
<br>;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
order&nbsp;&nbsp; pref&nbsp;&nbsp; flags&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
replacement
<br>IN NAPTR&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;
""&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
""&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
"/urn:k-univ: '^.*yonsei.*$/\?/?"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--------------CCBACF9DD16F9659487608BE--


From owner-urn-ietf@Bunyip.Com  Fri Apr  2 17:07:25 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05746
	for <urn-archive@ietf.org>; Fri, 2 Apr 1999 17:07:24 -0500 (EST)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id QAA06416
	for urn-ietf-out; Fri, 2 Apr 1999 16:22:48 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id QAA06408
	for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 16:22:45 -0500 (EST)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id QAA28311
	for urn-ietf@services; Fri, 2 Apr 1999 16:22:44 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id QAA28308
	for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 16:22:42 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04013;
	Fri, 2 Apr 1999 16:22:38 -0500 (EST)
Message-Id: <199904022122.QAA04013@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: urn-ietf@Bunyip.Com
From: Internet-Drafts@ietf.org
Subject: [URN] I-D ACTION:draft-ietf-urn-nid-req-08.txt
Date: Fri, 02 Apr 1999 16:22:37 -0500
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org
Errors-To: owner-urn-ietf@Bunyip.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-nid-req-08.txt
	Pages		: 14
	Date		: 31-Mar-99
	
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 ([RFC2168, RFC2169]).
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'.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-nid-req-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-nid-req-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-nid-req-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:	<19990401090834.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-nid-req-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-urn-nid-req-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990401090834.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-urn-ietf@Bunyip.Com  Fri Apr  2 18:12:10 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09204
	for <urn-archive@ietf.org>; Fri, 2 Apr 1999 18:12:09 -0500 (EST)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id RAA07181
	for urn-ietf-out; Fri, 2 Apr 1999 17:25:30 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id RAA07176
	for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 17:25:27 -0500 (EST)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id RAA28632
	for urn-ietf@services; Fri, 2 Apr 1999 17:25:27 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id RAA28629
	for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 17:25:25 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06520;
	Fri, 2 Apr 1999 17:25:19 -0500 (EST)
Message-Id: <199904022225.RAA06520@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: urn-ietf@Bunyip.Com
From: Internet-Drafts@ietf.org
Subject: [URN] I-D ACTION:draft-ietf-urn-naptr-rr-02.txt
Date: Fri, 02 Apr 1999 17:25:19 -0500
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org
Errors-To: owner-urn-ietf@Bunyip.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           : The Naming Authority Pointer (NAPTR) DNS
			  Resource Record
	Author(s)	: M. Mealling, R. Daniel
	Filename	: draft-ietf-urn-naptr-rr-02.txt
	Pages		: 15
	Date		: 01-Apr-99
	
This document describes a DNS Resource Record (RR) which specifies a rewrite rule that, when applied to an existing string,
will produce a new domain. Reasons for rewriting a domain
vary from URN Resource Discovery Systems to moving out-of-date
services to new domains.
 
This document updates those portions of RFC2168 specifically
dealing with the definition of the NAPTR record.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.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-naptr-rr-02.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-naptr-rr-02.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:	<19990401152434.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-naptr-rr-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-urn-naptr-rr-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990401152434.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-urn-ietf@Bunyip.Com  Fri Apr  2 19:42:20 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14818
	for <urn-archive@ietf.org>; Fri, 2 Apr 1999 19:42:19 -0500 (EST)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id SAA08024
	for urn-ietf-out; Fri, 2 Apr 1999 18:49:08 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id SAA08010
	for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 18:48:13 -0500 (EST)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id SAA28943
	for urn-ietf@services; Fri, 2 Apr 1999 18:48:12 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id SAA28940
	for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 18:48:10 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11593;
	Fri, 2 Apr 1999 18:48:07 -0500 (EST)
Message-Id: <199904022348.SAA11593@ietf.org>
To: IETF-Announce: ;
Cc: urn-ietf@Bunyip.Com, lc-uri-resolution@apps.ietf.org
From: The IESG <iesg-secretary@ietf.org>
Subject: [URN] Last Call: Assignment Procedures for the URI Resolution using
	 DNS (RFC2168) to BCP
Date: Fri, 02 Apr 1999 18:48:07 -0500
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: The IESG <iesg-secretary@ietf.org>
Errors-To: owner-urn-ietf@Bunyip.Com

The IESG has received a request from the Uniform Resource Names Working
Group to consider the publication of the following:

Assignment Procedures for the URI Resolution using DNS (RFC2168)
<draft-ietf-urn-net-procedures-02.txt> as a BCP. 

Resolution of Uniform Resource Identifiers using the Domain Name
System <draft-ietf-urn-dns-rds-00.txt> as a Proposed Standard.  

The Naming Authority Pointer (NAPTR) DNS Resource Record
<draft-ietf-urn-naptr-rr-02.txt> as a Proposed Standard.  


The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by April 16, 1999.

The Applications Area Directors request that any Last Call comments
on these documents, be CC'ed to <lc-uri-resolution@apps.ietf.org>.


Files can be obtained via:
http://www.ietf.org/internet-drafts/draft-ietf-urn-net-procedures-02.txt
http://www.ietf.org/internet-drafts/draft-ietf-urn-dns-rds-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.txt



From owner-urn-ietf@Bunyip.Com  Fri Apr  2 19:49:01 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15086
	for <urn-archive@ietf.org>; Fri, 2 Apr 1999 19:49:01 -0500 (EST)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id SAA07980
	for urn-ietf-out; Fri, 2 Apr 1999 18:43:51 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id SAA07972
	for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 18:42:55 -0500 (EST)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id SAA28925
	for urn-ietf@services; Fri, 2 Apr 1999 18:42:55 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id SAA28921
	for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 18:42:52 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11210;
	Fri, 2 Apr 1999 18:42:49 -0500 (EST)
Message-Id: <199904022342.SAA11210@ietf.org>
To: IETF-Announce: ;
Cc: urn-ietf@Bunyip.Com, lc-uri-resolution@apps.ietf.org
From: The IESG <iesg-secretary@ietf.org>
Subject: [URN] Last Call: Assignment Procedures for the URI Resolution using
	 DNS (RFC2168) to BCP
Date: Fri, 02 Apr 1999 18:42:49 -0500
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: The IESG <iesg-secretary@ietf.org>
Errors-To: owner-urn-ietf@Bunyip.Com

The IESG has received a request from the Uniform Resource Names Working
Group to consider the publication of the following:

Assignment Procedures for the URI Resolution using DNS (RFC2168) <draft-ietf-urn-net-procedures-02.txt> as a BCP. 

Resolution of Uniform Resource Identifiers using the Domain Name System <draft-ietf-urn-dns-rds-00.txt> as a Proposed Standard.  

The Naming Authority Pointer (NAPTR) DNS Resource Record <draft-ietf-urn-naptr-rr-02.txt> as a Proposed Standard.  


The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by April 16, 1999.

The Applications Area Directors request that any Last Call comments
on these documents, be CC'ed to <lc-uri-resolution@apps.ietf.org>.


Files can be obtained via:
http://www.ietf.org/internet-drafts/draft-ietf-urn-net-procedures-02.txt
http://www.ietf.org/internet-drafts/draft-ietf-urn-dns-rds-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.txt



From owner-urn-ietf@Bunyip.Com  Fri Apr  2 19:50:24 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15143
	for <urn-archive@ietf.org>; Fri, 2 Apr 1999 19:50:23 -0500 (EST)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id TAA08205
	for urn-ietf-out; Fri, 2 Apr 1999 19:10:51 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id TAA08200
	for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 19:10:49 -0500 (EST)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id TAA28999
	for urn-ietf@services; Fri, 2 Apr 1999 19:10:48 -0500 (EST)
Received: from LOGOS.CC.BRANDEIS.EDU (logos.cc.brandeis.edu [129.64.1.2])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id TAA28995;
	Fri, 2 Apr 1999 19:10:45 -0500 (EST)
Received: from mantiscorp.com (mantiscorp.com)
 by LOGOS.CC.BRANDEIS.EDU (PMDF V5.0-8 #17137)
 id <01J9KH8IGRLCBNMXQS@LOGOS.CC.BRANDEIS.EDU>; Fri,
 02 Apr 1999 19:11:04 -0500 (EST)
Date: Fri, 02 Apr 1999 19:09:59 -0500
From: "Aaron E. Walsh" <aaron@mantiscorp.com>
Subject: Re: [URN] status
To: Leslie Daigle <leslie@Bunyip.Com>
Cc: urn-ietf@Bunyip.Com
Message-id: <37055C57.93EF0750@mantiscorp.com>
Organization: Mantis Development Corp.
MIME-version: 1.0
X-Mailer: Mozilla 4.51 [en]C-compaq  (Win98; I)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: <Pine.SUN.3.95.990401071901.17797A-100000@buzz.Bunyip.Com>
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: "Aaron E. Walsh" <aaron@mantiscorp.com>
Errors-To: owner-urn-ietf@Bunyip.Com
Content-Transfer-Encoding: 7bit

Thanks Leslie.. that was the pointer I needed :)

Aaron

Leslie Daigle wrote:
> 
> Howdy,
> 
> On Wed, 31 Mar 1999, Aaron E. Walsh wrote:
> > I'm preparing now to register a few URN namespaces, and wonder if you or
> > others could point me towards the proper documents to file? I understand
> > this isn't as simple a process as simply submitting an online form, as
> > we do for domains through InterNic, so want to make sure I'm heading in
> > the right direction :)
> 
> The procedure is outlined in
> 
>         draft-ietf-urn-nid-req-xx.txt
> 
> which is being finalized currently.  I.e., that document lays out the
> mechanism, which should be "live" within the next little while.
> 
> Leslie.
> 
> ------------------------------------------------------------------------------
> 
>   "Never confuse                               Leslie Daigle
>      an appreciation of the simple
>               for                              Bunyip Information Systems Inc.
>      a lack of understanding of the complex."  +1 514 285 0088
>                   -- ThinkingCat               leslie@bunyip.com
> 
> ------------------------------------------------------------------------------



From owner-urn-ietf@Bunyip.Com  Tue Apr  6 04:00:38 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29780
	for <urn-archive@ietf.org>; Tue, 6 Apr 1999 04:00:38 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id DAA25060
	for urn-ietf-out; Tue, 6 Apr 1999 03:05:35 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id DAA25055
	for <urn-ietf@services.bunyip.com>; Tue, 6 Apr 1999 03:05:32 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id DAA06253
	for urn-ietf@services; Tue, 6 Apr 1999 03:05:31 -0400 (EDT)
Received: from lis.yonsei.ac.kr ([165.132.148.111])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id DAA06250
	for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 03:05:17 -0400 (EDT)
Received: from lis.yonsei.ac.kr ([165.132.148.191])
	by lis.yonsei.ac.kr (8.9.1a-H1/8.9.1) with ESMTP id QAA04024
	for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 16:04:38 +0900 (KST)
Message-ID: <3709B1DB.9A9A456@lis.yonsei.ac.kr>
Date: Tue, 06 Apr 1999 16:03:55 +0900
From: lislee <lislee@lis.yonsei.ac.kr>
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: urn-ietf@Bunyip.Com
Subject: [URN] about reserved character slash('/')
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: lislee <lislee@lis.yonsei.ac.kr>
Errors-To: owner-urn-ietf@Bunyip.Com
Content-Transfer-Encoding: 8bit

I'm a student interested in URN.

In RFC2141(URN Syntax), the character slash('/') is a reserved
character, so it cannot be used in URN syntax.

But in DOI(Digital Object Identifier) or Handle System, the character
slash is used.

I think the character slash is useful in distinguishing something from
others, or  expressing hierarchical relation. For example,
<urn:USA:university/UCLA/1999-1>
So I think the character slash is to be freed from reserved character.

How about your opinion?



From owner-urn-ietf@Bunyip.Com  Tue Apr  6 12:57:26 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13149
	for <urn-archive@ietf.org>; Tue, 6 Apr 1999 12:57:25 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id LAA00481
	for urn-ietf-out; Tue, 6 Apr 1999 11:27:54 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA00475
	for <urn-ietf@services.bunyip.com>; Tue, 6 Apr 1999 11:27:50 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id LAA09631
	for urn-ietf@services; Tue, 6 Apr 1999 11:27:46 -0400 (EDT)
Received: from library.berkeley.edu (library.Berkeley.EDU [128.32.224.55])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA09628
	for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 11:27:43 -0400 (EDT)
Received: from jerome (doenx-380-8.Lib.Berkeley.EDU [128.32.224.162])
	by library.berkeley.edu (8.9.1a/8.9.1) with SMTP id IAA12831
	for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 08:33:01 -0700 (PDT)
Message-Id: <3.0.5.32.19990406081530.00983380@library.berkeley.edu>
X-Sender: jmcdonou@library.berkeley.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Tue, 06 Apr 1999 08:15:30 -0700
To: urn-ietf@Bunyip.Com
From: Jerome McDonough <jmcdonou@library.berkeley.edu>
Subject: [URN] Microsoft & URNs
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Jerome McDonough <jmcdonou@library.berkeley.edu>
Errors-To: owner-urn-ietf@Bunyip.Com

Thought this might interest you all.  In an article discussing XML's
use in Microsoft Office 2000
(http://webreview.com/wr/pub/1999/04/02/edge/index.html?wwwrrr_19990402.txt)
, the
author describes writing a simple document in Word and saving it as HTML.
The opening of the resulting document looks like this:

	<html xmlns:v="urn:schemas-microsoft-com:vml"
     xmlns:o="urn:schemas-microsoft-com:office:office"
     xmlns:w="urn:schemas-microsoft-com:office:word" 
     xmlns="-//W3C//DTD HTML 4.0//EN">

I found it intriguing that they're using URNs instead of URLs to define
name spaces.



Jerome McDonough -- jmcdonou@library.Berkeley.EDU  |  (......)
Library Systems Office, 386 Doe, U.C. Berkeley     |  \ *  * /
Berkeley, CA 94720-6000    (510) 642-5168          |  \  <>  /
"Well, it looks easy enough...."                   |   \ -- /  SGNORMPF!!!
         -- From the Famous Last Words file        |    ||||



From owner-urn-ietf@Bunyip.Com  Tue Apr  6 16:24:47 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16568
	for <urn-archive@ietf.org>; Tue, 6 Apr 1999 16:24:41 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id OAA03724
	for urn-ietf-out; Tue, 6 Apr 1999 14:50:52 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA03717
	for <urn-ietf@services.bunyip.com>; Tue, 6 Apr 1999 14:50:47 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id OAA10839
	for urn-ietf@services; Tue, 6 Apr 1999 14:50:46 -0400 (EDT)
Received: from email.centraal.com ([216.33.4.99])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA10832
	for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 14:50:34 -0400 (EDT)
Received: by mail.centraal.com with Internet Mail Service (5.5.2448.0)
	id <2LPGVCJS>; Tue, 6 Apr 1999 11:49:49 -0700
Message-ID: <7D28C07629C9D211A1CC00500403ADD41D3754@mail.centraal.com>
From: Yves Arrouye <Yves@centraal.com>
To: urn-ietf@Bunyip.Com
Subject: RE: [URN] Microsoft & URNs
Date: Tue, 6 Apr 1999 11:49:49 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Yves Arrouye <Yves@centraal.com>
Errors-To: owner-urn-ietf@Bunyip.Com

> author describes writing a simple document in Word and saving 
> it as HTML.
> The opening of the resulting document looks like this:
> 
> 	<html xmlns:v="urn:schemas-microsoft-com:vml"
>      xmlns:o="urn:schemas-microsoft-com:office:office"
>      xmlns:w="urn:schemas-microsoft-com:office:word" 
>      xmlns="-//W3C//DTD HTML 4.0//EN">
> 
> I found it intriguing that they're using URNs instead of URLs 
> to define
> name spaces.

Though the last time I checked, they didn't provide a way to get to their
document through a standard URN resolution mechanism. So it's quite useless
right now.

Yves.



From owner-urn-ietf@Bunyip.Com  Thu Apr  8 13:42:30 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04844
	for <urn-archive@ietf.org>; Thu, 8 Apr 1999 13:42:30 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id MAA12814
	for urn-ietf-out; Thu, 8 Apr 1999 12:10:26 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id MAA12809
	for <urn-ietf@services.bunyip.com>; Thu, 8 Apr 1999 12:10:20 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id KAA17407
	for urn-ietf@services; Thu, 8 Apr 1999 10:26:51 -0400 (EDT)
Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id KAA17400
	for <urn-ietf@bunyip.com>; Thu, 8 Apr 1999 10:26:42 -0400 (EDT)
Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id KAA13463 for urn-ietf@bunyip.com; Thu, 8 Apr 1999 10:18:24 -0400 (EDT)
From: Michael Mealling <michael@bailey.dscga.com>
Message-Id: <199904081418.KAA13463@bailey.dscga.com>
Subject: [URN] a proposed technical change to the NAPTR drafts...
To: urn-ietf@Bunyip.Com
Date: Thu, 8 Apr 1999 10:18:24 -0400 (EDT)
X-Mailer: ELM [version 2.4ME+ PL31H (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Michael Mealling <michael@bailey.dscga.com>
Errors-To: owner-urn-ietf@Bunyip.Com
Content-Transfer-Encoding: 7bit

Hi guys,
  In our Last Call comments we have received some from the DNSIND folx
concerning our use of SRV. Their suggestion is that we _not_ include
the protocol stuff in the domain-name that is found in either
the replacement field or the rewrite. In order to be more in line with
what the expected behavior of SRV will be we should use the protocol
out of our own Services field to construct the SRV.

Examples:

This is how we do it now:

IN NAPTR 100  50  "s"  "z3950+N2L+N2C"     ""    _z3950._tcp.gatech.edu.


This is how they would like it to behave:

IN NAPTR 100  50  "s"  "z3950+N2L+N2C"     ""    gatech.edu.

Then the client does the _z3950._tcp construct itself and prepends it to
the domain found in the replacement field.

In the first one the SRV component is explicit, thus creating a potential
error condition where the protocol in the Services field doesn't jive
with the stated protocol in the replacement. In the second its
emplicitly done by the client as part of the standard way clients use SRV
records, thus mitigating that error condition.

This is a content change as opposed to simple wordsmithing. The issues
for me are the following:

Code changes...

How do we know whether to use TCP or UDP for a given protocol? Most don't
have a UDP equivalent so its not that big of a deal. Those protocols that
do have a negotiated internal process for fall back (DNS itself does this).

I'm not aware of any other issues. If there are any please let me know...

-MM

-- 
--------------------------------------------------------------------------------
Michael Mealling	|      Vote Libertarian!       | www.rwhois.net/michael
Sr. Research Engineer   |   www.ga.lp.org/gwinnett     | ICQ#:         14198821
Network Solutions	|          www.lp.org          |  michaelm@netsol.com



From owner-urn-ietf@Bunyip.Com  Thu Apr 15 17:30:42 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14834
	for <urn-archive@ietf.org>; Thu, 15 Apr 1999 17:30:41 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id QAA22456
	for urn-ietf-out; Thu, 15 Apr 1999 16:03:31 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id QAA22451
	for <urn-ietf@services.bunyip.com>; Thu, 15 Apr 1999 16:03:27 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id QAA13261
	for urn-ietf@services; Thu, 15 Apr 1999 16:03:25 -0400 (EDT)
Received: from buzz.Bunyip.Com (buzz.Bunyip.Com [209.41.144.8])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id QAA13256;
	Thu, 15 Apr 1999 16:03:12 -0400 (EDT)
Received: from localhost (leslie@localhost) by buzz.Bunyip.Com (8.6.9/8.6.10) with SMTP id QAA22760; Thu, 15 Apr 1999 16:03:12 -0400
X-Authentication-Warning: buzz.Bunyip.Com: leslie owned process doing -bs
Date: Thu, 15 Apr 1999 16:03:11 -0400 (EDT)
From: Leslie Daigle <leslie@Bunyip.Com>
To: urn-ietf@Bunyip.Com
cc: Patrik Faltstrom <paf@swip.net>, moore@cs.utk.edu
Subject: [URN] reaching the chair
Message-ID: <Pine.SUN.3.95.990415160048.21755a-100000@buzz.Bunyip.Com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Leslie Daigle <leslie@Bunyip.Com>
Errors-To: owner-urn-ietf@Bunyip.Com

Howdy,

For any correspondance with me personally/as WG chair, please direct
your e-mail to

	leslie@thinkingcat.com

Thanks,
Leslie.

------------------------------------------------------------------------------

  "Never confuse                               Leslie Daigle
     an appreciation of the simple                              
              for                              
     a lack of understanding of the complex."  
                  -- ThinkingCat               leslie@thinkingcat.com
 
------------------------------------------------------------------------------



From owner-urn-ietf@Bunyip.Com  Fri Apr 16 16:14:34 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14823
	for <urn-archive@ietf.org>; Fri, 16 Apr 1999 16:14:27 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id OAA11259
	for urn-ietf-out; Fri, 16 Apr 1999 14:58:43 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA11254
	for <urn-ietf@services.bunyip.com>; Fri, 16 Apr 1999 14:58:39 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id OAA16691
	for urn-ietf@services; Fri, 16 Apr 1999 14:58:32 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA16688
	for <urn-ietf@bunyip.com>; Fri, 16 Apr 1999 14:58:30 -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 OAA11846;
	Fri, 16 Apr 1999 14:56:34 -0400 (EDT)
Message-Id: <199904161856.OAA11846@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: urn-ietf@Bunyip.Com
From: The IESG <iesg-secretary@ietf.org>
Subject: [URN] Protocol Action: URN Namespace Definition Mechanisms to BCP
Date: Fri, 16 Apr 1999 14:56:34 -0400
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: The IESG <iesg-secretary@ietf.org>
Errors-To: owner-urn-ietf@Bunyip.Com


The IESG has approved the Internet-Draft 'URN Namespace Definition
Mechanisms' <draft-ietf-urn-nid-req-08.txt> as a BCP.  This document is
the product of the Uniform Resource Names Working Group.  The IESG
contact persons are Keith Moore and Patrik Faltstrom.


Technical Summary
 
 This document describes a procedure for registering namespaces
 to be used in Uniform Resource Names.

Working Group Summary

 There was extensive discussion about these issues in the working group
 until these rules could be settled on, but the working group had
 consensus on this set of rules.

Protocol Quality

 If they are followed, these rules will be adequate to ensure proper
 assignment of namespaces and global uniqueness of URNs.

 Keith Moore reviewed the specification for IESG.



From owner-urn-ietf@Bunyip.Com  Mon Apr 19 13:24:44 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16693
	for <urn-archive@ietf.org>; Mon, 19 Apr 1999 13:24:43 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id LAA24574
	for urn-ietf-out; Mon, 19 Apr 1999 11:43:25 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA24566
	for <urn-ietf@services.bunyip.com>; Mon, 19 Apr 1999 11:43:18 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id LAA25586
	for urn-ietf@services; Mon, 19 Apr 1999 11:43:17 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA25583
	for <urn-ietf@Bunyip.Com>; Mon, 19 Apr 1999 11:43:15 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
	by astro.cs.utk.edu (cf v3.2) with ESMTP id LAA01405;
	Mon, 19 Apr 1999 11:40:20 -0400 (EDT)
Message-Id: <199904191540.LAA01405@astro.cs.utk.edu>
X-Mailer: exmh version 2.0.2 2/24/98
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Michael Mealling <michael@bailey.dscga.com>
cc: urn-ietf@Bunyip.Com
Subject: [URN] Re: a proposed technical change to the NAPTR drafts... 
In-reply-to: Your message of "Thu, 08 Apr 1999 10:18:24 EDT."
             <199904081418.KAA13463@bailey.dscga.com> 
X-SUBJECT-MSG-FROM: Michael Mealling <michael@bailey.dscga.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 19 Apr 1999 11:40:20 -0400
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>
Errors-To: owner-urn-ietf@Bunyip.Com

> Hi guys,
>   In our Last Call comments we have received some from the DNSIND folx
> concerning our use of SRV. Their suggestion is that we _not_ include
> the protocol stuff in the domain-name that is found in either
> the replacement field or the rewrite. In order to be more in line with
> what the expected behavior of SRV will be we should use the protocol
> out of our own Services field to construct the SRV.


that's silly.  part of the point of NAPTR is to allow client selection
of protocols to perform a particular service.  the proposed change would
make NAPTR much less functional.

Keith



From owner-urn-ietf@Bunyip.Com  Mon Apr 19 13:32:39 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16828
	for <urn-archive@ietf.org>; Mon, 19 Apr 1999 13:32:36 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id LAA24907
	for urn-ietf-out; Mon, 19 Apr 1999 11:54:03 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA24899
	for <urn-ietf@services.bunyip.com>; Mon, 19 Apr 1999 11:54:00 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id LAA25625
	for urn-ietf@services; Mon, 19 Apr 1999 11:53:59 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA25622
	for <urn-ietf@Bunyip.Com>; Mon, 19 Apr 1999 11:53:57 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
	by astro.cs.utk.edu (cf v3.2) with ESMTP id LAA01477;
	Mon, 19 Apr 1999 11:51:06 -0400 (EDT)
Message-Id: <199904191551.LAA01477@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: michaelm@netsol.com
cc: moore@cs.utk.edu (Keith Moore), urn-ietf@Bunyip.Com
Subject: [URN] Re: a proposed technical change to the NAPTR drafts... 
In-reply-to: Your message of "Mon, 19 Apr 1999 11:39:23 EDT."
             <199904191539.LAA03408@bailey.dscga.com> 
Date: Mon, 19 Apr 1999 11:51:06 -0400
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>
Errors-To: owner-urn-ietf@Bunyip.Com

> The main
> reason is that we are providing a NAPTR specific protocol (defined by
> the application that uses NAPTR) and that list of protocols may be 
> seperate from the list of services that may be offered at that site.

yep. and more generally for the purpose of NAPTR lookup we really might 
want to use "nonstandard" SRV labels rather than the defaults.  
so the "http" service to which NAPTR lookups are directed might be a 
completely different service than the "normal" http service.

Keith



From owner-urn-ietf@Bunyip.Com  Mon Apr 19 13:45:36 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16931
	for <urn-archive@ietf.org>; Mon, 19 Apr 1999 13:45:35 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id LAA24654
	for urn-ietf-out; Mon, 19 Apr 1999 11:48:31 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA24645
	for <urn-ietf@services.bunyip.com>; Mon, 19 Apr 1999 11:48:26 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id LAA25601
	for urn-ietf@services; Mon, 19 Apr 1999 11:48:19 -0400 (EDT)
Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA25596
	for <urn-ietf@Bunyip.Com>; Mon, 19 Apr 1999 11:48:14 -0400 (EDT)
Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id LAA03408; Mon, 19 Apr 1999 11:39:23 -0400 (EDT)
From: Michael Mealling <michael@bailey.dscga.com>
Message-Id: <199904191539.LAA03408@bailey.dscga.com>
Subject: [URN] Re: a proposed technical change to the NAPTR drafts...
In-Reply-To: <199904191540.LAA01405@astro.cs.utk.edu> from Keith Moore at "Apr 19, 99 11:40:20 am"
To: moore@cs.utk.edu (Keith Moore)
Date: Mon, 19 Apr 1999 11:39:23 -0400 (EDT)
Cc: urn-ietf@Bunyip.Com
X-Mailer: ELM [version 2.4ME+ PL31H (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Michael Mealling <michael@bailey.dscga.com>
Errors-To: owner-urn-ietf@Bunyip.Com
Content-Transfer-Encoding: 7bit

Keith Moore said this:
> > Hi guys,
> >   In our Last Call comments we have received some from the DNSIND folx
> > concerning our use of SRV. Their suggestion is that we _not_ include
> > the protocol stuff in the domain-name that is found in either
> > the replacement field or the rewrite. In order to be more in line with
> > what the expected behavior of SRV will be we should use the protocol
> > out of our own Services field to construct the SRV.
> 
> 
> that's silly.  part of the point of NAPTR is to allow client selection
> of protocols to perform a particular service.  the proposed change would
> make NAPTR much less functional.
> 

How so? As it stands the SRV draft requires the protocol to be there, which
means we're duplicating it. Actually, no it doesn't. I'm not sure if you're
right but I just realized that we have to have it in both places. The main
reason is that we are providing a NAPTR specific protocol (defined by
the application that uses NAPTR) and that list of protocols may be 
seperate from the list of services that may be offered at that site.

I.e. in the thttp example for the URN RDS the protocol _we_ put in our
services field is 'thttp'. THTTP defines how to use resolve URNs via http
so the service we ask for in the SRV would be '_http._tcp'. The distinction
between the RDS's use of 'thttp' and the SRV protocol of 'http' is an
important one for NAPTR based services to make.

Does that jive with what other folx think?  

-MM


-- 
--------------------------------------------------------------------------------
Michael Mealling	|      Vote Libertarian!       | www.rwhois.net/michael
Sr. Research Engineer   |   www.ga.lp.org/gwinnett     | ICQ#:         14198821
Network Solutions	|          www.lp.org          |  michaelm@netsol.com



From owner-urn-ietf@Bunyip.Com  Mon Apr 19 14:05:39 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17201
	for <urn-archive@ietf.org>; Mon, 19 Apr 1999 14:05:36 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id LAA24958
	for urn-ietf-out; Mon, 19 Apr 1999 11:58:16 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA24953
	for <urn-ietf@services.bunyip.com>; Mon, 19 Apr 1999 11:58:14 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id LAA25636
	for urn-ietf@services; Mon, 19 Apr 1999 11:58:13 -0400 (EDT)
Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA25633
	for <urn-ietf@Bunyip.Com>; Mon, 19 Apr 1999 11:58:08 -0400 (EDT)
Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id LAA03460; Mon, 19 Apr 1999 11:48:47 -0400 (EDT)
From: Michael Mealling <michael@bailey.dscga.com>
Message-Id: <199904191548.LAA03460@bailey.dscga.com>
Subject: [URN] Re: a proposed technical change to the NAPTR drafts...
In-Reply-To: <199904191551.LAA01477@astro.cs.utk.edu> from Keith Moore at "Apr 19, 99 11:51:06 am"
To: moore@cs.utk.edu (Keith Moore)
Date: Mon, 19 Apr 1999 11:48:46 -0400 (EDT)
Cc: michaelm@netsol.com, moore@cs.utk.edu, urn-ietf@Bunyip.Com
X-Mailer: ELM [version 2.4ME+ PL31H (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Michael Mealling <michael@bailey.dscga.com>
Errors-To: owner-urn-ietf@Bunyip.Com
Content-Transfer-Encoding: 7bit

Keith Moore said this:
> > The main
> > reason is that we are providing a NAPTR specific protocol (defined by
> > the application that uses NAPTR) and that list of protocols may be 
> > seperate from the list of services that may be offered at that site.
> 
> yep. and more generally for the purpose of NAPTR lookup we really might 
> want to use "nonstandard" SRV labels rather than the defaults.  
> so the "http" service to which NAPTR lookups are directed might be a 
> completely different service than the "normal" http service.

Yep. Unless I hear something other wise I'm going to add this reasoning
to the section of the NAPTR draft to clarify how it uses SRV. Since we
are using SRV somewhat differently than the folx in DNSIND had originally
invisioned I think a few words to that effect would be useful to the
reader. Especially since it has become obvious that SRV implementers are
making some assumptions that may not be correct for our usage.

-MM


-- 
--------------------------------------------------------------------------------
Michael Mealling	|      Vote Libertarian!       | www.rwhois.net/michael
Sr. Research Engineer   |   www.ga.lp.org/gwinnett     | ICQ#:         14198821
Network Solutions	|          www.lp.org          |  michaelm@netsol.com



From owner-urn-ietf@Bunyip.Com  Thu Apr 22 12:59:17 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22585
	for <urn-archive@ietf.org>; Thu, 22 Apr 1999 12:59:11 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id KAA15794
	for urn-ietf-out; Thu, 22 Apr 1999 10:44:38 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id KAA15789
	for <urn-ietf@services.bunyip.com>; Thu, 22 Apr 1999 10:44:27 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id KAA16779
	for urn-ietf@services; Thu, 22 Apr 1999 10:44:26 -0400 (EDT)
Received: from att.com (algw1.att.com [192.128.167.153])
	by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id KAA16776
	for <urn-ietf@bunyip.com>; Thu, 22 Apr 1999 10:44:16 -0400 (EDT)
Received: from alms2.fw.att.com by algw1.att.com (AT&T/IPNS/UPAS-1.0)
	for bunyip.com!urn-ietf
	sender att.com!jayhawk (att.com!jayhawk); Thu Apr 22 10:37 EDT 1999
Received: from qsun.ho.att.com (qsunn.ho.att.com [135.16.30.2])
	by alms2.fw.att.com (AT&T/IPNS/GW-1.0) with SMTP id KAA03468
	for <urn-ietf@Bunyip.Com>; Thu, 22 Apr 1999 10:39:42 -0400 (EDT)
Received: from schooner by qsun.ho.att.com (SMI-8.6/EMS-1.2 sol2)
	id KAA13116; Thu, 22 Apr 1999 10:43:50 -0400
From: "Ryan Moats" <jayhawk@att.com>
To: "IETF URN mailing List" <urn-ietf@Bunyip.Com>,
        "Internet Drafts Editor" <internet-drafts@ietf.org>
Subject: [URN] new IETF namespace draft -08
Date: Thu, 22 Apr 1999 09:43:24 -0500
Message-ID: <001c01be8cce$79858e20$e3c8090a@schooner.local.windrose.omaha.ne.us>
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 8.5, Build 4.71.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: "Ryan Moats" <jayhawk@att.com>
Errors-To: owner-urn-ietf@Bunyip.Com
Content-Transfer-Encoding: 7bit

Hi all-

Here is (hopefully) the final version of the IETF
namespace draft, in conformance with draft-ietf-urn-nid-req-08.

I-D editor please place this in the repository in
place of draft-ietf-urn-ietf-07.

The template is going to the urn-nid address later
this morning.

Ryan Moats







Internet-Draft                                                Ryan Moats
draft-ietf-urn-ietf-08.txt                                          AT&T
Expires in six months                                      November 1998

                   A URN Namespace for IETF Documents
                  Filename: draft-ietf-urn-ietf-08.txt


Status of This Memo

      This document is an Internet-Draft and is in full conformance with
      all provisions of Section 10 of RFC2026.

      Internet-Drafts are working documents of the Internet Engineering
      Task Force (IETF), its areas, and its working groups.  Note that
      other groups may also distribute working documents as Internet-
      Drafts.

      Internet-Drafts are draft documents valid for a maximum of six
      months and may be updated, replaced, or obsoleted by other
      documents at any time.  It is inappropriate to use Internet-
      Drafts as reference material or to cite them other than as ``work
      in progress.''

      To learn the current status of any Internet-Draft, please check
      the ``1id-abstracts.txt'' listing contained in the Internet-
      Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net
      (Europe), munnari.oz.au (Pacific Rim), ftp.ietf.org (US East
      Coast), or ftp.isi.edu (US West Coast).


Abstract

   A system for Uniform Resource Names (URNs) must be capable of
   supporting new naming systems.  As an example of proposing a new
   namespace, this document proposes the "ietf" namespace.  This
   namespace consists of the RFC family of documents (RFCs, STDs, FYIs,
   and BCPs) developed by the IETF and published by the RFC Editor, the
   minutes of working groups (WG) and birds of a feather (BOF) meetings
   that occur during IETF conferences, and the Internet Drafts published
   by the Internet Drafts Editor.  Both the current URN framework and
   URN syntax support this namespace.

1. Introduction

   This document proposes the "ietf" namespace, which consists of the
   RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the
   IETF and published by the RFC editor and the minutes of working



Expires 5/31/99                                                 [Page 1]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


   groups (WG) and birds of a feather (BOF) meetings that occur during
   IETF conferences.

   The namespace specification is for a formal namespace.

2. Specification Template

        Namespace ID:

                "ietf" requested.

        Registration Information:

                Registration version number: 1
                Registration date: 1999-04-22

        Declared registrant of the namespace:

                Ryan Moats
                jayhawk@att.com
                AT&T
                15621 Drexel Circle
                Omaha, NE 68135-2358

        Declaration of structure:

                The identifier has the following ABNF [2] specification:

                NSS = (family ":" number) / ("mtg-" number "-" wgbofname)
                      ( "id:" name)
                family = "rfc" / "std" / "fyi" / "bcp"
                number = 1*DIGIT
                wgbofname = 1*(DIGIT/ALPHA)
                name           = "draft-" draft-name "-" draft-version

                draft-name     = draft-ietf / draft-individual / draft-rfced
                draft-ietf     = "ietf-" wgbofname "-" draft-title
                draft-individual = draft-author "-" draft-title
                draft-rfced     = "rfced-" draft-title
                draft-title    = draft-namepart *( "-" draft-namepart )

                draft-author   = 1*(DIGIT/ALPHA)
                draft-nameart  = 1*(DIGIT/ALPHA)
                wgbofname      = 1*(DIGIT/ALPHA)
                number         = 1*DIGIT
                draft-version  = 2*DIGIT

                If the IESG (or it successor) adds a new document



Expires 5/31/99                                                 [Page 2]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


                series, this ABNF specification will need to be
                updated.  Further, if a working group or BOF is
                created that used characters outside the range of this
                ABNF specification, this specification will need to be
                updated.  Any system intended to resolve names for
                this namespace should be written with the awareness
                that this could occur at any time.

        Relevant ancillary documentation:

                The intended RFC document is currently
draft-ietf-urn-ietf-08.

        Identifier uniqueness considerations:

                Because the rfc-editor assigns the RFC number uniquely
                these URNs are unique.  Since the mapping between RFCs
                and other rfc-editor document series (STDs, FYIs or
                BCPs) is not necessarily one-to-one, uniqueness of
                STDs, FYIs and BCPs are defined based on the document
                mappings maintained by the RFC Editor (the index files
                "rfc-index.txt", "fyi-index.txt", "bcp-index.txt",
                "std-index.txt") are defined to be the definitive
                statement of the assignment of RFC Family URNs in this
                namespace.  The meeting minutes portion of the
                namespace is guaranteed unique because the URN
                includes the sequence number of the IETF conference.
                The document mapping maintained by the Internet Drafts
                editor ("1id-abstracts.txt") is defined as the
                definitive statement of the assignment of URNs for
                the internet draft portion of this namespace.

        Identifier persistence considerations:

                Persistence of the URNs of this namespace is
                independent of the mutability of the underlying
                documents.  A URN once assigned will never be
                reassigned to a different resource; the assignment is
                persistent and immutable.  Distinct from this, the
                resources identified as RFCs are immutable, whereas
                the other sorts of documents, STDs, FYIs, and BCPs are
                not.  They may be composites of one or more RFCs and
                the set of RFCs that includes them may change with
                time.  It is important to note that this mutability of
                some resources is independent of the immutability of
                URN assignment to a resource.

        Process of identifier assignment:




Expires 5/31/99                                                 [Page 3]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


                Assignment of URNs from this namespace occurs in three
                ways.  The first is through publication of a new RFC,
                FYI, STD or BCP is by the RFC Editor. This new document
                will have a new series number and will therefore define
                a new URN.  The document mappings maintained by the
                RFC Editor (the index files "rfc-index.txt",
                "fyi-index.txt", "bcp-index.txt" and "std-index.txt")
                are defined to be the definitive statement of the
                assignment of RFC Family URNs in this namespace.

                The second way a URN is assigned is through the filing
                of meeting minutes by a working group or birds of a
                feather as part of an IETF conference.  The list of
                minutes maintained by the IETF for each working group
                and conference in the subtree pointed at by the URL
                ftp://ietf.org/ietf/ is considered the definitive
                assignment of URNs for working group or birds of a
                feather minutes.

                The third way a URN is assigned is through the
                publication of a new internet-draft by the Internet
                Draft Editor.  This draft will have a distinct name
                (and version number) and therefore defined a new URN.
                The document mapping maintained by the Internet Drafts
                editor ("1id-abstracts.txt") is defined as the
                definitive statement of the assignment of URNs for
                this portion of the namespace.

        Process of identifier resolution:

                A mirrored copy of the underlying documentation is
                required to resolve these URNs.  Resolution via
                HTTP is done by a set of simple Perl cgi-bin
                scripts presented in Appendix A.

        Rules for Lexical Equivalence:

                The entire URN is case-insensitive.

        Conformance with URN Syntax:

                There are no additional characters reserved.

        Validation mechanism:

                None additional to resolution specified

        Scope:



Expires 5/31/99                                                 [Page 4]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


                Global.

3. Examples

   The following are examples of URNs that a resolver for this namespace
   can resolve:

           urn:ietf:rfc:2141
           urn:ietf:std:50
           urn:ietf:id:ietf-urn-ietf-06
           urn:ietf:mtg-41-urn

4. Security Considerations

   Because this namespace defines no additional reserved characters, it
   does not add any security considerations beyond those inherent from
   the existence of the reserved characters from [1].  Further, none of
   the reserved characters from [1] are used in the definition of the
   NSS. This means that resolvers for this namespace may be considered
   "secure" in the sense that any escaping of characters in the NSS MUST
   result in the resolver indicating that the URN has incorrect syntax.

5. Acknowledgments

   Thanks to various members of the URN working group for comments on
   earlier drafts of this document.  The work described in this document
   is partially supported by the National Science Foundation,
   Cooperative Agreement NCR-9218179.

6. References

   Request For Comments (RFC) and Internet Draft documents are available
   from numerous mirror sites.

         [1]         R. Moats, "URN Syntax," RFC 2141, May 5, 1997.

         [2]         D. Crocker, P. Overell, "Augmented BNF for Syntax
                     Specifications: ABNF," RFC 2234, November 1997.

7. Author's Address

   Ryan Moats
   AT&T
   15621 Drexel Circle
   Omaha, NE 68135-2358
   USA

   Phone:  +1 402 894-9456



Expires 5/31/99                                                 [Page 5]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


   EMail:  jayhawk@att.com

Appendix A.  Example Resolution Scripts

   The following scripts are examples that can be used for resolving
   URNs in this namespace.

A.1 I2C

#!/usr/local/bin/perl

use strict;

#
# this is a URN 2 URC resolver for the ietf namespace
#

my(%cite) = (
  bcp => "/ftp/rfc/bcp-index.txt",
  fyi => "/ftp/fyi/fyi-index.txt",
  id => "/ftp/internet-drafts/1id-abstracts.txt",
  rfc => "/ftp/rfc/rfc-index.txt",
  std => "/ftp/std/std-index.txt"
);
my(%number2date) = (
  44 => "99mar",
  43 => "98dec", 42 => "98aug", 41 => "98apr",
  40 => "97dec", 39 => "97aug", 38 => "97apr",
  37 => "96dec", 36 => "96jun", 35 => "96mar",
  34 => "95dec", 33 => "95jul", 32 => "95apr",
  31 => "94dec", 30 => "94jul", 29 => "94mar",
  28 => "93nov", 27 => "93jul", 26 => "93mar",
  25 => "92nov", 24 => "92jul", 23 => "92mar",
  22 => "91nov", 21 => "91jul", 20 => "91mar",
  19 => "90dec" );

my($wgpath) = "/ftp/ietf";
my($urn) = $ENV{'QUERY_STRING'};
my($host) = $ENV{'SERVER_NAME'}; #get my host name for ftp: URLs
my($accept) = $ENV{'HTTP_ACCEPT'}; #this is the "Accept:" HTTP header

(&resolveid($1), exit) if ($urn =~ /urn:ietf:id:(\S+)/i);
(&resolverfc($1, $2), exit) if ($urn =~ /urn:ietf:(\w*):(\d*)/i);
(&resolvemtg($1, $2), exit) if ($urn =~ /urn:ietf:mtg-(\d*)-(\w*)/i);
&urn_error("400 Bad Request\n");

sub resolvemtg {
  my($ietfnum, $sesnam) = @_;



Expires 5/31/99                                                 [Page 6]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


  &urn_error("404 Not Found\n") if (!defined $number2date{$ietfnum});
  my($date)=$number2date{$ietfnum};
  my($link)="$wgpath/$sesnam/$sesnam-minutes-$date.txt";
  if (-f $link) {
    print "Status:  200 OK\r\n";
    print "Content-type: text/html\r\n\r\n";
    print "<HTML>\n<TITLE>Citation for $urn</TITLE>\n";
    print "<BODY>\n";
    print "<H1><A HREF=\"$link\">$urn</A>:</H1>\n";
    print "Minutes of the $sesnam working group from the " . &end($ietfnum)
. " IETF";
    print "</BODY>\n</HTML>\n";
    return;
  }
  my($link)="$wgpath/$date/$sesnam-minutes-$date.txt";
  if (-f $link) {
    print "Status:  200 OK\r\n";
    print "Content-type: text/html\r\n\r\n";
    print "<HTML>\n<TITLE>Citation for $urn</TITLE>\n";
    print "<BODY>\n";
    print "<H1><A HREF=\"$link\">$urn</A>:</H1>\n";
    print "Minutes of the $sesnam working group from the " . &end($ietfnum)
. " IETF";
    print "</BODY>\n</HTML>\n";
    return;
  }
  &urn_error("404 Not Found\n");
}

sub end {
  my($inarg)=@_;
  return $inarg . "st" if ($inarg =~ /1$/);
  return $inarg . "nd" if ($inarg =~ /2$/);
  return $inarg . "rd" if ($inarg =~ /3$/);
  return $inarg . "th";
}

sub resolverfc {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link);
  my($scheme, $value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  if (!defined $cite{$scheme}) {
    &urn_error("404 Not Found\n");
  }

  $flag = 0;
  open(INPUT, "$cite{$scheme}");
  while (<INPUT>) {
    $flag = 1 if (/^0*$value /);



Expires 5/31/99                                                 [Page 7]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


    if ($flag == 1) {
      last if (/^$/);
      chop;
      push @bib,$_;
    }
  }

  if ($scheme ne "rfc") {
    print "Status:  200 OK\r\n";
    print "Content-type: text/html\r\n\r\n";
    $bib[0] =~ s/^[0-9]*\s*/<B>/;
    for ($i=0; $i<=$#bib; $i+=1) {
      last if ($bib[$i] =~ s/\./.<\/B>/);
    }
    for ($i=0;$i<=$#bib;$i+=1) {
      $k=$bib[$i];
      while ($k =~ /(fyi|std|rfc|bcp)([0-9]+)(.*)/i) {
        push @ref,"$1$2";
        $k=$3;
      }
      $done="";
      foreach $j (@ref) {
        next if ($done =~ $j);
        $done .= "$j ";
        $l = $j;
        $l =~ tr/A-Z/a-z/;
        $link=&make_link("$l");
        $bib[$i] =~ s/$j/<A HREF="$link">$j<\/A>/g;
      }
    }
    print "<HTML>\n<TITLE>Citation for $urn</TITLE>\n";
    print "<BODY>\n";
    $link=&make_link("$scheme$value");
    print "<H1><A HREF=\"$link\">$scheme$value</A>:</H1>\n";
    foreach $i (@bib) {
      print "$i\n";
    }
    print "</BODY>\n</HTML>\n";
  } else {
    print "Status:  200 OK\r\n";
    print "Content-type: text/html\r\n\r\n";
    $bib[0] =~ s/^[0-9]*\s*//;
    $j=0;
    for ($i=0; $i<=$#bib; $i+=1) {
      $j += ($bib[$i] =~ s/, "/, <B>"/);
      $j += ($bib[$i] =~ s/",/"<\/B>,/);
    }
    for ($i=0;$i<=$#bib;$i+=1) {



Expires 5/31/99                                                 [Page 8]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


      $k=$bib[$i];
      while ($k =~ /(fyi\s|std\s|rfc|bcp)([0-9]+)(.*)/i) {
        push @ref,"$1$2";
        $k=$3;
      }
      $done="";
      foreach $j (@ref) {
        next if ($done =~ $j);
        $done .= "$j ";
        $l = $j;
        $l =~ s/\s//g;
        $l =~ tr/A-Z/a-z/;
        $link=&make_link("$l");
        $bib[$i] =~ s/$j/<A HREF="$link">$j<\/A>/g;
      }
    }
    print "<HTML>\n<TITLE>Citation for $urn</TITLE>\n";
    print "<BODY>\n";
    $link=&make_link("$scheme$value");
    print "<H1><A HREF=\"$link\">$scheme$value</A>:</H1>\n";
    foreach $i (@bib) {
      print "$i\n";
    }
    print "</BODY>\n</HTML>\n";
  }
}

sub make_link {
  my($sc);
  my($inarg)=@_;
  ($sc=$1) if ($inarg =~ /([a-z]*)/);
  return "/$sc/$inarg.ps" if (-e "/ftp/$sc/$inarg.ps");
  return "/$sc/$inarg.html" if (-e "/ftp/$sc/$inarg.html");
  return "/$sc/$inarg.txt";
}

sub urn_error {
  my($code) = @_; #store failure code here...

  print "Status:  $code";
  print "Content-type: text/html\n\n<HTML>\n";
  print "<head><title>URN Resolution: I2C $code</title></head>\n";
  print "<BODY>\n";
  print "<h1>URN to URC resolution failed for the URN:</h1>\n";
  print "<hr><h3>$urn</h3>\n";
  print "</body>\n";
  print "</html>\n";
  exit;



Expires 5/31/99                                                 [Page 9]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


};

sub resolveid {
  my($flag,@bib,$i,$k,$j,$count,@ref);
  my($l,$link, $hdr, $done);
  my($value) = @_;
  my($scheme) = "id";

  open(INPUT, "$cite{$scheme}");
  while (<INPUT>) {
#
# capture record
#
    if ($flag == 1 || /^\s+\"/) {
      push @bib,$_;
      ($hdr = -1, $count = 0, $flag = 1) if (/^\s+\"/);
      $count++ if (/^\s+$/);
    }
    if ($count == 1) {
      $hdr = $#bib if ($hdr == -1);
    }
    if ($count == 2) {
      for ($i=0; $i<=$hdr; $i+=1) {
            if ($bib[$i] =~ /<(.*)>/) {
              $l = $1;
              if ($l eq "draft-$value.txt" || $l eq "draft-$value.ps") {
                print "Status:  200 OK\r\n";
                print "Content-type: text/html\r\n\r\n";
                print "<HTML>\n<TITLE>Citation for $urn</TITLE>\n";
                print "<BODY>\n";
                print "<a
href=\"http://blackhole.vip.att.net/internet-drafts/$l\">$l</a>:\n";
                print "<pre>\n";
                foreach $i (@bib) {
                  print "$i";
                }
                print "</pre>\n";
                print "</BODY>\n</HTML>\n";
                exit;
              }
            }
      }
      $flag = 0;
      @bib = ();
    }
  }
  &urn_error("404 Not Found\n");
}




Expires 5/31/99                                                [Page 10]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


A.2 I2L

#!/usr/local/bin/perl

use strict;

#
# this is a URN 2 URL resolver for the ietf namespace
#

my(%pathbase) = (
  rfc => "rfc/rfc",
  fyi => "fyi/fyi",
  std => "std/std",
  bcp => "bcp/bcp",
  id => "internet-drafts/draft-"
);

my(%number2date) = (
  44 => "99mar",
  43 => "98dec", 42 => "98aug", 41 => "98apr",
  40 => "97dec", 39 => "97aug", 38 => "97apr",
  37 => "96dec", 36 => "96jun", 35 => "96mar",
  34 => "95dec", 33 => "95jul", 32 => "95apr",
  31 => "94dec", 30 => "94jul", 29 => "94mar",
  28 => "93nov", 27 => "93jul", 26 => "93mar",
  25 => "92nov", 24 => "92jul", 23 => "92mar",
  22 => "91nov", 21 => "91jul", 20 => "91mar",
  19 => "90dec" );

my($wgpath) = "/ftp/ietf";
my($urn) = $ENV{'QUERY_STRING'};
my($host) = $ENV{'SERVER_NAME'}; #get my host name for ftp: URLs
my($accept) = $ENV{'HTTP_ACCEPT'}; #this is the "Accept:" HTTP header

(&resolveid($1), exit) if ($urn =~ /urn:ietf:id:(\S+)/i);
(&resolverfc($1, $2), exit) if ($urn =~ /urn:ietf:(\w*):(\d*)/i);
(&resolvemtg($1, $2), exit) if ($urn =~ /urn:ietf:mtg-(\d*)-(\w*)/i);
&urn_error("400 Bad Request\n");

sub resolvemtg {
  my($ietfnum, $sesnam) = @_;
  &urn_error("404 Not Found\n") if (!defined $number2date{$ietfnum});
  my($date)=$number2date{$ietfnum};
  my($link)="$wgpath/$sesnam/$sesnam-minutes-$date.txt";
  if (-f $link) {
    print "Status:  302 Moved temporarily\n";
    print "Location: $link\n";



Expires 5/31/99                                                [Page 11]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


    return;
  }
  my($link)="$wgpath/$date/$sesnam-minutes-$date.txt";
  if (-f $link) {
    print "Status:  302 Moved temporarily\n";
    print "Location: $link\n";
    return;
  }
  &urn_error("404 Not Found\n");
}

sub end {
  my($inarg)=@_;
  return $inarg . "st" if ($inarg =~ /1$/);
  return $inarg . "nd" if ($inarg =~ /2$/);
  return $inarg . "rd" if ($inarg =~ /3$/);
  return $inarg . "th";
}

sub resolverfc {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link);
  my($scheme, $value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  &urn_error("404 Not Found\n")if (!defined $pathbase{$scheme});
  my($txttry)="/ftp/$pathbase{$scheme}$value.txt";
  my($pstry)="/ftp/$pathbase{$scheme}$value.ps";
  my($htmltry)="/ftp/$pathbase{$scheme}$value.html";
MIME_SWITCH: {
    if ($accept =~ /application\/postscript/ && -f $pstry) {
      print "Status:  302 Moved temporarily\n";
      print "Location: http://$host/$pathbase{$scheme}$value.ps\n\n";
      last MIME_SWITCH;
    }
    if ($accept =~ /text\/html/ && -f $htmltry) {
      print "Status:  302 Moved temporarily\n";
      print "Location: http://$host/$pathbase{$scheme}$value.html\n\n";
      last MIME_SWITCH;
    }
    if ($accept =~ /\*\/\*|text\/plain/ && -f $txttry) {
      print "Status:  302 Moved temporarily\n";
      print "Location: http://$host/$pathbase{$scheme}$value.txt\n\n";
      last MIME_SWITCH;
    }
    &urn_error("404 Not Found\n");
  }
}




Expires 5/31/99                                                [Page 12]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


sub urn_error {
  my($code) = @_; #store failure code here...

  print "Status:  $code";
  print "Content-type: text/html\n\n<HTML>\n";
  print "<head><title>URN Resolution: I2L $code</title></head>\n";
  print "<BODY>\n";
  print "<h1>URN to URL resolution failed for the URN:</h1>\n";
  print "<hr><h3>$urn</h3>\n";
  print "</body>\n";
  print "</html>\n";
  exit;
}

sub resolveid {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link);
  my($scheme) = "id";
  my($value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  &urn_error("404 Not Found\n")if (!defined $pathbase{$scheme});
  my($txttry)="/ftp/$pathbase{$scheme}$value.txt";
  my($pstry)="/ftp/$pathbase{$scheme}$value.ps";
  my($htmltry)="/ftp/$pathbase{$scheme}$value.html";
MIME_SWITCH: {
    if ($accept =~ /application\/postscript/ && -f $pstry) {
      print "Status:  302 Moved temporarily\n";
      print "Location: http://$host/$pathbase{$scheme}$value.ps\n\n";
      last MIME_SWITCH;
    }
    if ($accept =~ /text\/html/ && -f $htmltry) {
      print "Status:  302 Moved temporarily\n";
      print "Location: http://$host/$pathbase{$scheme}$value.html\n\n";
      last MIME_SWITCH;
    }
    if ($accept =~ /\*\/\*|text\/plain/ && -f $txttry) {
      print "Status:  302 Moved temporarily\n";
      print "Location: http://$host/$pathbase{$scheme}$value.txt\n\n";
      last MIME_SWITCH;
    }
    &urn_error("404 Not Found\n");
  }
}

A.3 I2Ls

#!/usr/local/bin/perl




Expires 5/31/99                                                [Page 13]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


use strict;

#
# this is a URN 2 URLs resolver for the ietf namespace
#

my(@urls);

my(%pathbase) = (
  rfc => "rfc/rfc",
  fyi => "fyi/fyi",
  std => "std/std",
  bcp => "bcp/bcp",
  id => "internet-drafts/draft-"
);

my(%number2date) = (
  44 => "99mar",
  43 => "98dec", 42 => "98aug", 41 => "98apr",
  40 => "97dec", 39 => "97aug", 38 => "97apr",
  37 => "96dec", 36 => "96jun", 35 => "96mar",
  34 => "95dec", 33 => "95jul", 32 => "95apr",
  31 => "94dec", 30 => "94jul", 29 => "94mar",
  28 => "93nov", 27 => "93jul", 26 => "93mar",
  25 => "92nov", 24 => "92jul", 23 => "92mar",
  22 => "91nov", 21 => "91jul", 20 => "91mar",
  19 => "90dec" );

my($wgpath) = "/ftp/ietf";
my($urn) = $ENV{'QUERY_STRING'};
my($host) = $ENV{'SERVER_NAME'}; #get my host name for ftp: URLs
my($accept) = $ENV{'HTTP_ACCEPT'}; #this is the "Accept:" HTTP header

(&resolveid($1), exit) if ($urn =~ /urn:ietf:id:(\S+)/i);
(&resolve1($1, $2), exit) if ($urn =~ /urn:ietf:(\w*):(\d*)/i);
(&resolve2($1, $2), exit) if ($urn =~ /urn:ietf:mtg-(\d*)-(\w*)/i);
&urn_error("400 Bad Request\n");

sub resolve2 {
  my($ietfnum, $sesnam) = @_;
  &urn_error("404 Not Found\n") if (!defined $number2date{$ietfnum});
  my($date)=$number2date{$ietfnum};
  my($link)="$wgpath/$sesnam/$sesnam-minutes-$date.txt";
  if (-f $link) {
    $link=~s/^\/ftp\///;
    my($ftplink)="ftp://$host/$link";
    my($httplink)="http://$host/$link";
    my($glink)="gopher://$host:70/0/$link";



Expires 5/31/99                                                [Page 14]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


    if ($accept =~ /text\/uri-list/) { #look for text/uri-list, otherwise
text/html
      print "Status: 200 OK\n";
      print "Content-type: text/uri-list\n\n\n";
      print "#$urn\n";
      print "$ftplink\n";
      print "$httplink\n";
      print "$glink\n";
    }
    if ($accept =~ /\*\/\*|text\/html/) {
      print "Status: 200 OK\n";
      print "Content-type: text/html\n\n<HTML>\n";
      print "<head><title>URN Resolution: I2Ls</title></head>\n";
      print "<BODY>\n";
      print "<h1>URN $urn resolves to the following URLs:</h1>\n";
      print "<hr><ul>\n";
      print "<a href=\"$ftplink\">$ftplink</a>\n";
      print "<a href=\"$httplink\">$httplink</a>\n";
      print "<a href=\"$glink\">$glink</a>\n";
      print "</UL>\n</body>\n</HTML>\n";
    }
    return;
  }
  my($link)="$wgpath/$date/$sesnam-minutes-$date.txt";
  if (-f $link) {
    $link=~s/^\/ftp\///;
    my($ftplink)="ftp://$host/$link";
    my($httplink)="http://$host/$link";
    my($glink)="gopher://$host:70/0/$link";
    if ($accept =~ /text\/uri-list/) { #look for text/uri-list, otherwise
text/html
      print "Status: 200 OK\n";
      print "Content-type: text/uri-list\n\n\n";
      print "#$urn\n";
      print "$ftplink\n";
      print "$httplink\n";
      print "$glink\n";
    }
    if ($accept =~ /\*\/\*|text\/html/) {
      print "Status: 200 OK\n";
      print "Content-type: text/html\n\n<HTML>\n";
      print "<head><title>URN Resolution: I2Ls</title></head>\n";
      print "<BODY>\n";
      print "<h1>URN $urn resolves to the following URLs:</h1>\n";
      print "<hr><ul>\n";
      print "<a href=\"$ftplink\">$ftplink</a>\n";
      print "<a href=\"$httplink\">$httplink</a>\n";
      print "<a href=\"$glink\">$glink</a>\n";
      print "</UL>\n</body>\n</HTML>\n";
    }



Expires 5/31/99                                                [Page 15]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


    return;
  }
  &urn_error("404 Not Found\n");
}

sub resolve1 {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link);
  my($scheme, $value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  &urn_error("404 Not Found\n")if (!defined $pathbase{$scheme});
  my($try)="/ftp/$pathbase{$scheme}$value.txt";
  if (-f $try) {
    push(@urls, "http://$host/$pathbase{$scheme}$value.txt");
    push(@urls, "ftp://$host/$pathbase{$scheme}$value.txt");
    push(@urls, "gopher://$host:70/0/$pathbase{$scheme}$value.txt");
  }
  $try="/ftp/$pathbase{$scheme}$value.ps";
  if (-f $try) {
    push(@urls, "http://$host/$pathbase{$scheme}$value.ps");
    push(@urls, "ftp://$host/$pathbase{$scheme}$value.ps");
    push(@urls, "gopher://$host:70/0/$pathbase{$scheme}$value.ps");
  }
  $try="/ftp/$pathbase{$scheme}$value.html";
  if (-f $try) {
    push(@urls, "http://$host/$pathbase{$scheme}$value.html");
    push(@urls, "ftp://$host/$pathbase{$scheme}$value.html");
  }

  &urn_error("404 Not Found\n") if ($#urls == -1);

MIME_SWITCH: {
    if ($accept =~ /text\/uri-list/) { #look for text/uri-list, otherwise
text/html
      print "Status: 200 OK\n";
      print "Content-type: text/uri-list\n\n\n";
      print "#$urn\n";
      foreach $i (@urls) {
        print "$i\n";
      }
      last MIME_SWITCH;
    }
    if ($accept =~ /\*\/\*|text\/html/) {
      print "Status: 200 OK\n";
      print "Content-type: text/html\n\n<HTML>\n";
      print "<head><title>URN Resolution: I2Ls</title></head>\n";
      print "<BODY>\n";
      print "<h1>URN $urn resolves to the following URLs:</h1>\n";
      print "<hr><ul>\n";



Expires 5/31/99                                                [Page 16]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


      foreach $i (@urls) {
        print "<LI><A HREF=\"$i\">$i</A>\n";
      }
      print "</UL>\n</body>\n</HTML>\n";
      last MIME_SWITCH;
    }
  }
}

sub urn_error {
  my($code) = @_; #store failure code here...

  print "Status: $code";
  print "Content-type: text/html\n\n<HTML>\n";
  print "<head><title>URN Resolution: I2L $code</title></head>\n";
  print "<BODY>\n";
  print "<h1>URN to URL resolution failed for the URN:</h1>\n";
  print "<hr><h3>$urn</h3>\n";
  print "</body>\n";
  print "</html>\n";
  exit;
}

sub resolveid {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link);
  my($value) = @_;
  my($scheme) = "id";
  $scheme =~ tr/A-Z/a-z/;
  &urn_error("404 Not Found\n")if (!defined $pathbase{$scheme});
  my($try)="/ftp/$pathbase{$scheme}$value.txt";
  if (-f $try) {
    push(@urls, "http://$host/$pathbase{$scheme}$value.txt");
    push(@urls, "ftp://$host/$pathbase{$scheme}$value.txt");
    push(@urls, "gopher://$host:70/0/$pathbase{$scheme}$value.txt");
  }
  $try="/ftp/$pathbase{$scheme}$value.ps";
  if (-f $try) {
    push(@urls, "http://$host/$pathbase{$scheme}$value.ps");
    push(@urls, "ftp://$host/$pathbase{$scheme}$value.ps");
    push(@urls, "gopher://$host:70/0/$pathbase{$scheme}$value.ps");
  }
  $try="/ftp/$pathbase{$scheme}$value.html";
  if (-f $try) {
    push(@urls, "http://$host/$pathbase{$scheme}$value.html");
    push(@urls, "ftp://$host/$pathbase{$scheme}$value.html");
  }




Expires 5/31/99                                                [Page 17]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


  &urn_error("404 Not Found\n") if ($#urls == -1);

MIME_SWITCH: {
    if ($accept =~ /text\/uri-list/) { #look for text/uri-list, otherwise
text/html
      print "Status: 200 OK\n";
      print "Content-type: text/uri-list\n\n\n";
      print "#$urn\n";
      foreach $i (@urls) {
        print "$i\n";
      }
      last MIME_SWITCH;
    }
    if ($accept =~ /\*\/\*|text\/html/) {
      print "Status: 200 OK\n";
      print "Content-type: text/html\n\n<HTML>\n";
      print "<head><title>URN Resolution: I2Ls</title></head>\n";
      print "<BODY>\n";
      print "<h1>URN $urn resolves to the following URLs:</h1>\n";
      print "<hr><ul>\n";
      foreach $i (@urls) {
        print "<LI><A HREF=\"$i\">$i</A>\n";
      }
      print "</UL>\n</body>\n</HTML>\n";
      last MIME_SWITCH;
    }
  }
}

A.4 I2Ns

#!/usr/local/bin/perl

use strict;

#
# this is a URN 2 URNs resolver for the ietf namespace
#

my(%cite) = (
  rfc => "/ftp/rfc/rfc-index.txt",
  fyi => "/ftp/fyi/fyi-index.txt",
  std => "/ftp/std/std-index.txt",
  bcp => "/ftp/rfc/bcp-index.txt"
);

my(%number2date) = (
  44 => "99mar",
  43 => "98dec", 42 => "98aug", 41 => "98apr",



Expires 5/31/99                                                [Page 18]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


  40 => "97dec", 39 => "97aug", 38 => "97apr",
  37 => "96dec", 36 => "96jun", 35 => "96mar",
  34 => "95dec", 33 => "95jul", 32 => "95apr",
  31 => "94dec", 30 => "94jul", 29 => "94mar",
  28 => "93nov", 27 => "93jul", 26 => "93mar",
  25 => "92nov", 24 => "92jul", 23 => "92mar",
  22 => "91nov", 21 => "91jul", 20 => "91mar",
  19 => "90dec" );

my($wgpath) = "/ftp/ietf";
my($urn) = $ENV{'QUERY_STRING'};
my($host) = $ENV{'SERVER_NAME'}; #get my host name for ftp: URLs
my($port) = $ENV={'SERVER_PORT'};
my($accept) = $ENV{'HTTP_ACCEPT'}; #this is the "Accept:" HTTP header

(&resolve1($1, $2), exit) if ($urn =~ /urn:ietf:(\w*):(\d*)/i);
(&resolve2($1, $2), exit) if ($urn =~ /urn:ietf:mtg-(\d*)-(\w*)/i);
&urn_error("400 Bad Request\n");

sub resolve2 {
  my($ietfnum, $sesnam) = @_;
  &urn_error("404 Not Found\n") if (!defined $number2date{$ietfnum});
  my($date)=$number2date{$ietfnum};
  my($link)="$wgpath/$sesnam/$sesnam-minutes-$date.txt";
  if (-f $link) {
    if ($accept =~ /text\/uri-list/) {
        print "Status: 200 OK\n";
        print "Content-type: text/uri-list\n\n\n";
        print "#$urn\n";
        return;
    }
    if ($accept =~ /\*\/\*|text\/html/) {
      print "Status: 200 OK\n";
      print "Content-type: text/html\n\n<HTML>\n";
      print "<head><title>URN Resolution: I2Ns</title></head>\n";
      print "<BODY>\n";
      print "<h1>URN $urn resolves to the following URNs:</h1>\n";
      print "<hr><ul>\n";
      print "</UL>\n</body>\n</HTML>\n";
      return;
    }
  }
  my($link)="$wgpath/$date/$sesnam-minutes-$date.txt";
  if (-f $link) {
    if ($accept =~ /text\/uri-list/) {
        print "Status: 200 OK\n";
        print "Content-type: text/uri-list\n\n\n";
        print "#$urn\n";



Expires 5/31/99                                                [Page 19]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


        return;
    }
    if ($accept =~ /\*\/\*|text\/html/) {
        print "Status: 200 OK\n";
        print "Content-type: text/html\n\n<HTML>\n";
        print "<head><title>URN Resolution: I2Ns</title></head>\n";
        print "<BODY>\n";
        print "<h1>URN $urn resolves to the following URNs:</h1>\n";
        print "<hr><ul>\n";
        print "</UL>\n</body>\n</HTML>\n";
        return;
    }
  }
  &urn_error("404 Not Found\n");
}

sub end {
  my($inarg)=@_;
  return $inarg . "st" if ($inarg =~ /1$/);
  return $inarg . "nd" if ($inarg =~ /2$/);
  return $inarg . "rd" if ($inarg =~ /3$/);
  return $inarg . "th";
}

sub resolve1 {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link);
  my($scheme, $value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  if (!defined $cite{$scheme}) {
    &urn_error("404 Not Found\n");
  }

  $flag = 0;
  open(INPUT, "$cite{$scheme}");
  while (<INPUT>) {
    $flag = 1 if (/^0*$value /);
    if ($flag == 1) {
      last if (/^$/);
      chop;
      push @bib,$_;
    }
  }

  $k=join " ",@bib;
  while ($k =~ /(\S*)\s*(fyi|std|rfc|bcp)\s*([0-9]+)(.*)/i) {
    $k=$4;
    $a=$2; $b=$3;



Expires 5/31/99                                                [Page 20]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


    if (($a ne $scheme || $b ne $value) && ($1 !~ /obso/i)){
      $a =~ tr/A-Z/a-z/;
      $b =~ s/^0*//;
      push @ref,"urn:ietf:$a:$b";
    }
  }

MIME_SWITCH: {
    if ($accept =~ /text\/uri-list/) {
        print "Status: 200 OK\n";
        print "Content-type: text/uri-list\n\n\n";
        print "#$urn\n";
        foreach $i (@ref) {
            print "$i\n";
        }
        last MIME_SWITCH;
    }
  if ($accept =~ /\*\/\*|text\/html/) {
    print "Status: 200 OK\n";
    print "Content-type: text/html\n\n<HTML>\n";
    print "<head><title>URN Resolution: I2Ns</title></head>\n";
    print "<BODY>\n";
    print "<h1>URN $urn resolves to the following URNs:</h1>\n";
    print "<hr><ul>\n";
        foreach $i (@ref) {
            print "<li>$i: Click to resolve using\n";
            print "<a
href=\"http://$host:$port/uri-res/I2C?$i\">I2C</a>,\n";
            print "<a
href=\"http://$host:$port/uri-res/I2L?$i\">I2L</a>,\n";
            print "<a
href=\"http://$host:$port/uri-res/I2Ls?$i\">I2Ls</a>,\n";
            print "<a
href=\"http://$host:$port/uri-res/I2R?$i\">I2R</a>,\n";
            print "<a
href=\"http://$host:$port/uri-res/I2Rs?$i\">I2Rs</a>\n";
        }
    print "</UL>\n</body>\n</HTML>\n";
  }
}
}

sub make_link {
  my($sc);
  my($inarg)=@_;
  ($sc=$1) if ($inarg =~ /([a-z]*)/);
  return "/$sc/$inarg.ps" if (-e "/ftp/$sc/$inarg.ps");
  return "/$sc/$inarg.html" if (-e "/ftp/$sc/$inarg.html");
  return "/$sc/$inarg.txt";
}

sub urn_error {
  my($code) = @_; #store failure code here...



Expires 5/31/99                                                [Page 21]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


  print "Status: $code";
  print "Content-type: text/html\n\n<HTML>\n";
  print "<head><title>URN Resolution: I2Ns $code</title></head>\n";
  print "<BODY>\n";
  print "<h1>URN to URN resolution failed for the URN:</h1>\n";
  print "<hr><h3>$urn</h3>\n";
  print "</body>\n";
  print "</html>\n";
  exit;
};

A.5 I2R

#!/usr/local/bin/perl

use strict;

#
# this is a URN 2 resource resolver for the ietf namespace
#

my(%pathbase) = (
  rfc => "rfc/rfc",
  fyi => "fyi/fyi",
  std => "std/std",
  bcp => "bcp/bcp",
  id => "internet-drafts/draft-"
);

my(%number2date) = (
  44 => "99mar",
  43 => "98dec", 42 => "98aug", 41 => "98apr",
  40 => "97dec", 39 => "97aug", 38 => "97apr",
  37 => "96dec", 36 => "96jun", 35 => "96mar",
  34 => "95dec", 33 => "95jul", 32 => "95apr",
  31 => "94dec", 30 => "94jul", 29 => "94mar",
  28 => "93nov", 27 => "93jul", 26 => "93mar",
  25 => "92nov", 24 => "92jul", 23 => "92mar",
  22 => "91nov", 21 => "91jul", 20 => "91mar",
  19 => "90dec" );

my($wgpath) = "/ftp/ietf";
my($urn) = $ENV{'QUERY_STRING'};
my($host) = $ENV{'SERVER_NAME'}; #get my host name for ftp: URLs
my($accept) = $ENV{'HTTP_ACCEPT'}; #this is the "Accept:" HTTP header

print "$urn\n";
(&resolveid($1), exit) if ($urn =~ /urn:ietf:id:(\S+)/i);



Expires 5/31/99                                                [Page 22]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


(&resolve1($1, $2), exit) if ($urn =~ /urn:ietf:(\w*):(\d*)/i);
(&resolve2($1, $2), exit) if ($urn =~ /urn:ietf:mtg-(\d*)-(\w*)/i);
&urn_error("400 Bad Request\n");

sub resolve2 {
  my($ietfnum, $sesnam) = @_;
  &urn_error("404 Not Found\n") if (!defined $number2date{$ietfnum});
  my($date)=$number2date{$ietfnum};
  my($link)="$wgpath/$sesnam/$sesnam-minutes-$date.txt";
  if (-f $link) {
      print "Status:  200 OK\n";
      print "Content-type: text/plain\n\n";
      open(FILE, "$link");
      while (<FILE>) {
          print $_;
      }
      close FILE;
    return;
  }
  my($link)="$wgpath/$date/$sesnam-minutes-$date.txt";
  if (-f $link) {
      print "Status:  200 OK\n";
      print "Content-type: text/plain\n\n";
      open(FILE, "$link");
      while (<FILE>) {
          print $_;
      }
      close FILE;
    return;
  }
  &urn_error("404 Not Found\n");
}

sub end {
  my($inarg)=@_;
  return $inarg . "st" if ($inarg =~ /1$/);
  return $inarg . "nd" if ($inarg =~ /2$/);
  return $inarg . "rd" if ($inarg =~ /3$/);
  return $inarg . "th";
}

sub resolve1 {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link);
  my($scheme, $value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  &urn_error("404 Not Found\n")if (!defined $pathbase{$scheme});
  my($txttry)="/ftp/$pathbase{$scheme}$value.txt";



Expires 5/31/99                                                [Page 23]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


  my($pstry)="/ftp/$pathbase{$scheme}$value.ps";
  my($htmltry)="/ftp/$pathbase{$scheme}$value.html";
MIME_SWITCH: {
    if ($accept =~ /application\/postscript/ && -f $pstry) {
      print "Status:  200 OK\n";
      print "Content-type: application/postscript\n\n";
      open(FILE, "$pstry");
      while (<FILE>) {
          print $_;
      }
      close FILE;
      last MIME_SWITCH;
    }
    if ($accept =~ /text\/html/ && -f $htmltry) {
        print "Status:  200 OK\n";
        print "Content-type: text/html\n\n";
        open(FILE, "$htmltry");
        while (<FILE>) {
            print $_;
        }
        close FILE;
        last MIME_SWITCH;
    }
    if ($accept =~ /\*\/\*|text\/plain/ && -f $txttry) {
        print "Status:  200 OK\n";
        print "Content-type: text/plain\n\n";
        open(FILE, "$txttry");
        while (<FILE>) {
            print $_;
        }
        close FILE;
        last MIME_SWITCH;
    }
    &urn_error("404 Not Found\n");
  }
}

sub resolveid {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link);
  my($scheme) = "id";
  my($value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  &urn_error("404 Not Found\n")if (!defined $pathbase{$scheme});
  my($txttry)="/ftp/$pathbase{$scheme}$value.txt";
  my($pstry)="/ftp/$pathbase{$scheme}$value.ps";
  my($htmltry)="/ftp/$pathbase{$scheme}$value.html";
MIME_SWITCH: {



Expires 5/31/99                                                [Page 24]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


    if ($accept =~ /application\/postscript/ && -f $pstry) {
      print "Status:  200 OK\n";
      print "Content-type: application/postscript\n\n";
      open(FILE, "$pstry");
      while (<FILE>) {
          print $_;
      }
      close FILE;
      last MIME_SWITCH;
    }
    if ($accept =~ /text\/html/ && -f $htmltry) {
        print "Status:  200 OK\n";
        print "Content-type: text/html\n\n";
        open(FILE, "$htmltry");
        while (<FILE>) {
            print $_;
        }
        close FILE;
        last MIME_SWITCH;
    }
    if ($accept =~ /\*\/\*|text\/plain/ && -f $txttry) {
        print "Status:  200 OK\n";
        print "Content-type: text/plain\n\n";
        open(FILE, "$txttry");
        while (<FILE>) {
            print $_;
        }
        close FILE;
        last MIME_SWITCH;
    }
    &urn_error("404 Not Found\n");
  }
}

sub urn_error {
  my($code) = @_; #store failure code here...

  print "Status:  $code";
  print "Content-type: text/html\n\n<HTML>\n";
  print "<head><title>URN Resolution: I2R $code</title></head>\n";
  print "<BODY>\n";
  print "<h1>URN to URL resolution failed for the URN:</h1>\n";
  print "<hr><h3>$urn</h3>\n";
  print "</body>\n";
  print "</html>\n";
  exit;
}




Expires 5/31/99                                                [Page 25]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


A.6 I2Rs

#!/usr/local/bin/perl

use strict;

#
# this is a URN 2 resources resolver for the ietf namespace
#

my(@urls);

my(%pathbase) = (
  rfc => "rfc/rfc",
  fyi => "fyi/fyi",
  std => "std/std",
  bcp => "bcp/bcp",
  id => "internet-drafts/draft-"
);

my(%number2date) = (
  44 => "99mar",
  43 => "98dec", 42 => "98aug", 41 => "98apr",
  40 => "97dec", 39 => "97aug", 38 => "97apr",
  37 => "96dec", 36 => "96jun", 35 => "96mar",
  34 => "95dec", 33 => "95jul", 32 => "95apr",
  31 => "94dec", 30 => "94jul", 29 => "94mar",
  28 => "93nov", 27 => "93jul", 26 => "93mar",
  25 => "92nov", 24 => "92jul", 23 => "92mar",
  22 => "91nov", 21 => "91jul", 20 => "91mar",
  19 => "90dec" );

my($wgpath) = "/ftp/ietf";
my($urn) = $ENV{'QUERY_STRING'};
my($host) = $ENV{'SERVER_NAME'}; #get my host name for ftp: URLs
my($accept) = $ENV{'HTTP_ACCEPT'}; #this is the "Accept:" HTTP header

(&resolveid($1), exit) if ($urn =~ /urn:ietf:id:(\s*)/i);
(&resolve1($1, $2), exit) if ($urn =~ /urn:ietf:(\w*):(\d*)/i);
(&resolve2($1, $2), exit) if ($urn =~ /urn:ietf:mtg-(\d*)-(\w*)/i);
&urn_error("400 Bad Request\n");

sub resolve2 {
  my($ietfnum, $sesnam) = @_;
  my(@vers,$i);
  &urn_error("404 Not Found\n") if (!defined $number2date{$ietfnum});
  my($date)=$number2date{$ietfnum};
  my($link)="$wgpath/$sesnam/$sesnam-minutes-$date.txt";



Expires 5/31/99                                                [Page 26]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


  if (-f $link) {
      push(@vers,$link);
  }
  $link="$wgpath/$date/$sesnam-minutes-$date.txt";
  if (-f $link) {
      push(@vers,$link);
  }
  &urn_error("404 Not Found\n") if ($#vers==-1);

  print "Status: 200 OK\n";
  print "Content-type: multipart/alternative; boundary=endpart\n\n";
  foreach $i (@vers) {
      print "--endpart\n";
      if ($i =~ /html$/) {
          print "Content-Type: text/html\n\n";
      }
      if ($i =~ /txt$/) {
          print "Content-Type: text/plain\n\n";
      }
      if ($i =~ /ps$/) {
          print "Content-Type: application/postscript\n\n";
      }
      open(FILE, "$i");
      while (<FILE>) {
          print "$_";
      }
      close FILE;
  }
  print "--endpart\n";
}

sub resolve1 {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link,@vers);
  my($scheme, $value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  &urn_error("404 Not Found\n")if (!defined $pathbase{$scheme});
  my($try)="/ftp/$pathbase{$scheme}$value.txt";
  if (-f $try) {
      push(@vers, $try);
  }
  $try="/ftp/$pathbase{$scheme}$value.ps";
  if (-f $try) {
      push(@vers, $try);
  }
  $try="/ftp/$pathbase{$scheme}$value.html";
  if (-f $try) {
      push(@vers, $try);



Expires 5/31/99                                                [Page 27]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


  }
  print "Status: 200 OK\n";
  print "Content-type: multipart/alternative; boundary=endpart\n\n";
  foreach $i (@vers) {
      print "--endpart\n";
      if ($i =~ /html$/) {
          print "Content-Type: text/html\n\n";
      }
      if ($i =~ /txt$/) {
          print "Content-Type: text/plain\n\n";
      }
      if ($i =~ /ps$/) {
          print "Content-Type: application/postscript\n\n";
      }
      open(FILE, "$i");
      while (<FILE>) {
          print "$_";
      }
      close FILE;
  }
  print "--endpart\n";
}

sub resolveid {
  my($flag,@bib,$i,$k,$j,$done,@ref);
  my($l,$link,@vers);
  my($scheme) = "id";
  my($value) = @_;
  $scheme =~ tr/A-Z/a-z/;
  &urn_error("404 Not Found\n")if (!defined $pathbase{$scheme});
  my($try)="/ftp/$pathbase{$scheme}$value.txt";
  if (-f $try) {
      push(@vers, $try);
  }
  $try="/ftp/$pathbase{$scheme}$value.ps";
  if (-f $try) {
      push(@vers, $try);
  }
  $try="/ftp/$pathbase{$scheme}$value.html";
  if (-f $try) {
      push(@vers, $try);
  }
  print "Status: 200 OK\n";
  print "Content-type: multipart/alternative; boundary=endpart\n\n";
  foreach $i (@vers) {
      print "--endpart\n";
      if ($i =~ /html$/) {
          print "Content-Type: text/html\n\n";



Expires 5/31/99                                                [Page 28]





INTERNET DRAFT     A URN Namespace for IETF Documents      November 1998


      }
      if ($i =~ /txt$/) {
          print "Content-Type: text/plain\n\n";
      }
      if ($i =~ /ps$/) {
          print "Content-Type: application/postscript\n\n";
      }
      open(FILE, "$i");
      while (<FILE>) {
          print "$_";
      }
      close FILE;
  }
  print "--endpart\n";
}
sub urn_error {
  my($code) = @_; #store failure code here...

  print "Status: $code";
  print "Content-type: text/html\n\n<HTML>\n";
  print "<head><title>URN Resolution: I2Rs $code</title></head>\n";
  print "<BODY>\n";
  print "<h1>URN to URL resolution failed for the URN:</h1>\n";
  print "<hr><h3>$urn</h3>\n";
  print "</body>\n";
  print "</html>\n";
  exit;
}























Expires 5/31/99                                                [Page 29]





From owner-urn-ietf@Bunyip.Com  Fri Apr 23 11:15:01 1999
Received: from services.bunyip.com ([192.77.55.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20171
	for <urn-archive@ietf.org>; Fri, 23 Apr 1999 11:15:00 -0400 (EDT)
Received: (from daemon@localhost)
	by services.bunyip.com (8.8.5/8.8.5) id JAA00451
	for urn-ietf-out; Fri, 23 Apr 1999 09:58:43 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2])
	by services.bunyip.com (8.8.5/8.8.5) with ESMTP id JAA00446
	for <urn-ietf@services.bunyip.com>; Fri, 23 Apr 1999 09:58:41 -0400 (EDT)
Received: (from daemon@localhost)
	by mocha.bunyip.com (8.8.5/8.8.5) id JAA23711
	for urn-ietf@services; Fri, 23 Apr 1999 09:58:40 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id JAA23708
	for <urn-ietf@bunyip.com>; Fri, 23 Apr 1999 09:58:37 -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 JAA17115;
	Fri, 23 Apr 1999 09:58:33 -0400 (EDT)
Message-Id: <199904231358.JAA17115@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: urn-ietf@Bunyip.Com
From: Internet-Drafts@ietf.org
Subject: [URN] I-D ACTION:draft-ietf-urn-ietf-08.txt
Date: Fri, 23 Apr 1999 09:58:32 -0400
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org
Errors-To: owner-urn-ietf@Bunyip.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 URN Namespace for IETF Documents
	Author(s)	: R. Moats
	Filename	: draft-ietf-urn-ietf-08.txt
	Pages		: 29
	Date		: 22-Apr-99
	
A system for Uniform Resource Names (URNs) must be capable of
supporting new naming systems.  As an example of proposing a new
namespace, this document proposes the 'ietf' namespace.  This
namespace consists of the RFC family of documents (RFCs, STDs, FYIs,
and BCPs) developed by the IETF and published by the RFC Editor, the
minutes of working groups (WG) and birds of a feather (BOF) meetings
that occur during IETF conferences, and the Internet Drafts published
by the Internet Drafts Editor.  Both the current URN framework and
URN syntax support this namespace.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-ietf-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-ietf-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-ietf-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:	<19990422140839.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-ietf-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-urn-ietf-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990422140839.I-D@ietf.org>

--OtherAccess--

--NextPart--





Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id OAA03724 for urn-ietf-out; Tue, 6 Apr 1999 14:50:52 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA03717 for <urn-ietf@services.bunyip.com>; Tue, 6 Apr 1999 14:50:47 -0400 (EDT)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id OAA10839 for urn-ietf@services; Tue, 6 Apr 1999 14:50:46 -0400 (EDT)
Received: from email.centraal.com ([216.33.4.99]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA10832 for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 14:50:34 -0400 (EDT)
Received: by mail.centraal.com with Internet Mail Service (5.5.2448.0) id <2LPGVCJS>; Tue, 6 Apr 1999 11:49:49 -0700
Message-ID: <7D28C07629C9D211A1CC00500403ADD41D3754@mail.centraal.com>
From: Yves Arrouye <Yves@centraal.com>
To: urn-ietf@bunyip.com
Subject: RE: [URN] Microsoft & URNs
Date: Tue, 6 Apr 1999 11:49:49 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Yves Arrouye <Yves@centraal.com>
Errors-To: owner-urn-ietf@Bunyip.Com

> author describes writing a simple document in Word and saving 
> it as HTML.
> The opening of the resulting document looks like this:
> 
> 	<html xmlns:v="urn:schemas-microsoft-com:vml"
>      xmlns:o="urn:schemas-microsoft-com:office:office"
>      xmlns:w="urn:schemas-microsoft-com:office:word" 
>      xmlns="-//W3C//DTD HTML 4.0//EN">
> 
> I found it intriguing that they're using URNs instead of URLs 
> to define
> name spaces.

Though the last time I checked, they didn't provide a way to get to their
document through a standard URN resolution mechanism. So it's quite useless
right now.

Yves.



Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id LAA00481 for urn-ietf-out; Tue, 6 Apr 1999 11:27:54 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA00475 for <urn-ietf@services.bunyip.com>; Tue, 6 Apr 1999 11:27:50 -0400 (EDT)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id LAA09631 for urn-ietf@services; Tue, 6 Apr 1999 11:27:46 -0400 (EDT)
Received: from library.berkeley.edu (library.Berkeley.EDU [128.32.224.55]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA09628 for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 11:27:43 -0400 (EDT)
Received: from jerome (doenx-380-8.Lib.Berkeley.EDU [128.32.224.162]) by library.berkeley.edu (8.9.1a/8.9.1) with SMTP id IAA12831 for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 08:33:01 -0700 (PDT)
Message-Id: <3.0.5.32.19990406081530.00983380@library.berkeley.edu>
X-Sender: jmcdonou@library.berkeley.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Tue, 06 Apr 1999 08:15:30 -0700
To: urn-ietf@bunyip.com
From: Jerome McDonough <jmcdonou@library.berkeley.edu>
Subject: [URN] Microsoft & URNs
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Jerome McDonough <jmcdonou@library.berkeley.edu>
Errors-To: owner-urn-ietf@Bunyip.Com

Thought this might interest you all.  In an article discussing XML's
use in Microsoft Office 2000
(http://webreview.com/wr/pub/1999/04/02/edge/index.html?wwwrrr_19990402.txt)
, the
author describes writing a simple document in Word and saving it as HTML.
The opening of the resulting document looks like this:

	<html xmlns:v="urn:schemas-microsoft-com:vml"
     xmlns:o="urn:schemas-microsoft-com:office:office"
     xmlns:w="urn:schemas-microsoft-com:office:word" 
     xmlns="-//W3C//DTD HTML 4.0//EN">

I found it intriguing that they're using URNs instead of URLs to define
name spaces.



Jerome McDonough -- jmcdonou@library.Berkeley.EDU  |  (......)
Library Systems Office, 386 Doe, U.C. Berkeley     |  \ *  * /
Berkeley, CA 94720-6000    (510) 642-5168          |  \  <>  /
"Well, it looks easy enough...."                   |   \ -- /  SGNORMPF!!!
         -- From the Famous Last Words file        |    ||||



Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id DAA25060 for urn-ietf-out; Tue, 6 Apr 1999 03:05:35 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id DAA25055 for <urn-ietf@services.bunyip.com>; Tue, 6 Apr 1999 03:05:32 -0400 (EDT)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id DAA06253 for urn-ietf@services; Tue, 6 Apr 1999 03:05:31 -0400 (EDT)
Received: from lis.yonsei.ac.kr ([165.132.148.111]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id DAA06250 for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 03:05:17 -0400 (EDT)
Received: from lis.yonsei.ac.kr ([165.132.148.191]) by lis.yonsei.ac.kr (8.9.1a-H1/8.9.1) with ESMTP id QAA04024 for <urn-ietf@bunyip.com>; Tue, 6 Apr 1999 16:04:38 +0900 (KST)
Message-ID: <3709B1DB.9A9A456@lis.yonsei.ac.kr>
Date: Tue, 06 Apr 1999 16:03:55 +0900
From: lislee <lislee@lis.yonsei.ac.kr>
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: urn-ietf@bunyip.com
Subject: [URN] about reserved character slash('/')
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: lislee <lislee@lis.yonsei.ac.kr>
Errors-To: owner-urn-ietf@Bunyip.Com

I'm a student interested in URN.

In RFC2141(URN Syntax), the character slash('/') is a reserved
character, so it cannot be used in URN syntax.

But in DOI(Digital Object Identifier) or Handle System, the character
slash is used.

I think the character slash is useful in distinguishing something from
others, or  expressing hierarchical relation. For example,
<urn:USA:university/UCLA/1999-1>
So I think the character slash is to be freed from reserved character.

How about your opinion?



Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id TAA08205 for urn-ietf-out; Fri, 2 Apr 1999 19:10:51 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id TAA08200 for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 19:10:49 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id TAA28999 for urn-ietf@services; Fri, 2 Apr 1999 19:10:48 -0500 (EST)
Received: from LOGOS.CC.BRANDEIS.EDU (logos.cc.brandeis.edu [129.64.1.2]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id TAA28995; Fri, 2 Apr 1999 19:10:45 -0500 (EST)
Received: from mantiscorp.com (mantiscorp.com) by LOGOS.CC.BRANDEIS.EDU (PMDF V5.0-8 #17137) id <01J9KH8IGRLCBNMXQS@LOGOS.CC.BRANDEIS.EDU>; Fri, 02 Apr 1999 19:11:04 -0500 (EST)
Date: Fri, 02 Apr 1999 19:09:59 -0500
From: "Aaron E. Walsh" <aaron@mantiscorp.com>
Subject: Re: [URN] status
To: Leslie Daigle <leslie@bunyip.com>
Cc: urn-ietf@bunyip.com
Message-id: <37055C57.93EF0750@mantiscorp.com>
Organization: Mantis Development Corp.
MIME-version: 1.0
X-Mailer: Mozilla 4.51 [en]C-compaq  (Win98; I)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: <Pine.SUN.3.95.990401071901.17797A-100000@buzz.Bunyip.Com>
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: "Aaron E. Walsh" <aaron@mantiscorp.com>
Errors-To: owner-urn-ietf@Bunyip.Com

Thanks Leslie.. that was the pointer I needed :)

Aaron

Leslie Daigle wrote:
> 
> Howdy,
> 
> On Wed, 31 Mar 1999, Aaron E. Walsh wrote:
> > I'm preparing now to register a few URN namespaces, and wonder if you or
> > others could point me towards the proper documents to file? I understand
> > this isn't as simple a process as simply submitting an online form, as
> > we do for domains through InterNic, so want to make sure I'm heading in
> > the right direction :)
> 
> The procedure is outlined in
> 
>         draft-ietf-urn-nid-req-xx.txt
> 
> which is being finalized currently.  I.e., that document lays out the
> mechanism, which should be "live" within the next little while.
> 
> Leslie.
> 
> ------------------------------------------------------------------------------
> 
>   "Never confuse                               Leslie Daigle
>      an appreciation of the simple
>               for                              Bunyip Information Systems Inc.
>      a lack of understanding of the complex."  +1 514 285 0088
>                   -- ThinkingCat               leslie@bunyip.com
> 
> ------------------------------------------------------------------------------



Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id SAA08024 for urn-ietf-out; Fri, 2 Apr 1999 18:49:08 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id SAA08010 for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 18:48:13 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id SAA28943 for urn-ietf@services; Fri, 2 Apr 1999 18:48:12 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id SAA28940 for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 18:48:10 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11593; Fri, 2 Apr 1999 18:48:07 -0500 (EST)
Message-Id: <199904022348.SAA11593@ietf.org>
To: IETF-Announce: ;
Cc: urn-ietf@bunyip.com, lc-uri-resolution@apps.ietf.org
From: The IESG <iesg-secretary@ietf.org>
Subject: [URN] Last Call: Assignment Procedures for the URI Resolution using DNS (RFC2168) to BCP
Date: Fri, 02 Apr 1999 18:48:07 -0500
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: The IESG <iesg-secretary@ietf.org>
Errors-To: owner-urn-ietf@Bunyip.Com

The IESG has received a request from the Uniform Resource Names Working
Group to consider the publication of the following:

Assignment Procedures for the URI Resolution using DNS (RFC2168)
<draft-ietf-urn-net-procedures-02.txt> as a BCP. 

Resolution of Uniform Resource Identifiers using the Domain Name
System <draft-ietf-urn-dns-rds-00.txt> as a Proposed Standard.  

The Naming Authority Pointer (NAPTR) DNS Resource Record
<draft-ietf-urn-naptr-rr-02.txt> as a Proposed Standard.  


The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by April 16, 1999.

The Applications Area Directors request that any Last Call comments
on these documents, be CC'ed to <lc-uri-resolution@apps.ietf.org>.


Files can be obtained via:
http://www.ietf.org/internet-drafts/draft-ietf-urn-net-procedures-02.txt
http://www.ietf.org/internet-drafts/draft-ietf-urn-dns-rds-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.txt



Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id SAA07980 for urn-ietf-out; Fri, 2 Apr 1999 18:43:51 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id SAA07972 for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 18:42:55 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id SAA28925 for urn-ietf@services; Fri, 2 Apr 1999 18:42:55 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id SAA28921 for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 18:42:52 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11210; Fri, 2 Apr 1999 18:42:49 -0500 (EST)
Message-Id: <199904022342.SAA11210@ietf.org>
To: IETF-Announce: ;
Cc: urn-ietf@bunyip.com, lc-uri-resolution@apps.ietf.org
From: The IESG <iesg-secretary@ietf.org>
Subject: [URN] Last Call: Assignment Procedures for the URI Resolution using DNS (RFC2168) to BCP
Date: Fri, 02 Apr 1999 18:42:49 -0500
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: The IESG <iesg-secretary@ietf.org>
Errors-To: owner-urn-ietf@Bunyip.Com

The IESG has received a request from the Uniform Resource Names Working
Group to consider the publication of the following:

Assignment Procedures for the URI Resolution using DNS (RFC2168) <draft-ietf-urn-net-procedures-02.txt> as a BCP. 

Resolution of Uniform Resource Identifiers using the Domain Name System <draft-ietf-urn-dns-rds-00.txt> as a Proposed Standard.  

The Naming Authority Pointer (NAPTR) DNS Resource Record <draft-ietf-urn-naptr-rr-02.txt> as a Proposed Standard.  


The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by April 16, 1999.

The Applications Area Directors request that any Last Call comments
on these documents, be CC'ed to <lc-uri-resolution@apps.ietf.org>.


Files can be obtained via:
http://www.ietf.org/internet-drafts/draft-ietf-urn-net-procedures-02.txt
http://www.ietf.org/internet-drafts/draft-ietf-urn-dns-rds-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.txt



Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id RAA07181 for urn-ietf-out; Fri, 2 Apr 1999 17:25:30 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id RAA07176 for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 17:25:27 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id RAA28632 for urn-ietf@services; Fri, 2 Apr 1999 17:25:27 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id RAA28629 for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 17:25:25 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06520; Fri, 2 Apr 1999 17:25:19 -0500 (EST)
Message-Id: <199904022225.RAA06520@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: urn-ietf@bunyip.com
From: Internet-Drafts@ietf.org
Subject: [URN] I-D ACTION:draft-ietf-urn-naptr-rr-02.txt
Date: Fri, 02 Apr 1999 17:25:19 -0500
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org
Errors-To: owner-urn-ietf@Bunyip.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           : The Naming Authority Pointer (NAPTR) DNS
			  Resource Record
	Author(s)	: M. Mealling, R. Daniel
	Filename	: draft-ietf-urn-naptr-rr-02.txt
	Pages		: 15
	Date		: 01-Apr-99
	
This document describes a DNS Resource Record (RR) which specifies a rewrite rule that, when applied to an existing string,
will produce a new domain. Reasons for rewriting a domain
vary from URN Resource Discovery Systems to moving out-of-date
services to new domains.
 
This document updates those portions of RFC2168 specifically
dealing with the definition of the NAPTR record.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.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-naptr-rr-02.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-naptr-rr-02.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:	<19990401152434.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-naptr-rr-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-urn-naptr-rr-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990401152434.I-D@ietf.org>

--OtherAccess--

--NextPart--




Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id QAA06416 for urn-ietf-out; Fri, 2 Apr 1999 16:22:48 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id QAA06408 for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 16:22:45 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id QAA28311 for urn-ietf@services; Fri, 2 Apr 1999 16:22:44 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id QAA28308 for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 16:22:42 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04013; Fri, 2 Apr 1999 16:22:38 -0500 (EST)
Message-Id: <199904022122.QAA04013@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: urn-ietf@bunyip.com
From: Internet-Drafts@ietf.org
Subject: [URN] I-D ACTION:draft-ietf-urn-nid-req-08.txt
Date: Fri, 02 Apr 1999 16:22:37 -0500
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org
Errors-To: owner-urn-ietf@Bunyip.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-nid-req-08.txt
	Pages		: 14
	Date		: 31-Mar-99
	
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 ([RFC2168, RFC2169]).
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'.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-nid-req-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-nid-req-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-nid-req-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:	<19990401090834.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-nid-req-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-urn-nid-req-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990401090834.I-D@ietf.org>

--OtherAccess--

--NextPart--




Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id GAA01854 for urn-ietf-out; Fri, 2 Apr 1999 06:46:57 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id GAA01849 for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 06:46:55 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id GAA27043 for urn-ietf@services; Fri, 2 Apr 1999 06:46:54 -0500 (EST)
Received: from lis.yonsei.ac.kr (lis.yonsei.ac.kr [165.132.148.111]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id GAA27040 for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 06:46:47 -0500 (EST)
Received: from lis.yonsei.ac.kr ([165.132.148.191]) by lis.yonsei.ac.kr (8.9.1a-H1/8.9.1) with ESMTP id UAA29299; Fri, 2 Apr 1999 20:46:15 +0900 (KST)
Message-ID: <3704ADDC.BEBC537@lis.yonsei.ac.kr>
Date: Fri, 02 Apr 1999 20:45:33 +0900
From: lislee <lislee@lis.yonsei.ac.kr>
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: urn-ietf@bunyip.com, lislee@lis.yonsei.ac.kr
Subject: [URN] about RFC2168
Content-Type: multipart/alternative; boundary="------------CCBACF9DD16F9659487608BE"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: lislee <lislee@lis.yonsei.ac.kr>
Errors-To: owner-urn-ietf@Bunyip.Com

--------------CCBACF9DD16F9659487608BE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I'm a student interested in URN system, especially in URN resolution
system.
I am preparing for my master's thesis about URN system.

After reading    RFC2168(Resolution of Uniform Resource Identifiers
using the Domain Name System)  ,
and    Internet Draft(The Naming Authority Pointer (NAPTR) DNS Resource
Record)   , I can roughly
understand how to resolve URN using NAPTR RR.

I have some question about RFC2168.
Anybody who knows about my question tell me some advice.

<In RFC2168>
Example 2
---------

   Consider a URN namespace based on MIME Content-Ids. The URN might
   look like this:

                 urn:cid:199606121851.1@mordred.gatech.edu

   (Note that this example is chosen for pedagogical purposes, and does
   not conform to the recently-approved CID URL scheme.)

   The first step in the resolution process is to find out about the CID

   namespace. The namespace identifier, cid, is extracted from the URN,
   prepended to urn.net, and the NAPTR for cid.urn.net looked up. It
   might return records of the form:

 cid.urn.net
  ;;       order pref flags service        regexp           replacement
   IN NAPTR 100   10   ""  ""  "/urn:cid:.+@([^\.]+\.)(.*)$/\2/i"    .

   We have only one NAPTR response, so ordering the responses is not a
   problem.  The replacement field is empty, so we check the regexp
   field and use the pattern provided there. We apply that regexp to the

   entire URN to see if it matches, which it does.  The \2 part of the
   substitution expression returns the string "gatech.edu". Since the
   flags field does not contain "s" or "a", the lookup is not terminal
   and our next probe to DNS is for more NAPTR records:
   lookup(query=NAPTR, "gatech.edu").
<In RFC2168>


The NAPTR record has a string 'cid', so 'cid.urn.net' is retrived at the
1st look-up.
But I guess 'cid' is not a resolver of that URN, only a NID.
So it has no flag value, and no replacement value, but has regexp value.

And 2nd NAPTR look-up is processed with the string 'gatech.edu'.
My first question is that why the 2nd look-up is processed with
'gatech.edu', not else string?
How does the \2 part of the substitution expression return the string
"gatech.edu"?
And when the replacement field has value, and when it doesn't have
value?


I can imagine that I'll make URN as like <urn:k-univ:yonsei:d/lis/99-1>.

'k-univ' means "Korean Universities", and 'yonsei' means "Yonsei
University".
And the resolver of this URN is yonsei., its URL is
<http://www.yonse.ac.kr>.
And 'k-univ' is not a resolver, it's URL is <http://www.k-univ.ac.kr>
But I register NID of this URN as 'k-univ', because all the URNs of each
university should be managed in
'k-univ'.

If 'k-univ' is a resolver of that URN, maybe the result of querying
'k-univ.urn.net' is as follow.

k-univ.urn.net
;;                 order   pref  flags
service                       regexp               replacement
IN NAPTR   100     10   "s"    "http+N2L+N2C+N2R"
''''             http.www.k-univ.ac.kr

And client can discover the resolver of that URN, and access it to
http.www.k-univ.ac.kr.

But 'k-univ' is not a resolver, so the result of querying
'k-univ.urn.net' is like that(it is my imagination)

k-univ.urn.net
;;                 order   pref   flags
service                     regexp                           replacement

IN NAPTR   100     10     ""              ""              "/urn:k-univ:
'^.*yonsei.*$/\?/?"            .

Because, 'k-univ is not a resolver of that URN, flags field has no
value, and replacement has no value, and
regexp has some value. (I don't know exactly what the value is. the
example is my free
expression.)

And record returned from the query on "yonsei" might look like:

yonsei IN NAPTR
  ;;              order pref flags
service                      regexp                  replacement
 IN NAPTR 100   10   "s"      " http+N2L+N2C+N2R"
.                http.www.yonse.ac.kr

And client can discover the resolver of that URN, and access it to
http.www.yonsei.ac.kr.


Is there any problem above my imagination?
When I make my URN, should not I use the character '/' which is a
reserved character in URN
syntax(RFC2141).
Or should Iuse "%" encoding?


My 2nd question is like that:

I chance to meet the internet-draft,   Handle System: A Persistent
Global Name Service Overview
and I think Handle System doesn't use RDS(Resolver Discovery Service),
instead it resolves handle(a kind of
URN) directly.

Anybody who knows the difference of NAPTR and Handle system tell me the
difference.
And in Handle System syntax, the character '/' is used.
I know that the character '/' is a reserved character in URN
syntax(RFC2141).

--------------CCBACF9DD16F9659487608BE
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>I'm a student interested in URN system, especially in URN resolution
system.
<br>I am preparing for my master's thesis about URN system.
<p>After reading&nbsp;&nbsp;&nbsp; <a href="ftp://ftp.isi.edu/in-notes/rfc2168.txt">RFC2168(Resolution
of Uniform Resource Identifiers using the Domain Name System)</a>&nbsp;
,
<br>and&nbsp;&nbsp;&nbsp; <a href="http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.txt">Internet
Draft(The Naming Authority Pointer (NAPTR) DNS Resource Record)</a>&nbsp;&nbsp;
, I can roughly
<br>understand how to resolve URN using NAPTR RR.
<p>I have some question about RFC2168.
<br>Anybody who knows about my question tell me some advice.
<p>&lt;In RFC2168>
<br>Example 2
<br>---------
<p>&nbsp;&nbsp; Consider a URN namespace based on MIME Content-Ids. The
URN might
<br>&nbsp;&nbsp; look like this:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<A HREF="urn:cid:199606121851.1@mordred.gatech.edu">urn:cid:199606121851.1@mordred.gatech.edu</A>
<p>&nbsp;&nbsp; (Note that this example is chosen for pedagogical purposes,
and does
<br>&nbsp;&nbsp; not conform to the recently-approved CID URL scheme.)
<p>&nbsp;&nbsp; The first step in the resolution process is to find out
about the CID
<br>&nbsp;&nbsp; namespace. The namespace identifier, cid, is extracted
from the URN,
<br>&nbsp;&nbsp; prepended to urn.net, and the NAPTR for cid.urn.net looked
up. It
<br>&nbsp;&nbsp; might return records of the form:
<p>&nbsp;cid.urn.net
<br>&nbsp; ;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; order pref flags service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; replacement
<br>&nbsp;&nbsp; IN NAPTR 100&nbsp;&nbsp; 10&nbsp;&nbsp; ""&nbsp; ""&nbsp;
"/<A HREF="urn:cid:.+@([^\">urn:cid:.+@([^\</A>.]+\.)(.*)$/\2/i"&nbsp;&nbsp;&nbsp; .
<p>&nbsp;&nbsp; We have only one NAPTR response, so ordering the responses
is not a
<br>&nbsp;&nbsp; problem.&nbsp; The replacement field is empty, so we check
the regexp
<br>&nbsp;&nbsp; field and use the pattern provided there. We apply that
regexp to the
<br>&nbsp;&nbsp; entire URN to see if it matches, which it does.&nbsp;
The \2 part of the
<br>&nbsp;&nbsp; substitution expression returns the string "gatech.edu".
Since the
<br>&nbsp;&nbsp; flags field does not contain "s" or "a", the lookup is
not terminal
<br>&nbsp;&nbsp; and our next probe to DNS is for more NAPTR records:
<br>&nbsp;&nbsp; lookup(query=NAPTR, "gatech.edu").
<br>&lt;In RFC2168>
<br>&nbsp;
<p>The NAPTR record has a string 'cid', so 'cid.urn.net' is retrived at
the 1st look-up.
<br>But I guess 'cid' is not a resolver of that URN, only a NID.
<br>So it has no flag value, and no replacement value, but has regexp value.
<br>And 2nd NAPTR look-up is processed with the string 'gatech.edu'.
<br>My first question is that why the 2nd look-up is processed with 'gatech.edu',
not else string?
<br>How does the \2 part of the substitution expression return the string
"gatech.edu"?
<br>And when the replacement field has value, and when it doesn't have
value?
<br>&nbsp;
<p>I can imagine that I'll make URN as like &lt;<A HREF="urn:k-univ:yonsei:d/lis/99-1">urn:k-univ:yonsei:d/lis/99-1</A>>.
<br>'k-univ' means "Korean Universities", and 'yonsei' means "Yonsei University".
<br>And the resolver of this URN is yonsei., its URL is &lt;<A HREF="http://www.yonse.ac.kr">http://www.yonse.ac.kr</A>>.
<br>And 'k-univ' is not a resolver, it's URL is &lt;<A HREF="http://www.k-univ.ac.kr">http://www.k-univ.ac.kr</A>>
<br>But I register NID of this URN as 'k-univ', because all the URNs of
each university should be managed in
<br>'k-univ'.
<p>If 'k-univ' is a resolver of that URN, maybe the result of querying
'k-univ.urn.net' is as follow.
<p>k-univ.urn.net
<br>;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
order&nbsp;&nbsp; pref&nbsp; flags&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
replacement
<br>IN NAPTR&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp; "s"&nbsp;&nbsp;&nbsp;
"http+N2L+N2C+N2R"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ''''&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http.www.k-univ.ac.kr
<p>And client can discover the resolver of that URN, and access it to http.www.k-univ.ac.kr.
<p>But 'k-univ' is not a resolver, so the result of querying 'k-univ.urn.net'
is like that(it is my imagination)
<p>k-univ.urn.net
<br>;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
order&nbsp;&nbsp; pref&nbsp;&nbsp; flags&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
replacement
<br>IN NAPTR&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;
""&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
""&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
"/urn:k-univ: '^.*yonsei.*$/\?/?"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;


Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id DAA00272 for urn-ietf-out; Fri, 2 Apr 1999 03:53:57 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id DAA00267 for <urn-ietf@services.bunyip.com>; Fri, 2 Apr 1999 03:53:55 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id DAA26661 for urn-ietf@services; Fri, 2 Apr 1999 03:53:54 -0500 (EST)
Received: from lis.yonsei.ac.kr (lis.yonsei.ac.kr [165.132.148.111]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id DAA26658 for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 03:53:29 -0500 (EST)
Received: from lis.yonsei.ac.kr ([165.132.148.191]) by lis.yonsei.ac.kr (8.9.1a-H1/8.9.1) with ESMTP id RAA28427 for <urn-ietf@bunyip.com>; Fri, 2 Apr 1999 17:53:05 +0900 (KST)
Message-ID: <37048548.E1FD0156@lis.yonsei.ac.kr>
Date: Fri, 02 Apr 1999 17:52:25 +0900
From: lislee <lislee@lis.yonsei.ac.kr>
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: urn-ietf@bunyip.com
Subject: [URN] About RFC2168
Content-Type: multipart/alternative; boundary="------------A18DE0118ECBFE5131817667"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: lislee <lislee@lis.yonsei.ac.kr>
Errors-To: owner-urn-ietf@Bunyip.Com

--------------A18DE0118ECBFE5131817667
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'm a student interested in URN system, especially in URN resolution
system.
I am preparing for my master's thesis about URN system.

After reading   RFC2168(Resolution of Uniform Resource Identifiers using
the Domain Name System)  ,
and   Internet Draft(The Naming Authority Pointer (NAPTR) DNS Resource
Record)  , I can roughly understand how to resolve URN using NAPTR RR.

I have some question about RFC2168.
Anybody who knows about my question tell me some advice.

<In RFC2168>
Example 2
---------

   Consider a URN namespace based on MIME Content-Ids. The URN might
   look like this:

                 urn:cid:199606121851.1@mordred.gatech.edu

   (Note that this example is chosen for pedagogical purposes, and does
   not conform to the recently-approved CID URL scheme.)

   The first step in the resolution process is to find out about the CID

   namespace. The namespace identifier, cid, is extracted from the URN,
   prepended to urn.net, and the NAPTR for cid.urn.net looked up. It
   might return records of the form:

 cid.urn.net
  ;;       order pref flags service        regexp           replacement
   IN NAPTR 100   10   ""  ""  "/urn:cid:.+@([^\.]+\.)(.*)$/\2/i"    .

   We have only one NAPTR response, so ordering the responses is not a
   problem.  The replacement field is empty, so we check the regexp
   field and use the pattern provided there. We apply that regexp to the

   entire URN to see if it matches, which it does.  The \2 part of the
   substitution expression returns the string "gatech.edu". Since the
   flags field does not contain "s" or "a", the lookup is not terminal
   and our next probe to DNS is for more NAPTR records:
   lookup(query=NAPTR, "gatech.edu").
<In RFC2168>


The NAPTR record has a string 'cid', so 'cid.urn.net' is retrived at the
1st look-up.
But I guess 'cid' is not a resolver of that URN, only a NID.
So it has no flag value, and no replacement value, but has regexp value.

And 2nd NAPTR look-up is processed with the string 'gatech.edu'.
My first question is that why the 2nd look-up is processed with
'gatech.edu', not else string?
How does the \2 part of the substitution expression return the string
"gatech.edu"?
And when the replacement field has value, and when it doesn't have
value?


I can imagine that I'll make URN as like <urn:k-univ:yonsei:d/lis/99-1>.

'k-univ' means "Korean Universities", and 'yonsei' means "Yonsei
University".
And the resolver of this URN is yonsei., its URL is
<http://www.yonse.ac.kr>.
And 'k-univ' is not a resolver, it's URL is <http://www.k-univ.ac.kr>
But I register NID of this URN as 'k-univ', because all the URNs of each
university should be managed in
'k-univ'.

If 'k-univ' is a resolver of that URN, maybe the result of querying
'k-univ.urn.net' is as follow.

k-univ.urn.net
;;                 order   pref  flags
service                       regexp               replacement
IN NAPTR   100     10   "s"    "http+N2L+N2C+N2R"
''''             http.www.k-univ.ac.kr

And client can discover the resolver of that URN, and access it to
http.www.k-univ.ac.kr.

But 'k-univ' is not a resolver, so the result of querying
'k-univ.urn.net' is like that(it is my imagination)

k-univ.urn.net
;;                 order   pref   flags
service                     regexp                           replacement

IN NAPTR   100     10     ""              ""              "/urn:k-univ:
'^.*yonsei.*$/\?/?"            .

Because, 'k-univ is not a resolver of that URN, flags field has no
value, and replacement has no value, and
regexp has some value. (I don't know exactly what the value is. the
example is my free
expression.)

And record returned from the query on "yonsei" might look like:

yonsei IN NAPTR
  ;;              order pref flags
service                      regexp                  replacement
 IN NAPTR 100   10   "s"      " http+N2L+N2C+N2R"
.                http.www.yonse.ac.kr

And client can discover the resolver of that URN, and access it to
http.www.yonsei.ac.kr.


Is there any problem above my imagination?
When I make my URN, should not I use the character '/' which is a
reserved character in URN syntax(RFC2141).
Or should Iuse "%" encoding?


My 2nd question is like that:

I chance to meet the internet-draft,  Handle System: A Persistent Global
Name Service Overview and Syntax.
I think Handle System doesn't use RDS(Resolver Discovery Service),
instead it resolves handle(a kind of
URN) directly.

Anybody who knows the difference of NAPTR and Handle system tell me the
difference.
And in Handle System syntax, the character '/' is used.
I know that the character '/' is a reserved character in URN
syntax(RFC2141).


--------------A18DE0118ECBFE5131817667
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I'm a student interested in URN system, especially in URN resolution system.
<br>I am preparing for my master's thesis about URN system.
<p>After reading&nbsp;&nbsp; <a href="ftp://ftp.isi.edu/in-notes/rfc2168.txt">RFC2168(Resolution
of Uniform Resource Identifiers using the Domain Name System)</a>&nbsp;
,
<br>and&nbsp;&nbsp; <a href="http://www.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-02.txt">Internet
Draft(The Naming Authority Pointer (NAPTR) DNS Resource Record)</a>&nbsp;
, I can roughly understand how to resolve URN using NAPTR RR.
<p>I have some question about RFC2168.
<br>Anybody who knows about my question tell me some advice.
<p>&lt;In RFC2168>
<br>Example 2
<br>---------
<p>&nbsp;&nbsp; Consider a URN namespace based on MIME Content-Ids. The
URN might
<br>&nbsp;&nbsp; look like this:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<A HREF="urn:cid:199606121851.1@mordred.gatech.edu">urn:cid:199606121851.1@mordred.gatech.edu</A>
<p>&nbsp;&nbsp; (Note that this example is chosen for pedagogical purposes,
and does
<br>&nbsp;&nbsp; not conform to the recently-approved CID URL scheme.)
<p>&nbsp;&nbsp; The first step in the resolution process is to find out
about the CID
<br>&nbsp;&nbsp; namespace. The namespace identifier, cid, is extracted
from the URN,
<br>&nbsp;&nbsp; prepended to urn.net, and the NAPTR for cid.urn.net looked
up. It
<br>&nbsp;&nbsp; might return records of the form:
<p>&nbsp;cid.urn.net
<br>&nbsp; ;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; order pref flags service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; replacement
<br>&nbsp;&nbsp; IN NAPTR 100&nbsp;&nbsp; 10&nbsp;&nbsp; ""&nbsp; ""&nbsp;
"/<A HREF="urn:cid:.+@([^\">urn:cid:.+@([^\</A>.]+\.)(.*)$/\2/i"&nbsp;&nbsp;&nbsp; .
<p>&nbsp;&nbsp; We have only one NAPTR response, so ordering the responses
is not a
<br>&nbsp;&nbsp; problem.&nbsp; The replacement field is empty, so we check
the regexp
<br>&nbsp;&nbsp; field and use the pattern provided there. We apply that
regexp to the
<br>&nbsp;&nbsp; entire URN to see if it matches, which it does.&nbsp;
<b><u>The \2 part of the</u></b>
<br><b><u>&nbsp;&nbsp; substitution expression returns the string "gatech.edu".</u></b>
Since the
<br>&nbsp;&nbsp; flags field does not contain "s" or "a", the lookup is
not terminal
<br>&nbsp;&nbsp; and our next probe to DNS is for more NAPTR records:
<br>&nbsp;&nbsp; lookup(query=NAPTR, "gatech.edu").
<br>&lt;In RFC2168>
<br>&nbsp;
<p>The NAPTR record has a string 'cid', so 'cid.urn.net' is retrived at
the 1st look-up.
<br>But I guess 'cid' is not a resolver of that URN, only a NID.
<br>So it has no flag value, and no replacement value, but has regexp value.
<br>And 2nd NAPTR look-up is processed with the string 'gatech.edu'.
<br>My first question is that why the 2nd look-up is processed with 'gatech.edu',
not else string?
<br>How does the \2 part of the substitution expression return the string
"gatech.edu"?
<br>And when the replacement field has value, and when it doesn't have
value?
<br>&nbsp;
<p>I can imagine that I'll make URN as like &lt;<A HREF="urn:k-univ:yonsei:d/lis/99-1">urn:k-univ:yonsei:d/lis/99-1</A>>.
<br>'k-univ' means "Korean Universities", and 'yonsei' means "Yonsei University".
<br>And the resolver of this URN is yonsei., its URL is &lt;<A HREF="http://www.yonse.ac.kr">http://www.yonse.ac.kr</A>>.
<br>And 'k-univ' is not a resolver, it's URL is &lt;<A HREF="http://www.k-univ.ac.kr">http://www.k-univ.ac.kr</A>>
<br>But I register NID of this URN as 'k-univ', because all the URNs of
each university should be managed in
<br>'k-univ'.
<p>If 'k-univ' is a resolver of that URN, maybe the result of querying
'k-univ.urn.net' is as follow.
<p>k-univ.urn.net
<br>;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
order&nbsp;&nbsp; pref&nbsp; flags&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
replacement
<br>IN NAPTR&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp; "s"&nbsp;&nbsp;&nbsp;
"http+N2L+N2C+N2R"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ''''&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http.www.k-univ.ac.kr
<p>And client can discover the resolver of that URN, and access it to http.www.k-univ.ac.kr.
<p>But 'k-univ' is not a resolver, so the result of querying 'k-univ.urn.net'
is like that(it is my imagination)
<p>k-univ.urn.net
<br>;;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
order&nbsp;&nbsp; pref&nbsp;&nbsp; flags&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
regexp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
replacement
<br>IN NAPTR&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;
""&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
""&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
"/urn:k-univ: '^.*yonsei.*$/\?/?"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;


Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id HAA17135 for urn-ietf-out; Thu, 1 Apr 1999 07:21:04 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [209.41.144.2]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id HAA17130 for <urn-ietf@services.bunyip.com>; Thu, 1 Apr 1999 07:21:02 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id HAA22830 for urn-ietf@services; Thu, 1 Apr 1999 07:21:01 -0500 (EST)
Received: from buzz.Bunyip.Com (buzz.Bunyip.Com [209.41.144.8]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id HAA22827; Thu, 1 Apr 1999 07:20:58 -0500 (EST)
Received: from localhost (leslie@localhost) by buzz.Bunyip.Com (8.6.9/8.6.10) with SMTP id HAA17802; Thu, 1 Apr 1999 07:20:58 -0500
X-Authentication-Warning: buzz.Bunyip.Com: leslie owned process doing -bs
Date: Thu, 1 Apr 1999 07:20:57 -0500 (EST)
From: Leslie Daigle <leslie@Bunyip.Com>
To: "Aaron E. Walsh" <aaron@mantiscorp.com>
cc: urn-ietf@bunyip.com
Subject: Re: [URN] status
In-Reply-To: <3702B7AB.C8C0DAAB@mantiscorp.com>
Message-ID: <Pine.SUN.3.95.990401071901.17797A-100000@buzz.Bunyip.Com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Leslie Daigle <leslie@Bunyip.Com>
Errors-To: owner-urn-ietf@Bunyip.Com

Howdy,

On Wed, 31 Mar 1999, Aaron E. Walsh wrote:
> I'm preparing now to register a few URN namespaces, and wonder if you or
> others could point me towards the proper documents to file? I understand
> this isn't as simple a process as simply submitting an online form, as
> we do for domains through InterNic, so want to make sure I'm heading in
> the right direction :)

The procedure is outlined in 

	draft-ietf-urn-nid-req-xx.txt

which is being finalized currently.  I.e., that document lays out the
mechanism, which should be "live" within the next little while.

Leslie.

------------------------------------------------------------------------------

  "Never confuse                               Leslie Daigle
     an appreciation of the simple                              
              for                              Bunyip Information Systems Inc.
     a lack of understanding of the complex."  +1 514 285 0088
                  -- ThinkingCat               leslie@bunyip.com
 
------------------------------------------------------------------------------


