LPWAN Static Context Header Compression (SCHC) and fragmentation for IPv6 and UDP
lpwan Working Group A. Minaburo
Intended status: Informational L. Toutain
Expires: September 11, 2017 IMT-Atlantique
Universitat Politecnica de Catalunya
March 10, 2017
LPWAN Static Context Header Compression (SCHC) and fragmentation for
IPv6 and UDP
This document describes a header compression scheme and fragmentation
functionality for IPv6/UDP protocols. These techniques are
especially tailored for LPWAN (Low Power Wide Area Network) networks
and could be extended to other protocol stacks.
The Static Context Header Compression (SCHC) offers a great level of
flexibility when processing the header fields. Static context means
that information stored in the context which, describes field values,
does not change during the packet transmission, avoiding complex
resynchronization mechanisms, incompatible with LPWAN
characteristics. In most of the cases, IPv6/UDP headers are reduced
to a small identifier.
This document describes the generic compression/decompression process
and applies it to IPv6/UDP headers. Similar mechanisms for other
protocols such as CoAP will be described in a separate document.
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.
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 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
Minaburo, et al. Expires September 11, 2017 [Page 1]
Internet-Draft LPWAN SCHC March 2017
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 September 11, 2017.
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.
Header compression is mandatory to efficiently bring Internet
connectivity to the node within a LPWAN network
Some LPWAN networks properties can be exploited for an efficient
o Topology is star oriented, therefore all the packets follow the
same path. For the needs of this draft, the architecture can be
summarized to Things or End-Systems (ES) exchanging information
with LPWAN Application Server (LA) through a Network Gateway (NG).
o Traffic flows are mostly known in advanced, since End-Systems
embed built-in applications. Contrary to computers or
smartphones, new applications cannot be easily installed.
The Static Context Header Compression (SCHC) is defined for this
environment. SCHC uses a context where header information is kept in
order, this context is static the values on the header fields do not
change during time, avoiding complex resynchronization mechanisms,
incompatible with LPWAN characteristics. In most of the cases, IPv6/
UDP headers are reduced to a small context identifier.
The SCHC header compression is indedependent of the specific LPWAN
technology over which it will be used.
Minaburo, et al. Expires September 11, 2017 [Page 2]
Internet-Draft LPWAN SCHC March 2017
On the other hand, LPWAN technologies are characterized, among
others, by a very reduced data unit and/or payload size
[I-D.ietf-lpwan-overview]. However, some of these technologies do
Show full document text