OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xri-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: New RFC about registration of URI schemes

Drummond Reed wrote:
 > FYI - Jeff Hodges of NeuStar, an observer on the XRI TC, asked me to pass
 > along the following info:
 > FYI, the guidelines and procedures for registering new URI schemes (e.g.
 > "xri:") with IANA (nee IETF) are being revised and are essentially baked.
 > It's been approved for publication as a RFC and will be denoted as a "best
 > current practice (BCP)". It does not yet have an RFC number assigned AFAICT.

The RFC was published in Feb-2006 and is..

   4395 Guidelines and Registration Procedures for New URI Schemes. T.
      Hansen, T. Hardie, L. Masinter. February 2006. (Format: TXT=31933
      bytes) (Obsoletes RFC2717, RFC2718) (Also BCP0115) (Status: BEST

 > It'd probably be a good idea for xri: mavens to review this.
 > Note that it includes this text, in part at the behest of the W3C TAG..
 >    2.1.  Demonstratable, new, long-lived utility
 >       The use and deployment of new URI schemes in the Internet
 >       infrastructure is costly; some parts of URI processing may be scheme-
 >       dependent, and deployed software already processes URIs of well-known
 >       schemes.  Introducing a new URI scheme may require additional
 >       software, not only for client software and user agents but also in
 >       additional parts of the network infrastructure (gateways, proxies,
 >       caches).[13].  URI schemes constitute a single, global namespace; it
 >       is desirable to avoid contention over use of short, mneumonic scheme
 >       names.  For these reasons, the unbounded registration of new schemes
 >       is harmful.  New URI schemes SHOULD have clear utility to the broad
 >       Internet community, beyond that available with already registered URI
 >       schemes.
 > JeffH
 > -------- Original Message --------
 > Subject: Protocol Action: 'Guidelines and Registration Procedures for  new
 > URI
 > Schemes' to BCP
 > Date: Tue, 15 Nov 2005 17:23:13 -0500
 > From: The IESG <iesg-secretary@ietf.org>
 > To: IETF-Announce <ietf-announce@ietf.org>
 > CC: Internet Architecture Board <iab@iab.org>,   RFC Editor
 > <rfc-editor@rfc-editor.org>
 > The IESG has approved the following document:
 > - 'Guidelines and Registration Procedures for new URI Schemes '
 >      <draft-hansen-2717bis-2718bis-uri-guidelines-06.txt> as a BCP
 > This document has been reviewed in the IETF but is not the product of an
 > IETF Working Group.
 > The IESG contact person is Scott Hollenbeck.
 > A URL of this Internet-Draft is:
 > http://www.ietf.org/internet-drafts/draft-hansen-2717bis-2718bis-uri-guideli
 > nes-
 > 06.txt
 > Technical Summary
 > This document provides guidelines and recommendations for the
 > definition of Uniform Resource Identifier (URI) schemes.  It also
 > updates the process and IANA registry for URI schemes.  If approved,
 > this document obsoletes RFCs 2717 and 2718.
 > Working Group Summary
 > This document is the work of individual submitters.  It has not been
 > reviewed by an IETF working group, though it was reviewed by members
 > of the uri@w3.org mailing list.  An IETF last call was requested and
 > completed.  Review comments have been incorporated into the document.
 > Protocol Quality
 > Scott Hollenbeck has reviewed this document for the IESG.  In
 > addition, it was reviewed by the members of the uri@w3.org mailing
 > list.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]