[core] RFC 9997 on YANG-CBOR: Allocating SID Ranges for Private Enterprise Number (PEN) Holders

rfc-editor@rfc-editor.org Thu, 23 July 2026 09:33 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: core@ietf.org
Delivered-To: core@mail2.ietf.org
Received: from celery-55b7bf948f-hj2lc (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 857F911D2C9B6; Thu, 23 Jul 2026 02:33:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784799192; bh=NYIKSZAkoTkb+QhhqvUODL0pR6RHRufHh+iCdHoxXC4=; h=Subject:From:To:Cc:Date; b=iYoikoneO49Tb11mXp+rPUy2y8HgrLs9nkJegjWHeJXPELToTrLeJY5Ulyq2iCR+d pku9Ud2Xty/OMDdMOEAlzx1j2vTeMcDLf8UktlYOArUys6f2Ix4HZ4l+VExkmwjpUG klFX9r2cBTp8jhlCi67/Rs075xxCEV1UVgYNQnM0=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Thu, 23 Jul 2026 09:33:12 -0000
message-id: <178479919240.16.9710663676528552489@rfc-editor.org>
Message-ID-Hash: L736PD3VYMWSBALDR4V7VY3EAEPXKJQL
X-Message-ID-Hash: L736PD3VYMWSBALDR4V7VY3EAEPXKJQL
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: core@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [core] RFC 9997 on YANG-CBOR: Allocating SID Ranges for Private Enterprise Number (PEN) Holders
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/suZxrUXsBUeElMRm6es43efcjbc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Owner: <mailto:core-owner@ietf.org>
List-Post: <mailto:core@ietf.org>
List-Subscribe: <mailto:core-join@ietf.org>
List-Unsubscribe: <mailto:core-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        RFC 9997

        Title:      YANG-CBOR: Allocating SID Ranges for 
                    Private Enterprise Number (PEN) Holders
        Author:     C. Bormann
        Status:     Proposed Standard
        Stream:     IETF
        Date:       July 2026
        Mailbox:    cabo@tzi.org
        Pages:      6
        I-D Tag:    draft-ietf-core-yang-sid-pen-06

        URL:        https://www.rfc-editor.org/info/rfc9997

        DOI:        10.17487/RFC9997

YANG-CBOR (RFC 9254, "Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)") defines YANG Schema Item iDentifiers (YANG SIDs), globally unique 63-bit unsigned integers used to identify YANG items. RFC 9595 ("YANG Schema Item iDentifier (YANG SID)") defines ways to allocate these SIDs using IANA registries.

The present specification employs these SID allocation mechanisms to allocate ranges of 100 000 SIDs (representation size 64 bits) to each holder of an IANA Private Enterprise Number (PEN) of a value below 1 000 000. Holders of PENs of values smaller than 100 000 are also allocated ranges of 10 000 SIDs (representation size 32 bits).

This document is a product of the Constrained RESTful Environments Working Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team