Addition of organisation prefix to RFC6690 IANA CoRE parameters registration
Huawei
Registration values MUST be related to the intended purpose of these attributes as described in Section 3/.
Registered values MUST conform to the ABNF reg-rel-type definition of Section 2/, meaning that the value starts with a lowercase alphabetic character, followed by a sequence of lowercase alphabetic, numeric, “.”, or “-“ characters, and contains no white space.
It is recommended that the period “.” character be used for dividing name segments and that the dash “-“ character be used for making a segment more readable. Example Interface Description values might be “core.batch” and “core.link-batch”.
URIs are reserved for free use as extension values for these attributes and MUST NOT be registered.
The IANA CoRE resource type and interface description registry can be found at: IANA CoRE Registry.
Given the scope of the Internet of Things (IoT) the potential number of resource types (and to a lesser extent interface types) is potentially quite large. This would lead to a large number of requests for designated expert review. It would also mean additional work for the IANA to process each request.
The current trend for the definition of resource types and interface descriptions is that a few standards organisations have defined a large number of values.
For example the “OIC Resource Type Specification v1.1.0” contains 64 resource types.
ETSI oneM2M also defines a large number of resource types. For example is “Home Appliances Information Model and Mapping” .
The Open Mobile Alliance (OMA) also make use of resources types.
The above three organisations also have their own registry and procedures for adding resource types. Trying to keep the IANA registry aligned with the individual organisation registries would also add additional burden.
A significant amount of work could be saved by allowing organisations to register a prefix under which they can administer their own resources negating the need for the IANA and the designated IANA expert to be involved for each resource registration.
This specification updates the IANA registration procedures to allow the possibility to register a pre-fix.
As indicated by registered values MUST conform to the ABNF reg-rel-type definition, meaning that the value starts with a lowercase alphabetic character. Therefore an organisation registering a prefix MUST register a lowercase alphabetic sequence of characters. It MUST be followed by a “.”.
For example: “foo.”
This will allocate the namespace “foo.” to the organisation. The organisation will then be responsible for maintaining resources within this name space.
E.g. “foo.sensor”, “foo.actuator” could be allocated without requiring registration with IANA.
This specification updates the IANA Considerations. No additional protocol security impacts to what is already described in are foreseen.
The use of organisational prefixes introducing the possibility that people request prefixes for an organisation that they do not represent. The IANA considerations in this specification require that the designated expert determine if the person requesting a prefix represents the organisation related to the prefix.
This specification updates the Constrained RESTful Environments (CoRE) Parameter Registry by allowing the registration of an organisation prefix for Resource Type (rt=) and Interface Description (if=) Link Target Attribute values.
Organisation prefixes are registered by using the Specification Required policy (see , which requires review by a designated expert appointed by the IESG or their delegate.
The designated expert will enforce the following requirements:
o The registered prefix MUST conform to the ABNF reg-rel-type definition of Section 2/, meaning that the value starts with a lowercase alphabetic character followed by a period “.”.
o The registered prefixes are assigned on a first come first served basis.
o Prefixes must be requested by a representative of the organisation applying for the prefix and must be representative of the organisation. E.g. organisation “foo” trying to register “ietf.” would not be representative.
The specification MUST:
Specify the procedures for registering values within the prefixed namespace. It ideally SHOULD provide a link where current and future registered values may be found.
Indicate that registered values within the prefixed namespace MUST conform to the ABNF reg-rel-type definition of Section 2/. This means that the prefix MUST be followed by a sequence of lowercase alphabetic, numeric, “.”, or “-“ characters, and contains no white space. Note: It is not recommended to immediately follow the prefix with an additional period “.”, e.g. “foo..”.
Use the recommendation that the period “.” character be used for dividing name segments and that the dash “-“ character be used for making a segment more readable. Example Interface Description values might be “core.batch” and “core.link-batch”.
Registration requests consist of the completed registration template below, with the reference pointing to the required specification. To allow for the allocation of values prior to publication, the designated expert may approve registration once they are satisfied that a specification will be published.
The registration template for both sub-registries is:
o Prefix Value:
o Description:
o Reference:
o Notes: [optional]
Registration requests should be sent to the core-parameters@ietf.org mailing list, marked clearly in the subject line (e.g., “NEW RESOURCE TYPE PREFIX - example” to register an “example” relation type or “NEW INTERFACE DESCRIPTION PREFIX - example” to register an “example” Interface Description).
Handling and the decision process is as per section 7.4/.
Key words for use in RFCs to Indicate Requirement Levels
In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Guidelines for Writing an IANA Considerations Section in RFCs
Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Constrained RESTful Environments (CoRE) Link Format
This specification defines Web Linking using a link format for use by constrained web servers to describe hosted resources, their attributes, and other relationships between links. Based on the HTTP Link Header field defined in RFC 5988, the Constrained RESTful Environments (CoRE) Link Format is carried as a payload and is assigned an Internet media type. "RESTful" refers to the Representational State Transfer (REST) architecture. A well-known URI is defined as a default entry point for requesting the links hosted by a server. [STANDARDS-TRACK]
OIC Resource Type Specification v1.1.0
TS 0023 v2.0.0 Home Appliances Information Model and Mapping