Diet-IPsec: ESP Payload Compression of IPv6 / UDP / TCP / UDP-Lite
draft-mglt-6lo-diet-esp-payload-compression-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-01-08
Replaced by draft-mglt-ipsecme-diet-esp
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
6lo                                                      D. Migault, Ed.
Internet-Draft                                                    Orange
Intended status: Standards Track                        T. Guggemos, Ed.
Expires: July 12, 2015                                        LMU Munich
                                                        January 08, 2015

   Diet-IPsec: ESP Payload Compression of IPv6 / UDP / TCP / UDP-Lite
           draft-mglt-6lo-diet-esp-payload-compression-00.txt

Abstract

   ESP is a IPsec protocol that takes as input a Clear Text Data and
   outputs an encrypted ESP packet according to IPsec rules and
   parameters stored in different IPsec databases.

   Diet-ESP compresses the ESP fields.  However, Diet-ESP does not
   consider compression of the Clear Text Data.  Instead, if compression
   of the Clear Text Data is expected protocols like ROHCoverIPsec can
   be used.

   ROHCoverIPsec remains complex to implement in IoT devices, as states,
   and negotiations are involved between the compressors and
   decompressors of the two IoT devices.  Most of this complexity can be
   avoided by considering the parameters that have been negotiated by
   IPsec.

   This document describes an extension of the Diet-ESP Context that
   enables the compression of the Clear Text Data, without implementing
   the complex ROHCoverIPsec framework.  As opposed to ROHCoverIPsec the
   compression is not generic and as such all communication will not
   benefit from this compression.  However, we believe this extension
   addresses most of IoT communications.

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
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Migault & Guggemos       Expires July 12, 2015                  [Page 1]
Internet-Draft                  Diet-ESP                    January 2015

   This Internet-Draft will expire on July 12, 2015.

Copyright Notice

   Copyright (c) 2015 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.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Diet-ESP Context Extension  . . . . . . . . . . . . . . . . .   4
   5.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   5
   6.  IP Layer Compression  . . . . . . . . . . . . . . . . . . . .   6
   7.  UDP Transport Layer Compression . . . . . . . . . . . . . . .   8
   8.  UDP-Lite Transport Layer Compression  . . . . . . . . . . . .   9
   9.  TCP Transport Layer Compression . . . . . . . . . . . . . . .  10
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  11
   12. Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .  11
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     13.2.  Informational References . . . . . . . . . . . . . . . .  12
   Appendix A.  Interaction with ROHC profiles . . . . . . . . . . .  12
   Appendix B.  Document Change Log  . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   Diet-ESP [I-D.mglt-6lo-diet-esp] describes how to compress ESP
   fields.  Fields are compressed according to a Diet-ESP Context.

Migault & Guggemos       Expires July 12, 2015                  [Page 2]
Internet-Draft                  Diet-ESP                    January 2015
Show full document text