Skip to main content

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

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Daniel Voyer , Daniel Bernier , John Leddy , Clarence Filsfils , Stefano Previdi , Stefano Salsano , Antonio Cianfrani , David Lebrun , Olivier Bonaventure , Prem Jonnalagadda , Milad Sharif , Hani Elmalky , Ahmed Abdelsalam , Robert Raszuk , Arthi Ayyangar , Dirk Steinberg , Wim Henderickx
Last updated 2017-09-29 (Latest revision 2017-03-28)
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

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 Bernier
John Leddy
Clarence Filsfils
Stefano Previdi
Stefano Salsano
Antonio Cianfrani
David Lebrun
Olivier Bonaventure
Prem Jonnalagadda
Milad Sharif
Hani Elmalky
Ahmed Abdelsalam
Robert Raszuk
Arthi Ayyangar
Dirk Steinberg
Wim Henderickx

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