[rfc-dist] RFC 9363 on A YANG Data Model for Static Context Header Compression (SCHC)
rfc-editor@rfc-editor.org Wed, 01 March 2023 23:30 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14344C14F740; Wed, 1 Mar 2023 15:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 rysYpO7xdQ_Y; Wed, 1 Mar 2023 15:30:05 -0800 (PST)
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 5BD70C151540; Wed, 1 Mar 2023 15:30:05 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 260FBB3AE9; Wed, 1 Mar 2023 15:30:05 -0800 (PST)
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, lp-wan@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230301233005.260FBB3AE9@rfcpa.amsl.com>
Date: Wed, 01 Mar 2023 15:30:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/le6CShfY_WeMA35smLgYIzKhpIE>
Subject: [rfc-dist] RFC 9363 on A YANG Data Model for Static Context Header Compression (SCHC)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2023 23:30:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9363
Title: A YANG Data Model for
Static Context Header Compression (SCHC)
Author: A. Minaburo,
L. Toutain
Status: Standards Track
Stream: IETF
Date: March 2023
Mailbox: ana@ackl.io,
laurent.toutain@imt-atlantique.fr
Pages: 47
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lpwan-schc-yang-data-model-21.txt
URL: https://www.rfc-editor.org/info/rfc9363
DOI: 10.17487/RFC9363
This document describes a YANG data model for the Static Context
Header Compression (SCHC) compression and fragmentation Rules.
This document formalizes the description of the Rules for better
interoperability between SCHC instances either to exchange a set of
Rules or to modify the parameters of some Rules.
This document is a product of the IPv6 over Low Power Wide-Area Networks 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