Insertion of IPv6 Segment Routing Headers in a Controlled Domain
draft-voyer-6man-extension-header-insertion-04

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2018-12-24 (latest revision 2018-06-22)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
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 (daniel.voyer@bell.ca)
John Leddy (john_leddy@comcast.com)
Clarence Filsfils (cfilsfil@cisco.com)
Darren Dukes (ddukes@cisco.com)
Stefano Previdi (stefano@previdi.net)
Satoru Matsushima (satoru.matsushima@g.softbank.co.jp)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)