draft-ietf-6man-segment-routing-header-20.txt   draft-ietf-6man-segment-routing-header-21.txt 
Network Working Group C. Filsfils, Ed. Network Working Group C. Filsfils, Ed.
Internet-Draft D. Dukes, Ed. Internet-Draft D. Dukes, Ed.
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: December 12, 2019 S. Previdi Expires: December 15, 2019 S. Previdi
Huawei Huawei
J. Leddy J. Leddy
Individual Individual
S. Matsushima S. Matsushima
Softbank Softbank
D. Voyer D. Voyer
Bell Canada Bell Canada
June 10, 2019 June 13, 2019
IPv6 Segment Routing Header (SRH) IPv6 Segment Routing Header (SRH)
draft-ietf-6man-segment-routing-header-20 draft-ietf-6man-segment-routing-header-21
Abstract Abstract
Segment Routing can be applied to the IPv6 data plane using a new Segment Routing can be applied to the IPv6 data plane using a new
type of Routing Extension Header. This document describes the type of Routing Extension Header. This document describes the
Segment Routing Extension Header and how it is used by Segment Segment Routing Extension Header and how it is used by Segment
Routing capable nodes. Routing capable nodes.
Status of This Memo Status of This Memo
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 December 12, 2019. This Internet-Draft will expire on December 15, 2019.
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 26, line 30 skipping to change at page 26, line 30
This document makes the following registrations in the Internet This document makes the following registrations in the Internet
Protocol Version 6 (IPv6) Parameters "Routing Type" registry Protocol Version 6 (IPv6) Parameters "Routing Type" registry
maintained by IANA: maintained by IANA:
Suggested Description Reference Suggested Description Reference
Value Value
---------------------------------------------------------- ----------------------------------------------------------
4 Segment Routing Header (SRH) This document 4 Segment Routing Header (SRH) This document
This document makes the following registrations in "Type 4 -
Parameter Problem" message of the "Internet Control Message Protocol
version 6 (ICMPv6) Parameters" registry maintained by IANA:
CODE NAME/DESCRIPTION
----------------------------------------------------------
TBD IANA SR Upper-layer Header Error
This section provides guidance to the Internet Assigned Numbers This section provides guidance to the Internet Assigned Numbers
Authority (IANA) regarding registration of values related to the SRH, Authority (IANA) regarding registration of values related to the SRH,
in accordance with BCP 26, [RFC8126]. in accordance with BCP 26, [RFC8126].
The following terms are used here with the meanings defined in BCP The following terms are used here with the meanings defined in BCP
26: "namespace", "assigned value", "registration". 26: "namespace", "assigned value", "registration".
The following policies are used here with the meanings defined in BCP The following policies are used here with the meanings defined in BCP
26: "Private Use", "First Come First Served", "Expert Review", 26: "Private Use", "First Come First Served", "Expert Review",
"Specification Required", "IETF Consensus", "Standards Action". "Specification Required", "IETF Consensus", "Standards Action".
skipping to change at page 27, line 32 skipping to change at page 27, line 40
codepoint value, with assigned values 0-127 for TLVs that do not codepoint value, with assigned values 0-127 for TLVs that do not
change en route, and 128-255 for TLVs that may change en route. The change en route, and 128-255 for TLVs that may change en route. The
following codepoints are defined in this document: following codepoints are defined in this document:
Assigned Description Reference Assigned Description Reference
Value Value
----------------------------------------------------- -----------------------------------------------------
0 Pad1 TLV This document 0 Pad1 TLV This document
1 Reserved This document 1 Reserved This document
2 Reserved This document 2 Reserved This document
3 Reserved for Opaque TLV [*] 3 Reserved This document
4 PadN TLV This document 4 PadN TLV This document
5 HMAC TLV This document 5 HMAC TLV This document
6 Reserved for NSH TLV [*] 6 Reserved This document
124-126 Experimentation and Test This document 124-126 Experimentation and Test This document
127 Reserved This document 127 Reserved This document
252-254 Experimentation and Test This document 252-254 Experimentation and Test This document
255 Reserved This document 255 Reserved This document
[*] [I-D.xuclad-spring-sr-service-programming] Values 1,2,3,6 were defined in draft versions of this specification
and are Reserved for backwards compatibility with early
Values 1,2 were defined in draft versions of this specification and implementations and should not be reassigned. Values 127 and 255 are
are Reserved for backwards compatibility with early implementations. Reserved to allow for expansion of the Type field in future
Values 127 and 255 are Reserved to allow for expansion of the Type specifications if needed.
field in future specifications if needed.
9. Implementation Status 9. Implementation Status
This section is to be removed prior to publishing as an RFC. This section is to be removed prior to publishing as an RFC.
See [I-D.matsushima-spring-srv6-deployment-status] for updated See [I-D.matsushima-spring-srv6-deployment-status] for updated
deployment and interoperability reports. deployment and interoperability reports.
9.1. Linux 9.1. Linux
skipping to change at page 31, line 5 skipping to change at page 31, line 11
Salsano, S., Bonaventure, O., Horn, J., and J. Liste, Salsano, S., Bonaventure, O., Horn, J., and J. Liste,
"SRv6 interoperability report", draft-filsfils-spring- "SRv6 interoperability report", draft-filsfils-spring-
srv6-interop-02 (work in progress), March 2019. srv6-interop-02 (work in progress), March 2019.
[I-D.matsushima-spring-srv6-deployment-status] [I-D.matsushima-spring-srv6-deployment-status]
Matsushima, S., Filsfils, C., Ali, Z., and Z. Li, "SRv6 Matsushima, S., Filsfils, C., Ali, Z., and Z. Li, "SRv6
Implementation and Deployment Status", draft-matsushima- Implementation and Deployment Status", draft-matsushima-
spring-srv6-deployment-status-01 (work in progress), May spring-srv6-deployment-status-01 (work in progress), May
2019. 2019.
[I-D.xuclad-spring-sr-service-programming]
Clad, F., Xu, X., Filsfils, C., daniel.bernier@bell.ca,
d., Li, C., Decraene, B., Ma, S., Yadlapalli, C.,
Henderickx, W., and S. Salsano, "Service Programming with
Segment Routing", draft-xuclad-spring-sr-service-
programming-02 (work in progress), April 2019.
[RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed- [RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed-
Hashing for Message Authentication", RFC 2104, Hashing for Message Authentication", RFC 2104,
DOI 10.17487/RFC2104, February 1997, DOI 10.17487/RFC2104, February 1997,
<https://www.rfc-editor.org/info/rfc2104>. <https://www.rfc-editor.org/info/rfc2104>.
[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
Control Message Protocol (ICMPv6) for the Internet Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification", STD 89, Protocol Version 6 (IPv6) Specification", STD 89,
RFC 4443, DOI 10.17487/RFC4443, March 2006, RFC 4443, DOI 10.17487/RFC4443, March 2006,
<https://www.rfc-editor.org/info/rfc4443>. <https://www.rfc-editor.org/info/rfc4443>.
 End of changes. 9 change blocks. 
19 lines changed or deleted 19 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/