RSVP Extensions for Dynamic Reservation
draft-chodorek-tsvwg-rsvp-dynamic-resv-04

Document Type Active Internet-Draft (individual)
Last updated 2016-12-23
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                             A. Chodorek
Expires: June 23, 2017                 Kielce University of Technology
                                                     December 23, 2016

                  RSVP Extensions for Dynamic Reservation
                 draft-chodorek-tsvwg-rsvp-dynamic-resv-04

Abstract

   RSVP reservations are static in nature and typically last for the
   whole session. The proposed extension to the RSVP allows the RSVP to
   make elastic adjustments to reservations for the current demand of
   network resources. The proposed method dynamically changes the RSVP
   reservations on the basis of knowledge about transmitted traffic.

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 June 23, 2017.

Copyright Notice

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

Chodorek                Expires June 23, 2017                 [Page 1]
Internet-Draft       RSVP Extensions for Dynamic         December 2016

   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. RSVP Dynamic Reservation Protocol Mechanisms ................ 3
   3. RSVP Dynamic Reservation Message Formats .................... 3
      3.1. The new Flag definition in the Common Header ........... 4
      3.2. The PathChange Messages ................................ 4
      3.3. The ResvChange Messages ................................ 4
   4. RSVP Dynamic Reservation Objects ............................ 5
      4.1. SENDER_TCHSPEC Object .................................. 5
      4.2. FLOWCHANGESPEC Class ................................... 8
   5. Security Considerations .................................... 11
   6. IANA Considerations ........................................ 11
   7. References ................................................. 11
      7.1. Normative References .................................. 11
      7.2. Informative References ................................ 12

1. Introduction

   The proposed extension to the Resource ReserVation Protocol (RSVP)
   [RFC2205] enables reservations to be changed dynamically in the event
   of changes to network resource requirements for the transmitted
   multimedia stream. The proposed extension, in many cases, allows for
   the release of some of the network resources, allowing for their
   utilization by other transmissions. In practice, released resources
   can be used for the transmission of elastic traffic (e.g. the traffic
   observed during transmissions carried out using the TCP or other
   reliable transport protocols).

   Information about the behavior of the stream that will be transmitted
   in the near future is often available in the transmitter. It can be
   derived, for instance, from measurements taken in the output buffer
   or as a result of traffic predictions [Cho2002]. This information can
   be used in intermediate nodes for dynamic bandwidth allocation
   [Cho2010] (as, for example, the prediction-based bandwidth
   renegotiation module [Cho2003]).

Chodorek                Expires June 23, 2017                 [Page 2]
Internet-Draft       RSVP Extensions for Dynamic         December 2016

Show full document text