]> Universität Bremen TZI

Postfach 330440 D-28359 Bremen Germany +49-421-218-63921 cabo@tzi.org

Applications and Real-Time Area (art) CoRE Working Group YANG-CBOR YANG-CBOR (RFC 9254) defines YANG Schema Item iDentifiers (YANG SID), globally unique 63-bit unsigned integers used to identify YANG items. RFC 9595 defines ways to allocate these SIDs on the basis of IANA registries. The present specification employs these SID allocation mechanisms to allocate ranges with 100 000 63-bit SIDs each for each of the first 1 000 000 holders of IANA-registered Private Enterprise Numbers (PENs), as well as ranges with 10 000 32-bit SIDs each for each of the first 100 000 holders.
The present revision –03 is intended to address the feedback from the CoRE Working-Group last call.
Note that due to a regression in the bib.ietf.org service (https://github.com/ietf-tools/bibxml-service/issues/489), the reference may come out as "*** BROKEN REFERENCE ***" in some CI systems; this will certainly be fixed in the course of further processing. About This Document Status information for this document may be found at . Discussion of this document takes place on the CoRE Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction YANG-CBOR defines YANG Schema Item iDentifiers (YANG SID), globally unique 63-bit unsigned integers used to identify YANG items. defines ways to allocate these SIDs on the basis of IANA registries. The present specification employs these SID allocation mechanisms to allocate ranges with 100 000 63-bit SIDs each for each of the first 1 000 000 holders of IANA-registered Private Enterprise Numbers (PENs), as well as ranges with 10 000 32-bit SIDs each for each of the first 100 000 holders. IANA [is requested to allocate/has allocated] 100 000 mega-ranges, for the SID numbers 300 000 000 000 to 399 999 999 999. IANA also [is requested to allocate/has allocated] 1000 mega-ranges, for the SID numbers 3 000 000 000 to 3 999 999 999. Private Enterprise Numbers (PENs) are registered in in a low-threshold, low-overhead registration process. At the time of writing (~ 37 years after creating this registry), around 65 000 PENs are registered. In this document, the registrant for a PEN is referred to as the "PEN holder". The present specification makes the following SID ranges available to certain (current or future) PEN holders for allocation in a scheme defined by the holder:

• The holder of a PEN ppp ppp (< 1 000 000) can use the SID numbers 3pp ppp p00 000 to 3pp ppp p99 999.
• The holder of a PEN pp ppp (< 100 000) can use the SID numbers 3 ppp pp0 000 to 3 ppp pp9 999.

Example The Department for Mathematics and Computer Science of holds PEN 30810. To this PEN holder, the present specification confers control over the SID ranges:

• 303 081 000 000 up to 303 081 099 999, and
• 3 308 100 000 up to 3 308 109 999.

(The plaintext form of this document shows "*" characters around the digits conveying the PEN, which are shown in boldface in the typographic forms.)

Discussion This allocation provides an extremely-low-threshold (zero-interaction) way for PEN holders to get number space for the YANG SIDs used in their YANG modules. If a PEN is not already available to the entity needing such number space, it can be obtained in a very low-threshold process. Employing this number space is, however, not always the approach to recommend to a module author:

• The larger of the two spaces uses 64-bit numbers. The larger representation size of the absolute value of the SID is of comparatively little consequence due to the delta-encoding used for SIDs in YANG-CBOR.
• For the first 100 000 PEN holders, there also is a smaller space that uses 32-bit numbers. PEN numbers that have access to this space are likely to run out before or around 2040; the expectation is that by that time there will be enough opportunities to request SID ranges within mega-ranges allocated by other registrants that this mechanism is less needed.
• This space has no infrastructure to discover the YANG module behind a SID. Of course, each PEN holder can provide such infrastructure, but even then the problem remains of how to find that infrastructure for a SID. (Search engines may mitigate this somewhat.) On the other hand, in some cases this relative obscurity may be exactly what a PEN holder wants to achieve by using this mechanism. If obscurity is not the intention, one or both of the following approaches are encouraged:
  • The PEN holder can provide a public repository where their YANG models can be found alongside the applicable SID files. Such a repository may be easy to set up using a popular git forge such as, at the time of writing, GitHub.
  • Implementations that employ PEN-based SIDs can facilitate information discovery by providing or another form of YANG library .

Relying on the PEN registry might theoretically trigger a land-grab by prospective writers of YANG modules. However, PENs have been around for decades (see , which continues to be in force with no technical changes as Section of RFC 1155 ), and such a land-grab has not occurred for the other allocations implicitly provided by obtaining a PEN.

IANA Considerations RFC Ed.: throughout this section, please replace RFC-XXXX with the RFC number of this specification and remove this note. This document allocates 100 000 63-bit and 1000 32-bit SID mega-ranges as per , as summarized in . Megarange Allocations for use by PEN holders

Entry Point	Size	Allocation	Org Name	URL
3 000 000 000 up to 3 999 999 999	1 000 000 000	Private	IANA	https://rfc-editor.org/info/rfcxxxx
300 000 000 000 up to 399 999 999 999	100 000 000 000	Private	IANA	https://rfc-editor.org/info/rfcxxxx

An additional contact for the allocation is: IETF CORE Working Group (core@ietf.org) or IETF Applications and Real-Time Area (art@ietf.org). The allocation policy inside the mega-range is "private". The URL is that of the present specification. The management of the SID blocks of 100 000 SIDs each, 10 such blocks for each mega-range 3nn nnn 000 000, is delegated to the PEN holder for nnn nnx, where x is the sequence number of the SID block in the mega-range (i.e., the PEN holder for nnn nnx controls SID 3nn nnn x00 000 to 3nn nnn x99 999). Similarly, the management of the SID blocks of 10 000 SIDs each, 100 such blocks for each mega-range 3 nnn 000 000, is delegated to the PEN holder for nn nxx, where x is the sequence number of the SID block in the mega-range (i.e., the PEN holder for nn nxx controls SID 3 nnn xx0 000 to 3 nnn xx9 999). requires an organization that requests an entry in the "YANG-SID Mega-Ranges" registry to ensure the technical capacity to manage the SID ranges within those mega-ranges for a period of at least 10 years (Private ranges). The individual SID ranges within the mega-ranges allocated in this document are assigned through the registration of PEN numbers. The technical capacity to ensure the sustained operation of the PEN number registry is derived from the demonstrated capacity of IANA to maintain this registry as well as the importance of a functioning PEN number registry in other contexts.

Security Considerations Section Security Considerations of applies, as well as Section Security Considerations of . In particular, the fact that a certain Private Enterprise Number appears in a SID is not an indicator of provenance, i.e., it does not guarantee that the SID or underlying YANG model actually does originate from the holder of that PEN. The requirement to ascertain the authoritative source of this information, as discussed in the above security considerations, remains.

References Normative References YANG (RFC 7950) is a data modeling language used to model configuration data, state data, parameters and results of Remote Procedure Call (RPC) operations or actions, and notifications. This document defines encoding rules for YANG in the Concise Binary Object Representation (CBOR) (RFC 8949). YANG Schema Item iDentifiers (YANG SIDs) are globally unique 63-bit unsigned integers used to identify YANG items. SIDs provide a more compact method for identifying those YANG items that can be used efficiently, notably in constrained environments (RFC 7228). This document defines the semantics, registration processes, and assignment processes for YANG SIDs for IETF-managed YANG modules. To enable the implementation of these processes, this document also defines a file format used to persist and publish assigned YANG SIDs. Informative References This RFC provides the common definitions for the structure and identification of management information for TCP/IP-based internets. In particular, together with its companion memos, which describe the initial management information base along with the initial network management protocol, these documents provide a simple, working architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification. This RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1065. [STANDARDS-TRACK] This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK] Trilliant Networks Inc. Acklio This document describes a constrained version of the YANG library that provides information about the YANG modules, datastores, and datastore schemas used by a constrained network management server (e.g., a CORECONF server). This document describes a YANG library that provides information about the YANG modules, datastores, and datastore schemas used by a network management server. Simple caching mechanisms are provided to allow clients to minimize retrieval of this information. This version of the YANG library supports the Network Management Datastore Architecture (NMDA) by listing all datastores supported by a network management server and the schema that is used by each of these datastores.

Acknowledgments This document was inspired by the discussion of the authors of and on how to handle feedback.