| RFC 9423 | CoRE Target Attributes Registry | April 2024 |
| Bormann | Informational | [Page] |
The Constrained RESTful Environments (CoRE) specifications apply webtechnologies to constrained environments.One such important technology is Web Linking (RFC 8288), which CoREspecifications use as the basis for a number of discovery protocols, such as theLink Format (RFC 6690) in the Constrained Application Protocol's (CoAP's) resource discovery process (Section 7.2of RFC 7252) and the Resource Directory (RD) (RFC 9176).¶
Web Links can have target attributes, the names of which are notgenerally coordinated by the Web Linking specification (Section 2.2 ofRFC 8288).This document introduces an IANA registry for coordinating names of targetattributes when used in CoRE.It updates the "RD Parameters" IANA registry created by RFC 9176 to coordinate withthis registry.¶
This document is not an Internet Standards Track specification; it is published for informational purposes.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are candidates for any level of Internet Standard; see Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc9423.¶
Copyright (c) 2024 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 (https://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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Constrained RESTful Environments (CoRE) specifications apply webtechnologies to constrained environments.One such important technology is Web Linking[RFC8288], which CoREspecifications use as the basis for a number of discovery protocols, such as theLink Format[RFC6690] in the Constrained Application Protocol's (CoAP's) resource discovery process (Section 7.2 of [RFC7252]) and the Resource Directory (RD)[RFC9176].¶
Web Links can have target attributes.The original Web Linking specification (Section 3 of [RFC5988]) did not attemptto coordinate names of target attributes except for providing commontarget attributes for use in the Link HTTP header.The current revision of that specification (Section 2.2 of [RFC8288]) clarifies as follows:¶
This specification does not attempt to coordinate the name of target attributes, their cardinality, or use. Those creating and maintaining serialisationsSHOULD coordinate their target attributes to avoid conflicts in semantics or syntax andMAY define their own registries of target attributes.¶
This document introduces an IANA registry for coordinating names of targetattributes when used in CoRE, withspecific instructions for the designated expert for this registry (Section 2.1).It updates the "RD Parameters" IANA registry created by[RFC9176] to coordinate withthis registry.¶
With this registry now available, registration of target attributes is strongly encouraged.The incentive is that an unregistered attribute name might be registered with a different meaning at any time.¶
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 BCP 14[RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.¶
Per this specification, IANA has created a new "Target Attributes" registry inthe "Constrained RESTful Environments (CoRE) Parameters" registry group[IANA.core-parameters], with the policy"Expert Review" (Section4.5 of RFC 8126[BCP26]).¶
The expert is requested to guide the registrant towards reasonablyshort target attribute names where the shortness will help conserveresources in constrained systems, but to also be frugal in theallocation of very short names, keeping them in reserve forapplications that are likely to enjoy wide use and can make good useof their shortness.¶
The expert is also instructed to direct the registrant to provide aspecification (Section4.6 of RFC 8126[BCP26]) but can make exceptions --for instance, when a specification is not available at the time ofregistration but is likely forthcoming.¶
Any questions or issues that might interest a wider audience might beraised by the expert on the core-parameters@ietf.org mailing list fora time-limited discussion.This might include security considerations, or opportunities fororchestration, e.g., when different names with similar intent arebeing or could be registered.¶
If the expert becomes aware of target attributes that are deployed andin use, they may also initiate a registration on their own ifthey deem that such a registration can avert potential future collisions.¶
Each entry in the registry must include the following:¶
A lowercase ASCII string[STD80] that starts with a letter and cancontain digits and hyphen-minus characters afterward([a-z][-a-z0-9]*).(Note that[RFC8288] requires target attribute names to beinterpreted in a case-insensitive way; the restriction to lowercasehere ensures that they are registered in a predictable form.)¶
A brief description.¶
A reference document that provides a description of the targetattribute, including the semantics for when the target attributeappears more than once in a link.¶
Initial entries in this registry are listed inTable 1.¶
| Attribute Name | Brief Description | Change Controller | Reference |
|---|---|---|---|
| href | reserved (not useful as target attribute name) | IETF | [RFC6690] |
| anchor | reserved (not useful as target attribute name) | IETF | [RFC6690] |
| rel | reserved (not useful as target attribute name) | IETF | [RFC6690] |
| rev | reserved (not useful as target attribute name) | IETF | [RFC6690] |
| hreflang | (Web Linking) | IETF | [RFC8288] |
| media | (Web Linking) | IETF | [RFC8288] |
| title | (Web Linking) | IETF | [RFC8288] |
| type | (Web Linking) | IETF | [RFC8288] |
| rt | resource type | IETF | Section 3.1 of [RFC6690] |
| if | interface description | IETF | Section 3.2 of [RFC6690] |
| sz | maximum size estimate | IETF | Section 3.3 of [RFC6690] |
| ct | Content-Format hint | IETF | Section 7.2.1 of [RFC7252] |
| obs | observable resource | IETF | Section 6 of [RFC7641] |
| hct | HTTP-CoAP URI mapping template | IETF | Section 5.5 of [RFC8075] |
| osc | hint: resource only accessible using OSCORE | IETF | Section 9 of [RFC8613] |
| ep | Endpoint Name (with rt="core.rd-ep") | IETF | Section 9.3 of [RFC9176] |
| d | Sector (with rt="core.rd-ep") | IETF | Section 9.3 of [RFC9176] |
| base | Registration Base URI (with rt="core.rd-ep") | IETF | Section 9.3 of [RFC9176] |
| et | Endpoint Type (with rt="core.rd-ep") | IETF | Section 9.3 of [RFC9176] |
A number of names are reserved, as they are used for parameters inlinks other than target attributes.A further set of target attributes is predefined in[RFC8288] and isimported into this registry.¶
Section 9.3 of [RFC9176] created the "RD Parameters" IANA registry.Per this document, IANA has added the following note to that registry:¶
Note: In accordance with RFC 9423, all entries with the "A" flag set, including new ones,MUST also be registered in the "Target Attributes" registry[IANA.core-parameters].¶
The security considerations of[RFC8288] apply, as do those of thediscovery specifications[RFC6690],[RFC7252], and[RFC9176].¶
The CoRE Working Group had been discussing setting up a registry for targetattributes since the final touches were made on[RFC6690].The update of the Web Linking specification to[RFC8288] provided theformal setting, but it took untilJaime Jiménez provided the set ofinitial registrations to generate a first draft version of this specification.The current document addresses additional input and Working Group LastCall comments byEsko Dijk,Marco Tiloca,Thomas Fossati,andMohamed Boucadair,as well as Area Director review comments fromRob Wilton.¶
Jaime provided the list of initial registrations.¶