CoRE Target Attribute Registry

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 https://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 5 August 2023.¶

Copyright Notice

Copyright (c) 2023 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.¶

Table of Contents

1. Introduction

(Please see abstract.)¶

The original Web Linking specification Section 3 of [RFC5988] did not attempt to coordinate names of target attributes except for providing common target attributes for use in the Link HTTP header. The current revision of that specification clarifies (Section 2.2 of [RFC8288]):¶

This specification does not attempt to coordinate the name of target attributes, their cardinality, or use. Those creating and maintaining serialisations SHOULD coordinate their target attributes to avoid conflicts in semantics or syntax and MAY define their own registries of target attributes.¶

This short note introduces an IANA registry for coordinating names of Target Attributes when used in Constrained RESTful Environments.¶

With a 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. (See also Section 2, Paragraph 2.)¶

2. IANA Considerations

This specification defines a new sub-registry for Target Attributes in the CoRE Parameters registry [IANA.core-parameters], with the policy "expert review" (Section 4.5 of [BCP26]).¶

Each entry in the registry must include:¶

Attribute Name:

a lower case ASCII [STD80] string that starts with a letter and can contain digits and hyphen-minus characters afterward ([a-z][-a-z0-9]*). (Note that [RFC8288] requires target attribute names to be interpreted in a case-insensitive way; the restriction to lower case here ensures that they are registered in a predictable form).¶

Brief description:

a brief description¶

Change Controller:

(see Section 2.3 of [BCP26])¶

Reference:

a reference document that provides a description of the target attribute, including the semantics for when the target attribute appears more than once in a link.¶

Initial entries in this sub-registry are as listed in Table 1:¶

A number of names are reserved as they are used for parameters in links other than target attributes, this includes a further set that is predefined in [RFC8288].¶

This table includes some registrations from drafts that are not yet published as an RFC. Ideally, these RFCs should make those registrations. The entries here are insurance in case the present draft gets stuck on the way and [I-D.ietf-core-oscore-groupcomm] and/or [I-D.ietf-core-oscore-edhoc] get published as RFC first. They also serve to give some impression how the entries might grow, which may be useful for discussing in the WGLC some policies for choosing attribute names.-- Carsten¶

3. Security considerations

The security considerations of [RFC8288] apply, as do those of the discovery specifications [RFC6690], [RFC7252], and [RFC9176].¶

Acknowledgements

TBD¶

Contributors

Jaime provided the list of initial registrations.¶

Author's Address