[lp-wan] RFC 9441 on Static Context Header Compression (SCHC) Compound Acknowledgement (ACK)

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

        RFC 9441

        Title:      Static Context Header Compression (SCHC) 
                    Compound Acknowledgement (ACK) 
        Author:     J. Zúñiga,
                    C. Gomez,
                    S. Aguilar,
                    L. Toutain,
                    S. Céspedes,
                    D. Wistuba
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2023
        Mailbox:    juzuniga@cisco.com,
                    carles.gomez@upc.edu,
                    sergio.aguilar.romero@upc.edu,
                    laurent.toutain@imt-atlantique.fr,
                    sandra.cespedes@concordia.ca,
                    wistuba@niclabs.cl
        Pages:      22
        Updates:    RFC 8724, RFC 9363

        I-D Tag:    draft-ietf-lpwan-schc-compound-ack-17.txt

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

        DOI:        10.17487/RFC9441

This document updates the Static Context Header Compression (SCHC)
and fragmentation protocol (RFC 8724) and the corresponding YANG
module (RFC 9363). It defines a SCHC Compound Acknowledgement (ACK)
message format and procedure, which are intended to reduce the number
of response transmissions (i.e., SCHC ACKs) in the ACK-on-Error Mode,
by accumulating bitmaps of several windows in a single SCHC message
(i.e., the SCHC Compound ACK). 

Both the message format and procedure are generic, so they can be
used, for instance, by any of the four Low-Power Wide Area Network
(LPWAN) technologies defined in RFC 8376, which are Sigfox, Long
Range Wide Area Network (LoRaWAN), Narrowband Internet of Things
(NB-IoT), and IEEE 802.15.4w.

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