datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

Constructing protection paths for inter-AS, inter-sub-AS P2MP TE-LSPs
draft-mjsraman-pce-inter-as-p2mp-protect-03

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-07-29 (latest revision 2013-01-25)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-mjsraman-pce-inter-as-p2mp-protect-03.txt

Abstract

Constructing primary and backup explicit path Point-to-Multipoint Label Switched Paths is important from the point of view of providing protection switching in case the primary fails. It is absolutely essential that the backup P2MP LSPs constructed do not share risk with any of the links and nodes of the primary path. In the case of inter-AS P2MP TE-LSPs or in the case of inter-sub-AS (in the case of BGP-Confederations being deployed) P2MP TE-LSPs where BGP confederations are deployed within an AS, such protection switching can be provided by calculating primary and backup multicast distribution trees (read P2MP TE-LSPs) that dont intersect with each other. In this paper we propose a method by which inter-sub-AS P2MP TE-LSPs (hence even inter-AS P2MP TE-LSPs) can be constructed by first finding the AS level topology of the network (be it inter-AS or inter-sub-AS within a single AS) in question and secondly to compute the paths in such a way that they dont intersect or if necessary in the worst case partially intersect each other. The proposed scheme is explained with an example and subsequent discussion is done to elucidate its benefits to multicast in particular.

Authors

Shankar Raman <mjsraman@cse.iitm.ac.in>
Balaji Venkat <balajivenkat299@gmail.com>
Gaurav Raina <gaurav@ee.iitm.ac.in>

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