|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Informational RFC approved 2005-10.
|
|
3.
|
Justification for the specific reference:
|
|
|
This Informational IETF RFC defines a "tag" Uniform Resource Identifier (URI) scheme. Tag URIs (also known as "tags") are designed to be unique across space and time while being tractable to humans. They are distinct from most other URIs in that they have no authoritative resolution mechanism. A tag may be used purely as an entity identifier. Furthermore, using tags has some advantages over the common practice of using "http" URIs as identifiers for non-HTTP-accessible resources. Even though this is an Informational RFC, tag URIs add an important functionality for ITU-T H.274 | ISO/IEC 23002-7 implementations.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3986
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Document published in October 2005 (http://www.ietf.org/rfc/rfc4151.txt). The status is INFORMATIONAL.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Document published in October 2005 (http://www.ietf.org/rfc/rfc4151.txt). The status is INFORMATIONAL. Errata exist.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
URIs are widely used to identify resources. Tag URIs are distinct from most other URIs in that they have no authoritative resolution mechanism. A tag may be used purely as an entity identifier. Furthermore, using tags has some advantages over the common practice of using "http" URIs as identifiers for non-HTTP-accessible resources.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[1] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986,/
January 2005./
/
[2] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", RFC 2234, November 1997./
/
[3] Mockapetris, P., "Domain names - implementation and/
specification", STD 13, RFC 1035, November 1987./
/
[4] "Data elements and interchange formats -- Information/
interchange -- Representation of dates and times", ISO/
(International Organization for Standardization) ISO 8601:1988,/
1988./
/
Informative References/
/
[5] Leach, P. and R. Salz, "UUIDs and GUIDs", Work in Progress,/
1997./
/
[6] "Information technology - Open Systems Interconnection - Remote/
Procedure Call (RPC)", ISO (International Organization for/
Standardization) ISO/IEC 11578:1996, 1996./
/
[7] "Specification of abstract syntax notation one (ASN.1)", ITU-T/
recommendation X.208, (see also RFC 1778), 1988./
/
[8] Mealling, M., "A URN Namespace of Object Identifiers",/
RFC 3061, February 2001./
/
[9] Paskin, N., "Information Identifiers", Learned Publishing Vol./
10, No. 2, pp. 135-156, (see also www.doi.org), April 1997./
/
[10] Klyne, G. and C. Newman, "Date and Time on the Internet:/
Timestamps", RFC 3339, July 2002.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
