datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

The Profile URI Registry
draft-lanthaler-profile-registry-05

Document type: Active Internet-Draft (individual)
Document stream: ISE
Last updated: 2014-04-12 (latest revision 2014-01-21)
Intended RFC status: Informational
Other versions: plain text, xml, pdf, html
IETF Conflict Review: conflict-review-lanthaler-profile-registry

ISE State: Sent to the RFC Editor
Document shepherd: No shepherd assigned

IESG State: I-D Exists
IANA Action State: RFC-Ed-Ack
RFC Editor State: EDIT
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                       M. Lanthaler
Internet-Draft                                          January 21, 2014
Intended status: Informational
Expires: July 25, 2014

                        The Profile URI Registry
                  draft-lanthaler-profile-registry-05

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 July 25, 2014.

Copyright Notice

   Copyright (c) 2014 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 July 25, 2014                 [Page 1]
Internet-Draft          The Profile URI Registry            January 2014

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 . . . . . . . . . . . . . . . . . . . . 5
   6.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     6.1.  From -04 to -05 . . . . . . . . . . . . . . . . . . . . . . 5
     6.2.  From -03 to -04 . . . . . . . . . . . . . . . . . . . . . . 5
     6.3.  From -02 to -03 . . . . . . . . . . . . . . . . . . . . . . 6
     6.4.  From -01 to -02 . . . . . . . . . . . . . . . . . . . . . . 6
     6.5.  From -00 to -01 . . . . . . . . . . . . . . . . . . . . . . 6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 7

Lanthaler                 Expires July 25, 2014                 [Page 2]
Internet-Draft          The Profile URI Registry            January 2014

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 should be documented in a
   permanent and readily available public specification in sufficient
   detail so that interoperability between independent implementations
   is possible (see the registration template in Section 4).

   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

[include full document text]