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

Document Type Active Internet-Draft (individual)
Last updated 2018-07-25
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                         July 25, 2018 
    Expires: January 25, 2019 
                                       
     
                                        
                  An IP option for describing the traffic flow 
                     draft-chodorek-traffic-flow-option-09   

    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).  Note that other groups may also distribute 
       working documents as Internet-Drafts.  The list of current 
       Internet-Drafts is at 
       https://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 January 25, 2019. 

    Copyright Notice 

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

     
     
     
    Chodorek              Expires January 25, 2019            [Page 1] 
     


    Internet-Draft      IP option forthcoming traffic          July 2018 
        

       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 ............................................... 7 
          3.1. The streaming application ........................... 7 
          3.2. The elastic application ............................. 7 
       4. Security Considerations .................................. 8 
       5. IANA Considerations ...................................... 8 
       6. References ............................................... 8 
          6.1. Normative References ................................ 8 
          6.2. Informative References .............................. 9 
        
    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 

     
     
    Chodorek              Expires January 25, 2019            [Page 2] 
        


Show full document text