Signaling RSVP-TE P2MP LSPs in an Inter-domain Environment
draft-ietf-mpls-inter-domain-p2mp-rsvp-te-lsp-01
| Document | Type | Expired Internet-Draft (mpls WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2013-04-12) | ||
| Replaces | draft-ali-mpls-inter-domain-p2mp-rsvp-te-lsp | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Dead WG Document | |
| Document shepherd | Loa Andersson | ||
| Shepherd write-up | Show (last changed 2013-05-21) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Adrian Farrel | ||
| IESG note | Loa Andersson <loa@pi.nu> is the document shepherd | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-mpls-inter-domain-p2mp-rsvp-te-lsp-01.txt
Abstract
Point-to-MultiPoint (P2MP) Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) are established using signaling procedures defined in [RFC4875]. However, [RFC4875] does not address several issues that arise when a P2MP-TE LSP is signaled in inter-domain networks. One such issue is the computation of a loosely routed inter-domain P2MP- TE LSP paths that are re-merge free. Another issue is the reoptimization of the inter-domain P2MP-TE LSP tree vs. an individual destination(s), since the loosely routing domain ingress border node is not aware of the reoptimization scope. This document defines the required protocol extensions needed for establishing and reoptimizing P2MP MPLS and GMPLS TE LSPs in inter-domain networks.
Authors
Zafar Ali
(zali@cisco.com)
Rakesh Gandhi
(rgandhi@cisco.com)
Tarek Saad
(tsaad@cisco.com)
Robert Venator
(robert.h.venator.civ@mail.mil)
Yuji Kamite
(y.kamite@ntt.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)