Tunneling Compressed Multiplexed Traffic Flows (TCMTF)
draft-saldana-tsvwg-tcmtf-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-02-16
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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)
Transport Area Working Group                             J. Saldana, Ed.
Internet-Draft                                    University of Zaragoza
Obsoletes: 4170 (if approved)                          February 16, 2012
Intended status: BCP
Expires: August 19, 2012

         Tunneling Compressed Multiplexed Traffic Flows (TCMTF)
                      draft-saldana-tsvwg-tcmtf-00

Abstract

   This document describes a method to improve the bandwidth utilization
   of network paths that carry multiple streams in parallel between two
   endpoints, as in voice trunking.  The method combines standard
   protocols that provide compression, multiplexing, and tunneling over
   a network path for the purpose of reducing the bandwidth used when
   multiple streams are carried over that path.

Status of this Memo

   This Internet-Draft is submitted to IETF 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 August 19, 2012.

Copyright Notice

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

Saldana                  Expires August 19, 2012                [Page 1]
Internet-Draft                    TCMTF                    February 2012

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
     1.2.  Bandwidth efficiency of real-time flows  . . . . . . . . .  3
     1.3.  Real-time applications not using RTP . . . . . . . . . . .  4
     1.4.  Scenarios of application . . . . . . . . . . . . . . . . .  5
     1.5.  Objective of this standard . . . . . . . . . . . . . . . .  5
     1.6.  Overview of Protocols  . . . . . . . . . . . . . . . . . .  6
   2.  Protocol Operation . . . . . . . . . . . . . . . . . . . . . .  8
     2.1.  Models of implementation . . . . . . . . . . . . . . . . .  8
     2.2.  Choice of the compressing protocol . . . . . . . . . . . .  9
       2.2.1.  Context Synchronization in ECRTP . . . . . . . . . . . 10
       2.2.2.  Context Synchronization in ROHC  . . . . . . . . . . . 10
     2.3.  Multiplexing . . . . . . . . . . . . . . . . . . . . . . . 10
       2.3.1.  Tunneling Inefficiencies . . . . . . . . . . . . . . . 11
     2.4.  Tunneling  . . . . . . . . . . . . . . . . . . . . . . . . 11
     2.5.  Encapsulation Formats  . . . . . . . . . . . . . . . . . . 11
   3.  Contributing Authors . . . . . . . . . . . . . . . . . . . . . 13
   4.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 14
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 16
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16

Saldana                  Expires August 19, 2012                [Page 2]
Internet-Draft                    TCMTF                    February 2012

1.  Introduction

   This document describes a way to combine existing protocols for
   compression, multiplexing, and tunneling to save bandwidth for some
   applications that generate small packets, such as real-time ones.

1.1.  Requirements Language

   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 RFC 2119 [RFC2119].

1.2.  Bandwidth efficiency of real-time flows

   In the last years we are witnessing the raise of new real-time
Show full document text