I would like to see
Updates RFC3986
on this.
It says
" discussions of URNs and URN namespaces should be interpreted
according to this document and not by extrapolation from RFC 3986.
"
which to me says that RFC3986 may not be authoritative for URN and so is
de facto updated.
Tom Petch
----- Original Message -----
From: "The IESG" <iesg-secretary(_at_)ietf(_dot_)org>
To: "IETF-Announce" <ietf-announce(_at_)ietf(_dot_)org>
Cc: <urn(_at_)ietf(_dot_)org>; <alexey(_dot_)melnikov(_at_)isode(_dot_)com>;
<barryleiba(_at_)computer(_dot_)org>;
<draft-ietf-urnbis-rfc2141bis-urn(_at_)ietf(_dot_)org>;
<urnbis-chairs(_at_)ietf(_dot_)org>
Sent: Monday, February 13, 2017 3:08 PM
Subject: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform
Resource Names (URNs)) to Proposed Standard
The IESG has received a request from the Uniform Resource Names,
Revised
WG (urnbis) to consider the following document:
- 'Uniform Resource Names (URNs)'
<draft-ietf-urnbis-rfc2141bis-urn-20.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2017-02-27. Exceptionally, comments
may
be
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
Abstract
A Uniform Resource Name (URN) is a Uniform Resource Identifier
(URI)
that is assigned under the "urn" URI scheme and a particular URN
namespace, with the intent that the URN will be a persistent,
location-independent resource identifier. With regard to URN
syntax,
this document defines the canonical syntax for URNs (in a way that
is
consistent with URI syntax), specifies methods for determining URN-
equivalence, and discusses URI conformance. With regard to URN
namespaces, this document specifies a method for defining a URN
namespace and associating it with a namespace identifier, and
describes procedures for registering namespace identifiers with the
Internet Assigned Numbers Authority (IANA). This document
obsoletes
both RFC 2141 and RFC 3406.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc2141bis-urn/
IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc2141bis-urn/ballot
/
No IPR declarations have been submitted directly on this I-D.