Re: [6lo] [lp-wan] RFC 8724 on SCHC: Generic Framework for Static Context Header Compression and Fragmentation

Alexander Pelov <a@ackl.io> Thu, 16 April 2020 08:33 UTC

Return-Path: <alexander@ackl.io>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFEF13A11C1 for <6lo@ietfa.amsl.com>; Thu, 16 Apr 2020 01:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=ackl-io.20150623.gappssmtp.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 zyFBBKYMzBnP for <6lo@ietfa.amsl.com>; Thu, 16 Apr 2020 01:33:14 -0700 (PDT)
Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 9F5EC3A11C9 for <6lo@ietf.org>; Thu, 16 Apr 2020 01:33:14 -0700 (PDT)
Received: by mail-il1-x129.google.com with SMTP id f2so6113430ilq.7 for <6lo@ietf.org>; Thu, 16 Apr 2020 01:33:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackl-io.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KqWtHWr5Noxco3dkAhs2wiNqkudNl68MauqBfNtLbMI=; b=tw0l2YioYxVUPsB5lDv8cdywdE85Iye9RSWhjACLgr2rRnS4B1lTZULJ3r48mwao6/ xVi3nJnk8GEG+n1bVfFv6XYSkPxFTk2vI01yYL/mj22V4PFcrD7jaD2evdLqf9F9f9JD +iR923uI+BeOXy/c6RRe6F8Kw6ljebT6+kRVlRoQIhpl4IRtHhxywWQ4sC53p6M8Sh2p MzVSlHjfeUHvCanqG974n02EWQ7V62DT0NlDeDHBxXKxH+ub5KDbMukxwUxC1nAvMCQN Pykg1xrblFMVGR5vvZdZuJEuIuuXEt2VRaYzITitgBzsTErAGUT7gvK7vzu51T3EU6IG h3Xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KqWtHWr5Noxco3dkAhs2wiNqkudNl68MauqBfNtLbMI=; b=t0/7Gvj5QZOMlviXN5LGfwh89j57cP8RLPchBqT768/wA0Qhad6n8gn4xQurQxo5OU 9tIOh1RZJxsoBwTQnEcWLggbRFIgUrmNzoufZWYi0vzCNsmME2ZH6kct9Hst4SnZ6MMe kkEEj5uirVg869FYR8hUZBNYRsAXoQya1v+4sb2i0TAP927SeHQNk/vpwc5vjxrnaYZh 07x2ytk8dBgAY0fWUBRz47FBhhTBKdO46sRw0amv7mwtrpiFDTD4mYd9nPbBQeqfbOPD nAkqV4DgOdFNJHq6W6pdZHGwSxsfRB36Jr4UJM3FvXIzhU6of52JfPGy4PkvDfkI2swo /3gA==
X-Gm-Message-State: AGi0PuY6MuOmn34/dGKi0F9qdXbV/YMioCbnthDdIwpLBEKn0dXszXyA RkFls4FoOHpnlw6QOQXpQeM5hdzkIlyAkslhjF9q7g==
X-Google-Smtp-Source: APiQypJpYgiWSrnnU89Wrbuz4a0rgY/DtoFQsQ+nVtE70kAsdS/HNUK0fnMJtc19LuJk/P6T6IHExxBIDXpE3wRlvLo=
X-Received: by 2002:a92:394d:: with SMTP id g74mr9468550ila.250.1587025993688; Thu, 16 Apr 2020 01:33:13 -0700 (PDT)
MIME-Version: 1.0
References: <20200416023941.58346F4074C@rfc-editor.org> <7B04CD72-D631-44DD-96CB-1B278E8B1EA3@tzi.org>
In-Reply-To: <7B04CD72-D631-44DD-96CB-1B278E8B1EA3@tzi.org>
From: Alexander Pelov <a@ackl.io>
Date: Thu, 16 Apr 2020 10:32:27 +0200
Message-ID: <CACQW0ErFzLR_MbPYx+e3TR-o0-5ExFxwVkySwf6S6C8CdOcqzw@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: lp-wan <lp-wan@ietf.org>, 6lo@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009a827605a36448b3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/GJ6FawgHJGDsMxZ9v9t76yFlQp0>
Subject: Re: [6lo] [lp-wan] RFC 8724 on SCHC: Generic Framework for Static Context Header Compression and Fragmentation
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2020 08:33:17 -0000

Congrats to the WG and everyone that has contributed in this monumental
task of building the bridge between Non-IP LPWAN world and the world of the
IP!

And yes, looking forward to the many things that will have SCHC Inside ;)

Cheers,
Alex


On Thu, Apr 16, 2020 at 8:44 AM Carsten Bormann <cabo@tzi.org> wrote:

> Congratulations!
>
> After area-context header compression, RFC 6282 in 2011, this is another
> milestone of header compression to bring IP to constrained environments.
> Looking forward towards many things being built on top of this!
>
> Grüße, Carsten
>
>
> > On 2020-04-16, at 04:39, rfc-editor@rfc-editor.org wrote:
> >
> > 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
> >
> >
> > _______________________________________________
> > 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
>