[rfc-dist] RFC 8724 on SCHC: Generic Framework for Static Context Header Compression and Fragmentation

rfc-editor@rfc-editor.org Thu, 16 April 2020 02:40 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60DAE3A099A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Apr 2020 19:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, 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 tGxXcnqx4TMV for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Apr 2020 19:40:03 -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 8A11B3A099C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 15 Apr 2020 19:40:03 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0CA7FF40750; Wed, 15 Apr 2020 19:39:43 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 58346F4074C; Wed, 15 Apr 2020 19:39:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200416023941.58346F4074C@rfc-editor.org>
Date: Wed, 15 Apr 2020 19:39:41 -0700
Subject: [rfc-dist] RFC 8724 on SCHC: Generic Framework for Static Context Header Compression and Fragmentation
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: lp-wan@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8724

        Title:      SCHC: Generic Framework for Static 
                    Context Header Compression and Fragmentation 
        Author:     A. Minaburo, 
                    L. Toutain,
                    C. Gomez,
                    D. Barthel,
                    JC. Zúñiga
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2020
        Mailbox:    ana@ackl.io, 
                    laurent.toutain@imt-atlantique.fr, 
                    carlesgo@entel.upc.edu, 
                    dominique.barthel@orange.com, 
                    juancarlos.zuniga@sigfox.com
        Pages:      71
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lpwan-ipv6-static-context-hc-24.txt

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

        DOI:        10.17487/RFC8724

This document defines the Static Context Header Compression and
fragmentation (SCHC) framework, which provides both a header
compression mechanism and an optional fragmentation mechanism. SCHC
has been designed with Low-Power Wide Area Networks (LPWANs) in mind.

SCHC compression is based on a common static context stored both in
the LPWAN device and in the network infrastructure side. This
document defines a generic header compression mechanism and its
application to compress IPv6/UDP headers.

This document also specifies an optional fragmentation and reassembly
mechanism. It can be used to support the IPv6 MTU requirement over
the LPWAN technologies. Fragmentation is needed for IPv6 datagrams
that, after SCHC compression or when such compression was not
possible, still exceed the Layer 2 maximum payload size.

The SCHC header compression and fragmentation mechanisms are
independent of the specific LPWAN technology over which they are
used. This document defines generic functionalities and offers
flexibility with regard to parameter settings and mechanism choices.
This document standardizes the exchange over the LPWAN between two
SCHC entities. Settings and choices specific to a technology or a
product are expected to be grouped into profiles, which are specified
in other documents. Data models for the context and profiles are out
of scope.

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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org