The IETF Profile URI Registry
draft-lanthaler-profile-registry-02
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2013-09-03
(latest revision 2013-06-16)
|
|
Stream |
|
ISE
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
IETF conflict review |
|
conflict-review-lanthaler-profile-registry |
| Stream |
ISE state
|
|
(None)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
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.
Show full document text