|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3987 (2005)
|
|
Title:
|
Internationalized Resource Identifiers (IRIs). M. Duerst, M. Suignard. January 2005.
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
IRIs are used for designation of BIP endpoints (see subclause 15.3).
|
|
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=3987
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Document published in January 2005 (http://www.ietf.org/rfc/rfc3987.txt). The status is PROPOSED STANDARD.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Document published in January 2005 (http://www.ietf.org/rfc/rfc3987.txt). The status is PROPOSED STANDARD.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
IRIs are widely used to identify resources.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ASCII] American National Standards Institute, "Coded Character Set -- 7-bit American Standard Code for Information Interchange", ANSI X3.4, 1986./
[ISO10646] International Organization for Standardization, "ISO/IEC 10646:2003: Information Technology -Universal Multiple-Octet Coded Character Set (UCS)", ISO Standard 10646, December 2003./
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997./
[RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, "Internationalizing Domain Names in Applications (IDNA)", RFC 3490, March 2003./
[RFC3491] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)", RFC 3491, March 2003./
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003./
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005./
[UNI9] Davis, M., "The Bidirectional Algorithm", Unicode Standard Annex #9, March 2004, http://www.unicode.org/reports/tr9/tr9-13.html./
[UNIV4] The Unicode Consortium, "The Unicode Standard, Version 4.0.1, defined by: The Unicode Standard, Version 4.0 (Reading, MA, Addison-Wesley, 2003. ISBN 0-321-18578-1), as amended by Unicode 4.0.1 (http://www.unicode.org/versions/Unicode4.0.1/)", March 2004./
[UTR15] Davis, M. and M. Duerst, "Unicode Normalization Forms", Unicode Standard Annex #15, April 2003, http://www.unicode.org/unicode/reports/tr15/tr15-23.html./
[BidiEx] "Examples of bidirectional IRIs", http://www.w3.org/International/iri-edit/BidiExamples./
[CharMod] Duerst, M., Yergeau, F., Ishida, R., Wolf, M., and T.Texin, "Character Model for the World Wide Web: Resource Identifiers", World Wide Web Consortium Candidate Recommendation, November 2004, http://www.w3.org/TR/charmod-resid./
[Duerst97] Duerst, M., "The Properties and Promises of UTF-8", Proc. 11th International Unicode Conference, San Jose, September 1997, http://www.ifi.unizh.ch/mml/mduerst/papers/PDF/IUC11-UTF-8.pdf./
[Gettys] Gettys, J., "URI Model Consequences", http://www.w3.org/DesignIssues/ModelConsequences./
[HTML4] Raggett, D., Le Hors, A., and I. Jacobs, "HTML 4.01 Specification", World Wide Web Consortium Recommendation, December 1999, http://www.w3.org/TR/html401/appendix/notes.html#h-B.2./
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996./
[RFC2130] Weider, C., Preston, C., Simonsen, K., Alvestrand, H., Atkinson, R., Crispin, M., and P. Svanberg, "The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996", RFC 2130, April 1997./
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997./
[RFC2192] Newman, C., "IMAP URL Scheme", RFC 2192, September 1997./
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998./
RFC 3987 Internationalized Resource Identifiers January 2005/
[RFC2368] Hoffman, P., Masinter, L., and J. Zawinski, "The mailto URL scheme", RFC 2368, July 1998./
[RFC2384] Gellens, R., "POP URL Scheme", RFC 2384, August 1998./
[RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998./
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, August 1998./
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999./
[RFC2640] Curtin, B., "Internationalization of the File Transfer Protocol", RFC 2640, July 1999./
[RFC2718] Masinter, L., Alvestrand, H., Zigmond, D., and R. Petke, "Guidelines for new URL Schemes", RFC 2718, November 1999./
[UNIXML] Duerst, M. and A. Freytag, "Unicode in XML and other Markup Languages", Unicode Technical Report #20, World Wide Web Consortium Note, June 2003, http://www.w3.org/TR/unicode-xml/./
[XLink] DeRose, S., Maler, E., and D. Orchard, "XML Linking Language (XLink) Version 1.0", World Wide Web Consortium Recommendation, June 2001, http://www.w3.org/TR/xlink/#link-locators./
[XML1] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E.,and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium Recommendation, February 2004, http://www.w3.org/TR/REC-xml#sec-external-ent./
[XMLNamespace] Bray, T., Hollander, D., and A. Layman, "Namespaces in XML", World Wide Web Consortium Recommendation, January 1999, http://www.w3.org/TR/REC-xml-names./
[XMLSchema] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes", World Wide Web Consortium Recommendation, May 2001, http://www.w3.org/TR/xmlschema-2/#anyURI./
[XPointer] Grosso, P., Maler, E., Marsh, J. and N. Walsh, "XPointer Framework", World Wide Web Consortium Recommendation, March 2003, http://www.w3.org/TR/xptr-framework/#escaping./
|
|
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
|
|
