RFC Errata
Found 2 records.
Status: Verified (1)
RFC 5279, "A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)", July 2008
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 1516
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Verifier Name: Alexey Melnikov
Date Verified: 2010-11-12
Section 2, pg.2/3 says:
Declaration of syntactic structure:
| The Namespace Specific String (NSS) of all URNs that use the
| "3gpp" NID will have the following structure:
urn:3gpp:{3gpp-urn}
where the "3gpp-urn" is a US-ASCII string that conforms to the
NSS(Namespace Specific String) Syntax described in RFC 2141
| [RFC2141] and defines a specific resource type.
It should say:
Declaration of syntactic structure:
| All URNs that use the "3gpp" NID will have the following
| structure:
urn:3gpp:{3gpp-urn}
where the "3gpp-urn" is a US-ASCII string that conforms to the
NSS(Namespace Specific String) Syntax described in RFC 2141
| [RFC2141] and defines a specific resource.
Notes:
a) Obviously, the original clause contradicts itself.
It is impossible that the NSS is a proper subpart of itself
as would be required by the text and the syntax shown.
The corrected text resolves this partial issue, but not the
next two issues, which still remain open. Furthermore, for
logical consistency, "resource type" had to be replaced by
"resource" in the last line, to maintain the required
uniqueness property of '3gpp' URNs.
b) Even the corrected statement merely is a simple instantiation of
the general definition in RFC 2141 (Section 2, page 1), plus
giving an alias name (<3gpp-urn>) to the NSSs of '3gpp' URNs.
However, it does not cure the apparent underspecification:
The current URN Namespace registration template per BCP 66,
RFC3406, serves for "... providing a mechanism for disclosing
[the] structure of the URN namespace ..." (page 11 of RFC 3406),
but the quoted clause, as it stands, does *not*
"outline any structural features of identifiers in this namespace"
(p. 12 of RFC 3406).
Status: Held for Document Update (1)
RFC 5279, "A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)", July 2008
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 2626
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Held for Document Update by: Peter Saint-Andre
Date Held: 2010-11-12
Section 3 says:
Notes:
Furthermore, the second example presented in Section 3 of RFC 5279
does not precisely match the pattern indicated in the above clause;
instead, it tries to suggest that
urn:3gpp:acme.foo-serv
defines a '3gpp' URN
... identified by the "3gpp-urn" value "acme".
This contradiction seems to be a hint that the authors indeed
want to define a structured NSS with <3gpp-urn> being the most
significant part, and the period character used to separate it
from a potentially following more specific part of the '3gpp' URN.
Yet, there's no syntax definition in the RFC that would support
this precisely.