< draft-voyer-6man-extension-header-insertion-05.txt   draft-voyer-6man-extension-header-insertion-06.txt >
Network Working Group D. Voyer, Ed. Network Working Group D. Voyer, Ed.
Internet-Draft Bell Canada Internet-Draft Bell Canada
Intended status: Informational J. Leddy Intended status: Informational J. Leddy
Expires: July 15, 2019 Individual Contributor Expires: January 9, 2020 Individual Contributor
C. Filsfils C. Filsfils
D. Dukes, Ed. D. Dukes, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
S. Previdi S. Previdi
Individual Contributor Individual Contributor
S. Matsushima S. Matsushima
Softbank Softbank
January 11, 2019 July 8, 2019
Insertion of IPv6 Segment Routing Headers in a Controlled Domain Insertion of IPv6 Segment Routing Headers in a Controlled Domain
draft-voyer-6man-extension-header-insertion-05 draft-voyer-6man-extension-header-insertion-06
Abstract Abstract
The network operator and vendor community has clearly indicated that The network operator and vendor community has clearly indicated that
IPv6 header insertion is useful and required. This is notably the IPv6 header insertion is useful and required. This is notably the
case when the entire journey of the packet remains in its source case when the entire journey of the packet remains in its source
domain. In such a context, it does not matter where the extension domain. In such a context, it does not matter where the extension
header is inserted. The source domain may decide to place the IPv6 header is inserted. The source domain may decide to place the IPv6
extension header insertion where it suits its best: at the source of extension header insertion where it suits its best: at the source of
the packet or at any midpoint within the source domain. the packet or at any midpoint within the source domain.
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 15, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 7, line 51 skipping to change at page 7, line 51
b., Krol, P., Horneffer, M., Steinberg, D., Decraene, B., b., Krol, P., Horneffer, M., Steinberg, D., Decraene, B.,
Litkowski, S., Mattes, P., Ali, Z., Talaulikar, K., Liste, Litkowski, S., Mattes, P., Ali, Z., Talaulikar, K., Liste,
J., Clad, F., and K. Raza, "Segment Routing Policy J., Clad, F., and K. Raza, "Segment Routing Policy
Architecture", draft-filsfils-spring-segment-routing- Architecture", draft-filsfils-spring-segment-routing-
policy-06 (work in progress), May 2018. policy-06 (work in progress), May 2018.
[I-D.filsfils-spring-srv6-network-programming] [I-D.filsfils-spring-srv6-network-programming]
Filsfils, C., Camarillo, P., Leddy, J., Filsfils, C., Camarillo, P., Leddy, J.,
daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6
Network Programming", draft-filsfils-spring-srv6-network- Network Programming", draft-filsfils-spring-srv6-network-
programming-06 (work in progress), October 2018. programming-07 (work in progress), February 2019.
[I-D.ietf-6man-segment-routing-header] [I-D.ietf-6man-segment-routing-header]
Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and Filsfils, C., Dukes, D., Previdi, S., Leddy, J.,
d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment
(SRH)", draft-ietf-6man-segment-routing-header-15 (work in Routing Header (SRH)", draft-ietf-6man-segment-routing-
progress), October 2018. header-21 (work in progress), June 2019.
Authors' Addresses Authors' Addresses
Daniel Voyer (editor) Daniel Voyer (editor)
Bell Canada Bell Canada
Email: daniel.voyer@bell.ca Email: daniel.voyer@bell.ca
John Leddy John Leddy
Individual Contributor Individual Contributor
 End of changes. 6 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/