Resilient MPLS Rings and Multicast
draft-ietf-mpls-rmr-multicast-00
| Document | Type |
Expired Internet-Draft
(mpls WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhaohui (Jeffrey) Zhang , Santosh Esale | ||
| Last updated | 2020-02-14 (Latest revision 2019-08-13) | ||
| Replaces | draft-zzhang-mpls-rmr-multicast | ||
| 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 | Expired | |
| 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
With Resilient MPLS Rings (RMR), although all existing multicast procedures and solutions can work as is, there are optimizations that could be done for RSVP-TE P2MP tunnel signaling and Fast-ReRouting for both mLDP and RSVP-TE P2MP tunnels. This document describes RMR multicast on a high level, with detailed protocol procedure for RSVP- TE P2MP optimizations specified in a separate document. This document also discusses end to end multicast when there are RMRs.
Authors
Zhaohui (Jeffrey) Zhang
Santosh Esale
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)