LPWAN Static Context Header Compression (SCHC) and fragmentation for IPv6 and UDP
draft-ietf-lpwan-ipv6-static-context-hc-09
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (lpwan WG)
|
|
Last updated |
|
2017-12-22
|
|
Replaces |
|
draft-toutain-lpwan-ipv6-static-context-hc
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
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: June 25, 2018 IMT-Atlantique
C. Gomez
Universitat Politecnica de Catalunya
December 22, 2017
LPWAN Static Context Header Compression (SCHC) and fragmentation for
IPv6 and UDP
draft-ietf-lpwan-ipv6-static-context-hc-09
Abstract
This document describes a header compression scheme and fragmentation
functionality for very low bandwidth networks. These techniques are
specially tailored for Low Power Wide Area Network (LPWAN).
The Static Context Header Compression (SCHC) offers a great level of
flexibility when processing the header fields. SCHC compression is
based on a common static context stored in a LPWAN device and in the
network. Static context means that the stored information does not
change during packet transmission. The context describes the field
values and keeps information that will not be transmitted through the
constrained network.
SCHC must be used for LPWAN networks because it avoids complex
resynchronization mechanisms, which are incompatible with LPWAN
characteristics. And also, because with SCHC, in most cases IPv6/UDP
headers can be reduced to a small identifier called Rule ID. Even
though, sometimes, a SCHC compressed packet will not fit in one L2
PDU, and the SCHC fragmentation protocol defined in this document may
be used.
This document describes the SCHC compression/decompression framework
and applies it to IPv6/UDP headers. This document also specifies a
fragmentation and reassembly mechanism that is used to support the
IPv6 MTU requirement over LPWAN technologies. Fragmentation is
mandatory for IPv6 datagrams that, after SCHC compression or when it
has not been possible to apply such compression, still exceed the L2
maximum payload size. Similar solutions for other protocols such as
CoAP will be described in separate documents.
Minaburo, et al. Expires June 25, 2018 [Page 1]
Internet-Draft LPWAN SCHC December 2017
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
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://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 June 25, 2018.
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
(https://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 . . . . . . . . . . . . . . . . . . . . . . . . 4
2. LPWAN Architecture . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Static Context Header Compression . . . . . . . . . . . . . . 7
4.1. SCHC Rules . . . . . . . . . . . . . . . . . . . . . . . 8
4.2. Rule ID . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3. Packet processing . . . . . . . . . . . . . . . . . . . . 10
4.4. Matching operators . . . . . . . . . . . . . . . . . . . 12
4.5. Compression Decompression Actions (CDA) . . . . . . . . . 12
4.5.1. not-sent CDA . . . . . . . . . . . . . . . . . . . . 13
4.5.2. value-sent CDA . . . . . . . . . . . . . . . . . . . 13
4.5.3. mapping-sent . . . . . . . . . . . . . . . . . . . . 14
4.5.4. LSB CDA . . . . . . . . . . . . . . . . . . . . . . . 14
4.5.5. DEViid, APPiid CDA . . . . . . . . . . . . . . . . . 14
Minaburo, et al. Expires June 25, 2018 [Page 2]
Show full document text