[rfc-dist] RFC 9391 on Static Context Header Compression over Narrowband Internet of Things

rfc-editor@rfc-editor.org Thu, 20 April 2023 01:01 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 12507C16B5B5; Wed, 19 Apr 2023 18:01:24 -0700 (PDT)
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=unavailable 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 ZNmXPatD5jcP; Wed, 19 Apr 2023 18:01:20 -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 A3177C480D2E; Wed, 19 Apr 2023 17:59:52 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6C9EC563F6; Wed, 19 Apr 2023 17:59:52 -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, lp-wan@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230420005952.6C9EC563F6@rfcpa.amsl.com>
Date: Wed, 19 Apr 2023 17:59:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/FXkLHyTW7F9wFs0Sf5oL9ci3kM4>
Subject: [rfc-dist] RFC 9391 on Static Context Header Compression over Narrowband Internet of Things
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: Thu, 20 Apr 2023 01:01:24 -0000

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

        
        RFC 9391

        Title:      Static Context Header Compression over 
                    Narrowband Internet of Things 
        Author:     E. Ramos,
                    A. Minaburo
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2023
        Mailbox:    edgar.ramos@ericsson.com,
                    ana@ackl.io
        Pages:      22
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lpwan-schc-over-nbiot-15.txt

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

        DOI:        10.17487/RFC9391

This document describes Static Context Header Compression and
fragmentation (SCHC) specifications, RFCs 8724 and 8824, in
combination with the 3rd Generation Partnership Project (3GPP) and
the Narrowband Internet of Things (NB-IoT).

This document has two parts: one normative part that specifies the
use of SCHC over NB-IoT and one informational part that recommends
some values if 3GPP wants to use SCHC inside their architectures.

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