Generic Aggregation of Resource ReSerVation Protocol (RSVP) for IPv4 And IPv6 Reservations over PCN domains
draft-ietf-tsvwg-rsvp-pcn-05

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Authors Georgios Karagiannis  , Anurag Bhargava 
Last updated 2013-07-13
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Spencer Dawkins
Send notices to tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-rsvp-pcn@tools.ietf.org
Internet Engineering Task Force                     Georgios Karagiannis
Internet-Draft                                      University of Twente
Intended status: Experimental                         Anurag Bhargava
Expires: January 14, 2014                            Cisco Systems, Inc.
                                                       July 14, 2013

        Generic Aggregation of Resource ReSerVation Protocol (RSVP) 
              for IPv4 And IPv6 Reservations over PCN domains    
                     draft-ietf-tsvwg-rsvp-pcn-05

Abstract

   This document specifies extensions to Generic Aggregated RSVP  
   [RFC4860] for support of the PCN Controlled Load (CL) and Single 
   Marking (SM) edge behaviors over a Diffserv cloud using Pre-
   Congestion Notification. 
   

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 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 January 14, 2014.
   

Karagiannis, et al.   Expires January 14, 2014                  [Page 1]
Internet-Draft       Aggregated RSVP over PCN           July 2013      

Copyright Notice

   Copyright (c) 2013 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

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

Table of Contents
1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 
   1.1. Objective   . . . . . . . . . . . . . . . . . . . . . . . . .  4
   1.2. Overview and Motivation . . . . . . . . . . . . . . . . . . .  4
   1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . .  7
   1.4. Organization of This Document . . . . . . . . . . . . . . . . 11
2.  Overview of RSVP extensions and Operations . . . . . . . . . . .  11 
2.1. Overview of RSVP Aggregation Procedures in PCN domains . . . . . 11 
2.2. PCN Marking and encoding and transport of pre-congestion 
     Information . . . . . . . . . . . . . . . . . . . . . . . . . .  13 
2.3. Traffic Classification Within The Aggregation Region . . . . . . 13 
2.4. Deaggregator (PCN-egress-node) Determination . . . . . . . . . . 13
2.5. Mapping E2E Reservations Onto Aggregate Reservations . . . . . . 14 
2.6  Size of Aggregate Reservations . . . . . . . . . . . . . . . . . 14 
2.7. E2E Path ADSPEC update . . . . . . . . . . . . . . . . . . . . . 14 
2.8. Intra-domain Routes . . . . . . . . . . . . . . . . . . . . . . .14
2.9.  Inter-domain Routes . . . . . . . . . . . . . . . . . . . . . . 14
2.10. Reservations for Multicast Sessions . . . . . . . . . . . . . . 14
2.11. Multi-level Aggregation . . . . . . . . . . . . . . . . . . . . 15
2.12. Reliability Issues . . . . . . . . . . . . . . . . . . . . . .  15
2.13.  Message Integrity and Node Authentication . . . . . . . . . .  15
3. Elements of Procedure . . . . . . . . . . . . . . . . . . . . . .  15 
3.1.  Receipt of E2E Path Message By PCN-ingress-node 
     (aggregating router) . . . . . . . . . . . . . . . . . . . . . . 15 
3.2.  Handling Of E2E Path Message By Interior Routers . . . . . . .  16 
3.3.  Receipt of E2E Path Message By PCN-egress-node 
     (deaggregating router) . . . . . . . . . . . . . . . . . . . . . 16
3.4.  Initiation of new Aggregate Path Message By PCN-ingress-node 
      (Aggregating Router) . . . . . . . . . . . . . . . . . . . . .  17 
3.5.  Handling Of new Aggregate Path Message By Interior Routers . .  17 
3.6.  Handling of E2E Resv Message by Deaggregating Router . . . . .  17 
3.7.  Handling Of E2E Resv Message By Interior Routers . . . . . . .  17 
3.8. Initiation of New Aggregate Resv Message By Deaggregating Router 17
Show full document text