LPWAN Static Context Header Compression (SCHC) and fragmentation for IPv6 and UDP
draft-ietf-lpwan-ipv6-static-context-hc-04

Document Type Active Internet-Draft (lpwan WG)
Last updated 2017-06-16
Replaces draft-toutain-lpwan-ipv6-static-context-hc
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd Dominique Barthel
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Dominique Barthel <dominique.barthel@orange.com>
lpwan Working Group                                          A. Minaburo
Internet-Draft                                                    Acklio
Intended status: Informational                                L. Toutain
Expires: December 18, 2017                                IMT-Atlantique
                                                                C. Gomez
                                    Universitat Politecnica de Catalunya
                                                           June 16, 2017

  LPWAN Static Context Header Compression (SCHC) and fragmentation for
                              IPv6 and UDP
               draft-ietf-lpwan-ipv6-static-context-hc-04

Abstract

   This document describes a header compression scheme and fragmentation
   functionality for very low bandwidth networks.  These techniques are
   especially tailored for LPWAN (Low Power Wide Area Network) networks.

   The Static Context Header Compression (SCHC) offers a great level of
   flexibility when processing the header fields and must be used for
   this kind of networks.  A common context stored in a LPWAN device and
   in the network is used.  This context stores information that will
   not be transmitted in the constrained network.  Static context means
   that information stored in the context which describes field values,
   does not change during packet transmission, avoiding complex
   resynchronization mechanisms, incompatible with LPWAN
   characteristics.  In most of the cases, IPv6/UDP headers are reduced
   to a small identifier called Rule ID.  But sometimes the SCHC header
   compression will not be enough to send the packet in one L2 PDU, so
   this document also describes a Fragmentation protocol that must be
   used when needed.

   This document describes the generic compression/decompression
   mechanism and applies it to IPv6/UDP headers.  Similar mechanisms for
   other protocols such as CoAP will be described in separate documents.
   Moreover, this document specifies fragmentation and reassembly
   mechanims for SCHC compressed packets exceeding the L2 PDU size and
   for the case where the SCHC compression is not possible then the
   IPv6/UDP packet is sent using the fragmentation protocol.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute

Minaburo, et al.        Expires December 18, 2017               [Page 1]
Internet-Draft                 LPWAN SCHC                      June 2017

   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 18, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  LPWAN Architecture  . . . . . . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Static Context Header Compression . . . . . . . . . . . . . .   6
     4.1.  SCHC Rules  . . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Rule ID . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.3.  Packet processing . . . . . . . . . . . . . . . . . . . .   9
   5.  Matching operators  . . . . . . . . . . . . . . . . . . . . .  10
   6.  Compression Decompression Actions (CDA) . . . . . . . . . . .  11
     6.1.  not-sent CDA  . . . . . . . . . . . . . . . . . . . . . .  12
     6.2.  value-sent CDA  . . . . . . . . . . . . . . . . . . . . .  12
     6.3.  mapping-sent  . . . . . . . . . . . . . . . . . . . . . .  12
     6.4.  LSB CDA . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.5.  DEViid, APPiid CDA  . . . . . . . . . . . . . . . . . . .  13
Show full document text