SRv6 End.M behavior for traversing MPLS Networks
draft-li-spring-srv6-end-mpls-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhenbin Li , Cheng Li | ||
| Last updated | 2021-10-21 (Latest revision 2021-04-19) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
As the development of cloud computing, increasing services have been migrated from enterprise sites to clouds, so the connection between sites and clouds are critical for enterprises. SRv6 provides a sourcing routing mechanism to connect the enterprise sites and clouds by programming the end-to-end path at the ingress node. In this scenario, the SRv6 packets may traverse multiple network domains and some of them may not be SRv6-capable. In order to support SRv6 end-to-end path programming, this document defines the mechanism of SRv6 traversing MPLS networks, which supports encoding MPLS tunnel information in the SRH.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)