PCE Working Group Shankar Raman
Internet draft Balaji Venkat
Intended Status: Experimental RFC Gaurav Raina
Expires: July 2013 I.I.T, Madras
January 25, 2013
Constructing protection paths for inter-AS, inter-sub-AS P2MP TE-LSPs
draft-mjsraman-pce-inter-as-p2mp-protect-03
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.
Status of this Memo
This Internet-Draft is submitted to IETF 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
Shankar Raman.et.al Expires July 2013 [Page 1]
INTERNET DRAFT Inter-AS/sub-AS disjoint P2MP TE-LSPs January 2013
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/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License 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.
Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Methodology of the proposal . . . . . . . . . . . . . . . . . . 3
3 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 Discussion of Algorithms to be used . . . . . . . . . . . . 9
4 Security Considerations . . . . . . . . . . . . . . . . . . . . 11
5 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 11
6 References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1 Normative References . . . . . . . . . . . . . . . . . . . 11
6.2 Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
Shankar Raman.et.al Expires July 2013 [Page 2]
INTERNET DRAFT Inter-AS/sub-AS disjoint P2MP TE-LSPs January 2013
1 Introduction
In the context of P2MP TE-LSPs being constructed for carriage of
multicast traffic across multiple areas within a given AS employing
BGP confederations where such an autonomous system may comprise of
more than one BGP confederation instance, and if such multicast
traffic is mission critical traffic then it would be most useful to
have backup protection trees (where such trees represent entire P2MP