Insertion of IPv6 Segment Routing Headers in a Controlled Domain
draft-voyer-6man-extension-header-insertion-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Daniel Voyer , John Leddy , Clarence Filsfils , Darren Dukes , Stefano Previdi , Satoru Matsushima | ||
| Last updated | 2018-12-24 (Latest revision 2018-06-22) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-voyer-6man-extension-header-insertion-04.txt
Abstract
The network operator and vendor community has clearly indicated that IPv6 header insertion is useful and required. This is notably the case when the entire journey of the packet remains in its source domain. In such a context, it does not matter where the extension header is inserted. The source domain may decide to place the IPv6 extension header insertion where it suits its best: at the source of the packet or at any midpoint within the source domain.
Authors
Daniel Voyer
John Leddy
Clarence Filsfils
Darren Dukes
Stefano Previdi
Satoru Matsushima
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)