The four recent I-Ds replace the "yaurn" I-D

Paul Hoffman <ietf-lists@proper.com> Thu, 04 May 1995 00:55 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11386; 3 May 95 20:55 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa11382; 3 May 95 20:55 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa19831; 3 May 95 20:55 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id RAA26744 for uri-out; Wed, 3 May 1995 17:33:20 -0400
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id RAA26739 for <uri@services.bunyip.com>; Wed, 3 May 1995 17:33:18 -0400
Received: from proper.proper.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA04701 (mail destined for uri@services.bunyip.com); Wed, 3 May 95 17:32:35 -0400
Received: from [165.227.40.11] (user11.znet.com [165.227.40.11]) by proper.proper.com (8.6.11/8.6.5) with SMTP id OAA13609 for <uri@bunyip.com>; Wed, 3 May 1995 14:28:16 -0700
X-Sender: ietflist@proper.com
Message-Id: <v02120c00abcda6b7ac99@[165.227.40.27]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 03 May 1995 14:33:28 -0700
To: uri@bunyip.com
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Hoffman <ietf-lists@proper.com>
Subject: The four recent I-Ds replace the "yaurn" I-D
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

Greetings. Larry Masinter has pointed out that there is some confusion
about our recent I-Ds and the status of our previous I-D,
"draft-ietf-uri-yaurn-00". We got feedback from folks that they'd rather
see the "draft-ietf-uri-yaurn-00" broken into smaller pieces to make
commenting on it easier. Thus, we split "yaurn" into the four I-Ds we sent
out earlier this week and had the "yaurn" I-D expired early. Before sending
out the four I-Ds, we also made other changes to some of the specifics in
each proposal.

For perspective, the other URN I-Ds that were submitted before Danvers
mostly talked specific URN resolution schemes. Few of the active I-Ds went
into much detail about the overall structure of URN resolution, about
resolution results, or about the syntax of URNs; we thought these were very
important, so we made each of these a separate I-D. The active I-Ds written
by other authors all do talk about specific URN resolution schemes, so we
separated out our own proposal for a resolution scheme, x-dns-2, as its own
I-D.

--Paul Hoffman
--Ron Daniel