[core] RFC 9254 on Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)
rfc-editor@rfc-editor.org Mon, 18 July 2022 19:39 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF54C13C500; Mon, 18 Jul 2022 12:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.963
X-Spam-Level:
X-Spam-Status: No, score=-3.963 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id awtdLkuutbsI; Mon, 18 Jul 2022 12:39:50 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DD47C15791D; Mon, 18 Jul 2022 12:39:50 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7C4CC4C087; Mon, 18 Jul 2022 12:39:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, core@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220718193950.7C4CC4C087@rfcpa.amsl.com>
Date: Mon, 18 Jul 2022 12:39:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Q2Rl7QEFa7VLRwkkUp9nIuHABso>
Subject: [core] RFC 9254 on Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2022 19:39:54 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9254
Title: Encoding of Data Modeled with
YANG in the Concise Binary Object
Representation (CBOR)
Author: M. Veillette, Ed.,
I. Petrov, Ed.,
A. Pelov,
C. Bormann,
M. Richardson
Status: Standards Track
Stream: IETF
Date: July 2022
Mailbox: michel.veillette@trilliantinc.com,
ivaylopetrov@google.com,
a@ackl.io,
cabo@tzi.org,
mcr+ietf@sandelman.ca
Pages: 45
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-core-yang-cbor-20.txt
URL: https://www.rfc-editor.org/info/rfc9254
DOI: 10.17487/RFC9254
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).
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