GPCOMP
draft-moskowitz-gpcomp-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-27
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                       R. Moskowitz
Internet-Draft                                                  S. Hares
Intended status: Standards Track                                  Huawei
Expires: April 30, 2017                                      I. Faynberg
                                              Stargazers Consulting, LLC
                                                                   H. Lu
                                                                 Retired
                                                             P. Giacomin
                                                               FreeLance
                                                        October 27, 2016

                                 GPCOMP
                     draft-moskowitz-gpcomp-01.txt

Abstract

   This document describes a protocol intended to provide lossless
   compression for use within any datagram.  It is particularly intended
   for use in encrypted datagrams where lower-level compression is
   ineffective.

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."

   This Internet-Draft will expire on April 30, 2017.

Copyright Notice

   Copyright (c) 2016 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

Moskowitz, et al.        Expires April 30, 2017                 [Page 1]
Internet-Draft    Generic Payload Compression Protocol      October 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Terminology  . . . . . . . . . . . . . . . .   3
     2.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Compression Process . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Compressed Payload  . . . . . . . . . . . . . . . . . . .   3
     3.2.  Uncompressing Conundrum . . . . . . . . . . . . . . . . .   4
     3.3.  Non-Expansion Policy  . . . . . . . . . . . . . . . . . .   4
   4.  Compressed Datagram Structure . . . . . . . . . . . . . . . .   5
     4.1.  Implied Structure . . . . . . . . . . . . . . . . . . . .   5
     4.2.  GPComp header for Explicit Structure  . . . . . . . . . .   5
   5.  Negotiating GPComp  . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  The GPCA  . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Using IKEv2 . . . . . . . . . . . . . . . . . . . . . . .   6
     5.3.  Using HIP . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Generic payload compression is a protocol to reduce the size of most
   datagrams.  This protocol will increase the overall communication
   performance by compressing the datagrams, provided the participating
   devices have sufficient computation power, through either CPU
   capacity or a compression coprocessor, and the communication is over
   constrained links.

   Generic payload compression is especially useful when encryption is
   applied to datagrams.  Encrypting a datagram causes the data to be
   random in nature, rendering compression at lower protocol layers
Show full document text