Simplemux. A generic multiplexing protocol
draft-saldana-tsvwg-simplemux-07

Document Type Active Internet-Draft (individual)
Last updated 2017-07-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml 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)
Transport Area Working Group                                  J. Saldana
Internet-Draft                                    University of Zaragoza
Intended status: Standards Track                           July 31, 2017
Expires: February 1, 2018

              Simplemux.  A generic multiplexing protocol
                    draft-saldana-tsvwg-simplemux-07

Abstract

   The high amount of small packets present in nowaday's networks
   results in a low efficiency, as the size of the headers and the
   payload of these packets can be in the same order of magnitude.  In
   some situations, multiplexing a number of small packets into a bigger
   one is desirable in order to improve the efficiency.  For example, a
   number of small packets can be sent together between a pair of
   machines if they share a common network path.  Thus, the traffic
   profile can be shifted from small to larger packets, reducing the
   network overhead and the number of packets per second to be managed
   by intermediate routers.

   This document describes Simplemux, a protocol able to encapsulate a
   number of packets belonging to different protocols into a single
   packet.  Small headers (separators) are added at the beginning of
   each multiplexed packet, including some flags, the packet length and
   a "Protocol" field.  This allows the inclusion of a number of packets
   belonging to different protocols (the "multiplexed packets") on a
   packet of another protocol (the "tunneling protocol").

   In order to reduce the overhead, the size of the multiplexing headers
   is kept very low (it may be a single byte when multiplexing small
   packets).

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

Saldana                 Expires February 1, 2018                [Page 1]
Internet-Draft                  Simplemux                      July 2017

   This Internet-Draft will expire on February 1, 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
   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Existing multiplexing protocols . . . . . . . . . . . . .   3
     1.3.  Benefits of multiplexing  . . . . . . . . . . . . . . . .   5
   2.  Description of the scenario . . . . . . . . . . . . . . . . .   6
   3.  Protocol description  . . . . . . . . . . . . . . . . . . . .   6
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The high amount of small packets present in nowaday's networks
   results in a low efficiency, when the size of the headers and the
   payload are in the same order of magnitude.  In some situations,
   multiplexing a number of small packets into a bigger one is desirable
   in order to improve the efficiency.  For example, a number of small
   packets can be sent together between a pair of machines if they share
   a common network path.  Thus, the traffic profile can be shifted from
   small to larger packets, thus reducing the network overhead and the
   number of packets per second to be managed by intermediate routers.

   This document describes Simplemux, a protocol able to encapsulate a
   number of packets belonging to different protocols into a single
   packet.  This can be useful e.g. for grouping small packets and thus
Show full document text