Addition of organisation prefix to RFC6690 IANA CoRE parameters registration
draft-groves-core-rfc6690up-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-17
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CoRE Working Group                                             C. Groves
Internet-Draft                                                   W. Yang
Intended status: Standards Track                                  Huawei
Expires: April 20, 2017                                 October 17, 2016

    Addition of organisation prefix to RFC6690 IANA CoRE parameters
                              registration
                     draft-groves-core-rfc6690up-00

Abstract

   [RFC6690] defines the resource type 'rt' and interface description
   'if' link attributes and defines procedures for registering values.
   Currently each 'rt' and 'if' attribute value must be registered with
   IANA.  This specification updates the process to enable organisation
   prefixes to be registered allowing organisations to manage their own
   namespace within a certain set of rules.

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 April 20, 2017.

Copyright Notice

   Copyright (c) 2016 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

Groves & Yang            Expires April 20, 2017                 [Page 1]
Internet-Draft        Prefix for CoRE parameter reg         October 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Organisation Prefix . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Constrained RESTful Environments (CoRE) Parameters
           Registry Update . . . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
     7.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].

2.  Introduction

   [RFC6690] "Constrained RESTful Environments (CoRE) Link Format"
   defines the Resource Type 'rt' and Interface Description 'if' link
   attributes.  In order to co-ordinate the use of these attributes,
   sections 7.4 and 7.5/[RFC6690] establish IANA registries to register
   link attribute values for 'rt' and 'if'.

   In order to register a new 'rt' and 'if' link attribute value the
   [RFC5226] "Specification Required" process is followed for each
   value.  As part of the process a designated expert will examine the
   specification to enforce a number of requirements including:

   o  Registration values MUST be related to the intended purpose of
      these attributes as described in Section 3/[RFC6690].

   o  Registered values MUST conform to the ABNF reg-rel-type definition
      of Section 2/[RFC6690], meaning that the value starts with a
      lowercase alphabetic character, followed by a sequence of
Show full document text