RFC 9595 on YANG Schema Item iDentifier (YANG SID)

rfc-editor@rfc-editor.org Wed, 31 July 2024 22:45 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 180C4C14F605; Wed, 31 Jul 2024 15:45:58 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 846703B873; Wed, 31 Jul 2024 15:45:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9595 on YANG Schema Item iDentifier (YANG SID)
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240731224557.846703B873@rfcpa.rfc-editor.org>
Date: Wed, 31 Jul 2024 15:45:57 -0700
Message-ID-Hash: XYITWWJIL7DJBVSWOLU7XJIB3PSJCOJX
X-Message-ID-Hash: XYITWWJIL7DJBVSWOLU7XJIB3PSJCOJX
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, core@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/VzjaN1tCIDWygedHWqAfxQsPgHM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

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

        
        RFC 9595

        Title:      YANG Schema Item iDentifier (YANG SID) 
        Author:     M. Veillette, Ed.,
                    A. Pelov, Ed.,
                    I. Petrov, Ed.,
                    C. Bormann,
                    M. Richardson
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2024
        Mailbox:    michel.veillette@trilliant.com,
                    alexander.pelov@imt-atlantique.fr,
                    ivaylopetrov@google.com,
                    cabo@tzi.org,
                    mcr+ietf@sandelman.ca
        Pages:      44
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-core-sid-24.txt

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

        DOI:        10.17487/RFC9595

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.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/retrieve/bulk

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
Association Management Solutions, LLC