Skip to main content

Domain Subobjects for Resource ReserVation Protocol - Traffic Engineering (RSVP-TE)
draft-dhody-ccamp-rsvp-te-domain-subobjects-02

Document Type Replaced Internet-Draft (ccamp WG)
Expired & archived
Authors Dhruv Dhody , Udayasree Palle , Venugopal Reddy Kondreddy , Ramon Casellas
Last updated 2013-10-04 (Latest revision 2013-07-09)
Replaced by draft-ietf-ccamp-rsvp-te-domain-subobjects
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-ccamp-rsvp-te-domain-subobjects
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The Resource ReserVation Protocol - Traffic Engineering (RSVP-TE) specification [RFC3209] and the Generalized Multiprotocol Label Switching (GMPLS) extensions to RSVP-TE [RFC3473] allow abstract nodes and resources to be explicitly included in a path setup. Further Exclude Routes extensions [RFC4874] allow abstract nodes and resources to be explicitly excluded in a path setup. This document specifies new subobjects to include or exclude domains during path setup where domain is a collection of network elements within a common sphere of address management or path computational responsibility (such as an Interior Gateway Protocol (IGP) area or an Autonomous System (AS)). Note that the use of AS as an abstract node representing domain is already defined in [RFC3209] and [RFC4874], albeit with a 2-Byte AS number.

Authors

Dhruv Dhody
Udayasree Palle
Venugopal Reddy Kondreddy
Ramon Casellas

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)