Network Working Group M. Lanthaler Internet-Draft June 16, 2013 Intended status: Informational Expires: December 18, 2013 The IETF Profile URI Registry draft-lanthaler-profile-registry-02 Abstract This document defines a registry for profile URIs to be used in specifications standardizing profiles. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 18, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Lanthaler Expires December 18, 2013 [Page 1] Internet-Draft Profile URI Registry June 2013 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Registration Process . . . . . . . . . . . . . . . . . . . . . 3 3. Example Registration Request . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Initial Registry Contents . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 6. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6.1. From -01 to -02 . . . . . . . . . . . . . . . . . . . . . . 5 6.2. From -00 to -01 . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 8. Normative References . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Lanthaler Expires December 18, 2013 [Page 2] Internet-Draft Profile URI Registry June 2013 1. Introduction Profiles, as defined by [RFC6906], can be used to signal support for additional semantics, such as constraints, conventions, extensions, or any other aspects that do not alter the basic media type semantics. Profiles are identified by a URI and can thus be created without central coordination. Similarly to media types and link relation types it is, in some cases, beneficial to centrally manage profile URIs to ensure interoperability and decrease the coupling between clients and servers. This allows the independent evolution of clients and servers as both are coupled to these central contracts instead of being coupled to each other. Therefore, this document establishes an IANA registry for profile URIs. 2. Registration Process All elements in this registry require a URI in order to be registered. The meaning of the profile URI must be documented in a permanent and readily available public specification in sufficient detail so that interoperability between independent implementations is possible ("Specification Required" per [RFC5226]). An exemplary registration request can be found in Section 3. 3. Example Registration Request The following is an example registration request for the profile URI http://example.com/profiles/example. This is a request to IANA to please register the profile URI "http://example.com/profiles/example" in the Profile URI Registry according [this document]. o Profile URI: http://example.com/profiles/example o Common Name: Exemplary Profile URI o Description: An exemplary profile URI registration. o Specification Document: [this document] Lanthaler Expires December 18, 2013 [Page 3] Internet-Draft Profile URI Registry June 2013 4. IANA Considerations This document establishes the Profile URI registry. The registration procedure for new entries requires a request in the form of the following template and is "Specification Required" per [RFC5226]. Instructions for a registrant to request the registration of a profile URI are in Section 2. The underlying registry data (e.g., the XML file) must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions (). The registration template is: o Profile URI: The URI that identifies the registered profile. o Common Name: The name by which the profile being registered is generally known. o Description: A short description of the profile o Specification Document: Reference to the document that specifies the URI, preferably including a URI that can be used to retrieve a copy of the document. An indication of the relevant sections may also be included but is not required. o Notes: [optional] 4.1. Initial Registry Contents The Profile URI registry's initial contents are: o Profile URI: urn:example:profile-uri o Common Name: Exemplary Profile o Description: A profile to be used in examples. o Specification Document: [this document] 5. Security Considerations There are no additional security considerations beyond those already inherent to using URIs. Security considerations for URIs in general can be found in [RFC3986]. 6. Change Log Note to RFC Editor: Please remove this section before publication. Lanthaler Expires December 18, 2013 [Page 4] Internet-Draft Profile URI Registry June 2013 6.1. From -01 to -02 o Do not establish a new IETF URN Sub-namespace anymore. 6.2. From -00 to -01 o Use HTTP URI instead of URN in example registration request to make it clearer that not only URNs can be registered. o Move security considerations to the end. 7. Acknowledgements Thanks to Dave Cridland for valuable comments and suggestions. 8. Normative References [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. [RFC6906] Wilde, E., "The 'profile' Link Relation Type", RFC 6906, March 2013. Author's Address Markus Lanthaler Email: mail@markus-lanthaler.com URI: http://www.markus-lanthaler.com/ Lanthaler Expires December 18, 2013 [Page 5]