SRv6-based BGP Service Capability
draft-lz-bess-srv6-service-capability-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Yao Liu , Zheng Zhang , Eduard Metz | ||
| Last updated | 2023-09-13 (Latest revision 2023-03-12) | ||
| RFC stream | (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
This draft describes the problems that may be encountered during the deployment of SRv6-based BGP services in the co-existence scenario where the network supports both SRv6 and MPLS in a given domain, and the possible solutions.
Authors
Yao Liu
Zheng Zhang
Eduard Metz
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)