idnits 2.17.1 draft-yevstifeyev-xri-uri-rsrv-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 4, 2011) is 4711 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2141 (Obsoleted by RFC 8141) -- Obsolete informational reference (is this intentional?): RFC 4395 (Obsoleted by RFC 7595) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT M. Yevstifeyev, Ed. 3 Intended Status: Informational June 4, 2011 4 Expires: December 6, 2011 6 Reserving 'xri' Scheme for URIs Mapped from 7 Extensible Resource Identifiers (XRIs) 8 draft-yevstifeyev-xri-uri-rsrv-00 10 Abstract 12 This document reserves the 'xri' Uniform Resource Identifier (URI) 13 scheme for URIs mapped from Extensible Resource Identifiers (XRIs) 14 via its formal registration. 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/1id-abstracts.html 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html 37 Copyright and License Notice 39 Copyright (c) 2011 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 1. Introduction 54 Extensible Resource Identifiers (XRIs) are a way of abstractly 55 identifying a resource independently of any particular concrete 56 representation of it. They are designed to suit Requirements for 57 Uniform Resource Names (URNs), laid out in [RFC1737], even though 58 they are not URNs [RFC2141] themselves. 60 The comprehensive XRI specification includes 3 documents: 61 [XRISyntax], which is the normative technical specification of XRI 62 generic syntax, [XRIResolution], which defines an optional HTTP-based 63 resolution protocol for XRIs, and [XRIMetadata], which defines four 64 namespaces under the XRI global context symbol "$" for common types 65 of identifier metadata. See [XRIIntro] for non-normative description 66 of XRIs and [XRIFaq] for FAQ on XRIs. XRI requirements and glossary 67 are defined in [XRIReq]. 69 [XRISyntax], Section 2.3.1 specifies rules for transforming XRI 70 references to URI [RFC3986] and Internationalized Resource 71 Identifiers (IRIs) [RFC3987] references. It mentions that URIs 72 mapped from XRIs use the "xri" scheme name. It has been noted that 73 this scheme name is not officially registered with IANA, as described 74 in [RFC4395]. This document removes the uncertainty by formal 75 registration of the 'xri' URI scheme. 77 1.1. Community Consensus 79 The Organization for the Advancement of Structured Information 80 Standards (OASIS) has the Technical Committee (TC), which is 81 responsible for developing and maintaining XRI specifications, - XRI 82 TC. This document has been prepared for this TC and has received its 83 excessive review, which revealed wide consensus of the TC's members. 85 [IMPORTANT: Currently, this document is only a subject for the 86 aforementioned review; the paragraph above actually does not 87 represent TC consensus.] 89 2. Registration Template for 'xri' URI Scheme 91 This section contains the registration template for 'xri' URI scheme, 92 as required by [RFC4395]. 94 URI scheme name: xri 96 Status: Permanent 97 URI scheme syntax: see Section 2.2 and 2.3 of [XRISyntax] 99 URI scheme semantics: see [XRIResolution] 101 XRI scheme encoding considerations: see Section 2.1 of [XRISyntax] 103 Protocols that use the scheme: see [XRIResolution] 105 Security considerations: see Section 3 of RFC xxxx 107 Contact: {TBD} 109 Author/Change controller: Organization for the Advancement of 110 Structured Information Standards (OASIS) 112 References: see Section 5 of RFC xxxx 114 [RFC Editor Note: Please replace xxxx with number of this RFC] 116 3. Security Considerations 118 Security considerations for XRIs are discussed in Section 3 of 119 [XRISyntax] and Section 18 of [XRIResolution]. 121 4. IANA Considerations 123 IANA is asked to register the 'xri' URI scheme using the template of 124 Section 2. 126 5. References 128 5.1. Normative References 130 [XRIResolution] 131 Wachob, B., Ed., Reed, D., Ed., Chasen, D., Ed., Tan, W., 132 Ed. and S. Churchill, Ed., "Extensible Resource 133 Identifier (XRI) Resolution Version 2.0", OASIS Committee 134 Specification, April 2008. 135 138 [XRISyntax] Reed, D., Ed. and D. McAlpin, Ed., "Extensible Resource 139 Identifier (XRI) Syntax V2.0", OASIS Committee 140 Specification, November 2005. 141 144 5.2. Informative References 146 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 147 Uniform Resource Names", RFC 1737, December 1994. 149 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 151 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 152 Resource Identifier (URI): Generic Syntax", STD 66, 153 RFC 3986, January 2005. 155 [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource 156 Identifiers (IRIs)", RFC 3987, January 2005. 158 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 159 Registration Procedures for New URI Schemes", BCP 35, 160 RFC 4395, February 2006. 162 [XRIFaq] OASIS XRI Technical Committee, "XRI 2.0 FAQ", Web Page, 163 March 2006. 164 166 [XRIIntro] Reed, D., Ed. and D. McAlpin, Ed., "An Introduction to 167 XRIs", work in progress. 169 [XRIMetadata] 170 Reed, D., Ed., "Extensible Resource Identifier (XRI) 171 Metadata V2.0", work in progress. 173 [XRIReq] Wachob, G., Ed., Reed, D., Ed., Le Maitre, M., Ed., 174 McAlpin, D., Ed. and D. McPherson, Ed., "Extensible 175 Resource Identifier (XRI) Requirements and Glossary 176 v1.0", OASIS Committee Specification, June 2003. 177 180 Authors' Addresses 182 Mykyta Yevstifeyev (editor) 183 8 Kuzovkov St., flat 25 184 Kotovsk 185 Ukraine 187 EMail: evnikita2@gmail.com