SRv6 interoperability report
draft-filsfils-spring-srv6-interop-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Clarence Filsfils , Francois Clad , Pablo Camarillo , Ahmed Abdelsalam , Stefano Salsano , Olivier Bonaventure , Jakub Horn , Jose Liste | ||
| Last updated | 2019-09-05 (Latest revision 2019-03-04) | ||
| 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
Segment Routing (SR) can be applied to the IPv6 data plane by leveraging a new type of routing extension header, called Segment Routing Header (SRH). An SRH contains an ordered list, or sequence, of segments representing topological or service-based instructions, or any combination of those. This draft provides an overview of IPv6 Segment Routing (SRv6) implementations and interoperability. It makes an inventory of the various pieces of hardware and software that have been demonstrated to support the processing of an SRH, and details some interoperability scenarios that have been showcased at a public event.
Authors
Clarence Filsfils
Francois Clad
Pablo Camarillo
Ahmed Abdelsalam
Stefano Salsano
Olivier Bonaventure
Jakub Horn
Jose Liste
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)