An IP option for describing the traffic flow
draft-chodorek-traffic-flow-option-07

Document Type Active Internet-Draft (individual)
Last updated 2017-06-26
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)
Network Working Group                                    R.R. Chodorek
Internet Draft                     AGH Univ. of Science and Technology
Intended status: Experimental                            June 26, 2017
Expires: December 26, 2017

               An IP option for describing the traffic flow
                   draft-chodorek-traffic-flow-option-07

Abstract

   Information about the behavior of the stream that will be transmitted
   in the near future will allow for better management of queues in the
   router and thus improve QoS and reduce the potential for a serious
   overload. Such information is often available in the transmitter. The
   proposed IP option allows for the sending of information about
   forthcoming traffic from the transmitter to the intermediate nodes.

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on December 26, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors. All rights reserved.

Chodorek              Expires December 26, 2017               [Page 1]
Internet-Draft      IP option forthcoming traffic            June 2017

   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. Introduction ................................................ 2
   2. Traffic Flow Description option ............................. 3
   3. Procedures .................................................. 6
      3.1. The streaming application .............................. 7
      3.2. The elastic application ................................ 7
   4. Security Considerations ..................................... 7
   5. IANA Considerations ......................................... 7
   6. References .................................................. 8
      6.1. Normative References ................................... 8
      6.2. Informative References ................................. 8

1. Introduction

   Information about the behavior of the stream that will be transmitted
   in the near future will allow for better management of queues in the
   router and thus improve QoS and reduce the potential for a serious
   overload. Such information is often available in the transmitter.
   Information on the amount of data that in the near future will be
   sent by the application can be derived from measurements taken in the
   output buffer or as a result of prediction (e.g. the prediction of
   video traffic [Cho2002]). This information can be used for dynamic
   bandwidth allocation (e.g. the extension to RSVP protocol, based on
   dynamic resource reservations [Cho2010] or prediction-based bandwidth
   renegotiation module [Cho2003]).

   The proposed IP Traffic Flow Description (TFD) Hop-by-Hop option
   allows for the sending of information about forthcoming traffic from
   the transmitter to the intermediate nodes. The proposed IP option can
   be used by applications which transmit streaming and elastic traffic.
   The proposed option will be used mainly for streaming applications
   because streaming applications are typically self-limited (have a
   limited output bandwidth depending to properties of transmitted media
   and used compression and coding).

Chodorek              Expires December 26, 2017               [Page 2]
Internet-Draft      IP option forthcoming traffic            June 2017

   The proposed option can be used to active queues (e.g. RED) or fair
   queuing (e.g. WFQ).
Show full document text