RFC 8824 on Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)
rfc-editor@rfc-editor.org Wed, 30 June 2021 06:24 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9851F3A0B00; Tue, 29 Jun 2021 23:24:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id llFpanbbYP0n; Tue, 29 Jun 2021 23:24:05 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A81043A0AF3; Tue, 29 Jun 2021 23:24:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 00199F40729; Tue, 29 Jun 2021 23:23:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8824 on Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20210630062348.00199F40729@rfc-editor.org>
Date: Tue, 29 Jun 2021 23:23:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/uk7MWtEXalgKgrFP6biI2wPpVQc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2021 06:24:11 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8824
Title: Static Context Header Compression (SCHC)
for the Constrained Application Protocol (CoAP)
Author: A. Minaburo,
L. Toutain,
R. Andreasen
Status: Standards Track
Stream: IETF
Date: June 2021
Mailbox: ana@ackl.io,
laurent.toutain@imt-atlantique.fr,
randreasen@fi.uba.ar
Pages: 30
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lpwan-coap-static-context-hc-19.txt
URL: https://www.rfc-editor.org/info/rfc8824
DOI: 10.17487/RFC8824
This document defines how to compress Constrained Application
Protocol (CoAP) headers using the Static Context Header Compression
and fragmentation (SCHC) framework. SCHC defines a header compression
mechanism adapted for Constrained Devices. SCHC uses a static
description of the header to reduce the header's redundancy and size.
While RFC 8724 describes the SCHC compression and fragmentation
framework, and its application for IPv6/UDP headers, this document
applies SCHC to CoAP headers. The CoAP header structure differs from
IPv6 and UDP, since CoAP uses a flexible header with a variable
number of options, themselves of variable length. The CoAP message
format is asymmetric: the request messages have a header format
different from the format in the response messages. This
specification gives guidance on applying SCHC to flexible headers and
how to leverage the asymmetry for more efficient compression 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