Re: [lp-wan] FW: RFC 8824 on Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)

dominique.barthel@orange.com Wed, 30 June 2021 07:34 UTC

Return-Path: <dominique.barthel@orange.com>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 213473A10FA for <lp-wan@ietfa.amsl.com>; Wed, 30 Jun 2021 00:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 5ie_PsJFJoZr for <lp-wan@ietfa.amsl.com>; Wed, 30 Jun 2021 00:34:28 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F7CF3A10FD for <lp-wan@ietf.org>; Wed, 30 Jun 2021 00:34:28 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar21.francetelecom.fr (ESMTP service) with ESMTPS id 4GFClk0ht0z7tv4; Wed, 30 Jun 2021 09:34:26 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1625038466; bh=pT3UM7cTAEEkZxNHhw9RK+CljxQWr4Kgx3iyxwRk354=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=S3yFEUtzG9OmMnFYkHutcvwRObP1Hqhjt3hSVCXXP+BpQnPD38TmmnDthg1joidiS MCPdB/T8XoiCJ8j4x1bzxxt9NRy2csujp9OrvciFcOPUGPiduHvD6tjYY7nN3c025f SF+BpuG5sEJI1J8U4VnYpywQYGYLVyyJ9JllCFHXLscQRgF2eZtixnB4oi4O5K1ICg 2r6YbyCo4KEIIi3V4p3kpW+gEbpARYHYYRDWAjgMu2RLyEM32Ikrd+MM+/aacK4buj +IiTG3G0FlL7wBdVl8FCU/BEND34Ir90tF2Ly3/sLAYjShXitSbYtR2yT/HiXPM+ny skGM9Gw4aoyDQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar04.francetelecom.fr (ESMTP service) with ESMTPS id 4GFClj71h6z1xp0; Wed, 30 Jun 2021 09:34:25 +0200 (CEST)
From: dominique.barthel@orange.com
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, "lp-wan@ietf.org" <lp-wan@ietf.org>
Thread-Topic: [lp-wan] FW: RFC 8824 on Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)
Thread-Index: AQHXbXiRRj0PJfTLa0+pW4uG7nah+assJx7QgAAB2sA=
Date: Wed, 30 Jun 2021 07:34:24 +0000
Message-ID: <23618_1625038466_60DC1E81_23618_257_1_8F1D83ADCC1AC94186A867BEE9B7D9137FD2DBDD@OPEXCAUBM21.corporate.adroot.infra.ftgroup>
References: <20210630062348.00199F40729@rfc-editor.org> <CO1PR11MB4881E5CDC49412228F2DFE83D8019@CO1PR11MB4881.namprd11.prod.outlook.com>
In-Reply-To: <CO1PR11MB4881E5CDC49412228F2DFE83D8019@CO1PR11MB4881.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/_PCMtyAnyFbXMXuSVMKqQNrur1c>
Subject: Re: [lp-wan] FW: RFC 8824 on Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2021 07:34:33 -0000

Congrats and thanks to all involved, indeed.
We're moving on!

Dominique


-----Original Message-----
From: lp-wan [mailto:lp-wan-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
Sent: mercredi 30 juin 2021 09:29
To: lp-wan@ietf.org
Subject: [lp-wan] FW: RFC 8824 on Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)

Congrats to the team and the whole group!

Now we have a whole stack for a node at least for one technology, more techs to follow soon with SigFox and NB IOT.

Next steps are the architecture and the data model, so we can deploy the infrastructure more automatically and scale to tons of various devices.

Keep the good time rollin'!

The chairs


-----Original Message-----
From: lp-wan <lp-wan-bounces@ietf.org> On Behalf Of rfc-editor@rfc-editor.org
Sent: mercredi 30 juin 2021 8:24
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: lp-wan@ietf.org; drafts-update-ref@iana.org; rfc-editor@rfc-editor.org
Subject: [lp-wan] RFC 8824 on Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)

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


_______________________________________________
lp-wan mailing list
lp-wan@ietf.org
https://www.ietf.org/mailman/listinfo/lp-wan

_______________________________________________
lp-wan mailing list
lp-wan@ietf.org
https://www.ietf.org/mailman/listinfo/lp-wan

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.