draft-ietf-6man-segment-routing-header-06.txt   draft-ietf-6man-segment-routing-header-07.txt 
Network Working Group S. Previdi, Ed. Network Working Group S. Previdi, Ed.
Internet-Draft C. Filsfils Internet-Draft C. Filsfils
Intended status: Standards Track K. Raza Intended status: Standards Track K. Raza
Expires: September 14, 2017 D. Dukes Expires: January 21, 2018 D. Dukes
Cisco Systems, Inc. Cisco Systems, Inc.
J. Leddy J. Leddy
B. Field B. Field
Comcast Comcast
D. Voyer D. Voyer
D. Bernier D. Bernier
Bell Canada Bell Canada
S. Matsushima S. Matsushima
Softbank Softbank
I. Leung I. Leung
skipping to change at page 1, line 32 skipping to change at page 1, line 32
T. Kosugi T. Kosugi
NTT NTT
E. Vyncke E. Vyncke
Cisco Systems, Inc. Cisco Systems, Inc.
D. Lebrun D. Lebrun
Universite Catholique de Louvain Universite Catholique de Louvain
D. Steinberg D. Steinberg
Steinberg Consulting Steinberg Consulting
R. Raszuk R. Raszuk
Bloomberg Bloomberg
March 13, 2017 July 20, 2017
IPv6 Segment Routing Header (SRH) IPv6 Segment Routing Header (SRH)
draft-ietf-6man-segment-routing-header-06 draft-ietf-6man-segment-routing-header-07
Abstract Abstract
Segment Routing (SR) allows a node to steer a packet through a Segment Routing (SR) allows a node to steer a packet through a
controlled set of instructions, called segments, by prepending an SR controlled set of instructions, called segments, by prepending an SR
header to the packet. A segment can represent any instruction, header to the packet. A segment can represent any instruction,
topological or service-based. SR allows to enforce a flow through topological or service-based. SR allows to enforce a flow through
any path (topological, or application/service based) while any path (topological, or application/service based) while
maintaining per-flow state only at the ingress node to the SR domain. maintaining per-flow state only at the ingress node to the SR domain.
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 September 14, 2017. This Internet-Draft will expire on January 21, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 28, line 23 skipping to change at page 28, line 23
---------------------------------------------------------- ----------------------------------------------------------
4 Segment Routing Header (SRH) This document 4 Segment Routing Header (SRH) This document
This document request IANA to create and maintain a new Registry: This document request IANA to create and maintain a new Registry:
"Segment Routing Header TLVs" "Segment Routing Header TLVs"
7.1. Segment Routing Header TLVs Register 7.1. Segment Routing Header TLVs Register
This document requests the creation of a new IANA managed registry to This document requests the creation of a new IANA managed registry to
identify SRH TLVs. The registration procedure is "Expert Review" as identify SRH TLVs. The registration procedure is "Expert Review" as
defined in [RFC5226]. Suggested registry name is "Segment Routing defined in [RFC8126]. Suggested registry name is "Segment Routing
Header TLVs". A TLV is identified through an unsigned 8 bit Header TLVs". A TLV is identified through an unsigned 8 bit
codepoint value. The following codepoints are defined in this codepoint value. The following codepoints are defined in this
document: document:
Suggested Description Reference Suggested Description Reference
Value Value
----------------------------------------------------- -----------------------------------------------------
1 Ingress Node TLV This document 1 Ingress Node TLV This document
2 Egress Node TLV This document 2 Egress Node TLV This document
3 Opaque Container TLV This document 3 Opaque Container TLV This document
skipping to change at page 30, line 10 skipping to change at page 30, line 10
Steinberg, D., Raszuk, R., Decraene, B., and S. Steinberg, D., Raszuk, R., Decraene, B., and S.
Matsushima, "BGP Signaling of IPv6-Segment-Routing-based Matsushima, "BGP Signaling of IPv6-Segment-Routing-based
VPN Networks", draft-dawra-bgp-srv6-vpn-00 (work in VPN Networks", draft-dawra-bgp-srv6-vpn-00 (work in
progress), March 2017. progress), March 2017.
[I-D.filsfils-spring-srv6-network-programming] [I-D.filsfils-spring-srv6-network-programming]
Filsfils, C., Leddy, J., daniel.voyer@bell.ca, d., Filsfils, C., Leddy, J., daniel.voyer@bell.ca, d.,
daniel.bernier@bell.ca, d., Steinberg, D., Raszuk, R., daniel.bernier@bell.ca, d., Steinberg, D., Raszuk, R.,
Matsushima, S., Lebrun, D., Decraene, B., Peirens, B., Matsushima, S., Lebrun, D., Decraene, B., Peirens, B.,
Salsano, S., Naik, G., Elmalky, H., Jonnalagadda, P., Salsano, S., Naik, G., Elmalky, H., Jonnalagadda, P.,
Sharif, M., Ayyangar, A., Mynam, S., Bashandy, A., Raza, Sharif, M., Ayyangar, A., Mynam, S., Henderickx, W.,
K., Dukes, D., Clad, F., and P. Camarillo, "SRv6 Network Bashandy, A., Raza, K., Dukes, D., Clad, F., and P.
Programming", draft-filsfils-spring-srv6-network- Camarillo, "SRv6 Network Programming", draft-filsfils-
programming-00 (work in progress), March 2017. spring-srv6-network-programming-01 (work in progress),
June 2017.
[I-D.ietf-isis-l2bundles] [I-D.ietf-isis-l2bundles]
Ginsberg, L., Bashandy, A., Filsfils, C., Previdi, S., Ginsberg, L., Bashandy, A., Filsfils, C., Nanduri, M., and
Nanduri, M., and E. Aries, "Advertising L2 Bundle Member E. Aries, "Advertising L2 Bundle Member Link Attributes in
Link Attributes in IS-IS", draft-ietf-isis-l2bundles-03 IS-IS", draft-ietf-isis-l2bundles-07 (work in progress),
(work in progress), February 2017. May 2017.
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., Previdi, S., Filsfils, C., Bashandy, A., Gredler, H.,
Litkowski, S., Decraene, B., and j. jefftant@gmail.com, Litkowski, S., Decraene, B., and j. jefftant@gmail.com,
"IS-IS Extensions for Segment Routing", draft-ietf-isis- "IS-IS Extensions for Segment Routing", draft-ietf-isis-
segment-routing-extensions-11 (work in progress), March segment-routing-extensions-13 (work in progress), June
2017. 2017.
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] [I-D.ietf-ospf-ospfv3-segment-routing-extensions]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H., Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3
Extensions for Segment Routing", draft-ietf-ospf-ospfv3- Extensions for Segment Routing", draft-ietf-ospf-ospfv3-
segment-routing-extensions-09 (work in progress), March segment-routing-extensions-09 (work in progress), March
2017. 2017.
[I-D.ietf-sfc-nsh] [I-D.ietf-sfc-nsh]
Quinn, P. and U. Elzur, "Network Service Header", draft- Quinn, P., Elzur, U., and C. Pignataro, "Network Service
ietf-sfc-nsh-12 (work in progress), February 2017. Header (NSH)", draft-ietf-sfc-nsh-16 (work in progress),
July 2017.
[I-D.ietf-spring-ipv6-use-cases] [I-D.ietf-spring-ipv6-use-cases]
Brzozowski, J., Leddy, J., Filsfils, C., Maglione, R., and Brzozowski, J., Leddy, J., Filsfils, C., Maglione, R., and
W. Townsley, "IPv6 SPRING Use Cases", draft-ietf-spring- M. Townsley, "IPv6 SPRING Use Cases", draft-ietf-spring-
ipv6-use-cases-09 (work in progress), February 2017. ipv6-use-cases-11 (work in progress), June 2017.
[I-D.ietf-spring-resiliency-use-cases] [I-D.ietf-spring-resiliency-use-cases]
Filsfils, C., Previdi, S., Decraene, B., and R. Shakir, Filsfils, C., Previdi, S., Decraene, B., and R. Shakir,
"Resiliency use cases in SPRING networks", draft-ietf- "Resiliency use cases in SPRING networks", draft-ietf-
spring-resiliency-use-cases-08 (work in progress), October spring-resiliency-use-cases-11 (work in progress), May
2016. 2017.
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
and R. Shakir, "Segment Routing Architecture", draft-ietf- and R. Shakir, "Segment Routing Architecture", draft-ietf-
spring-segment-routing-11 (work in progress), February spring-segment-routing-12 (work in progress), June 2017.
2017.
[I-D.ietf-spring-segment-routing-mpls] [I-D.ietf-spring-segment-routing-mpls]
Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., Filsfils, C., Previdi, S., Bashandy, A., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing with MPLS Litkowski, S., and R. Shakir, "Segment Routing with MPLS
data plane", draft-ietf-spring-segment-routing-mpls-08 data plane", draft-ietf-spring-segment-routing-mpls-10
(work in progress), March 2017. (work in progress), June 2017.
[I-D.previdi-idr-segment-routing-te-policy] [I-D.previdi-idr-segment-routing-te-policy]
Previdi, S., Filsfils, C., Sreekantiah, A., Sivabalan, S., Previdi, S., Filsfils, C., Mattes, P., Rosen, E., and S.
Mattes, P., Rosen, E., and S. Lin, "Advertising Segment Lin, "Advertising Segment Routing Policies in BGP", draft-
Routing Policies in BGP", draft-previdi-idr-segment- previdi-idr-segment-routing-te-policy-07 (work in
routing-te-policy-05 (work in progress), February 2017. progress), June 2017.
[RFC1940] Estrin, D., Li, T., Rekhter, Y., Varadhan, K., and D. [RFC1940] Estrin, D., Li, T., Rekhter, Y., Varadhan, K., and D.
Zappala, "Source Demand Routing: Packet Format and Zappala, "Source Demand Routing: Packet Format and
Forwarding Specification (Version 1)", RFC 1940, Forwarding Specification (Version 1)", RFC 1940,
DOI 10.17487/RFC1940, May 1996, DOI 10.17487/RFC1940, May 1996,
<http://www.rfc-editor.org/info/rfc1940>. <http://www.rfc-editor.org/info/rfc1940>.
[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,
skipping to change at page 31, line 44 skipping to change at page 31, line 43
[RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering: [RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering:
Defeating Denial of Service Attacks which employ IP Source Defeating Denial of Service Attacks which employ IP Source
Address Spoofing", BCP 38, RFC 2827, DOI 10.17487/RFC2827, Address Spoofing", BCP 38, RFC 2827, DOI 10.17487/RFC2827,
May 2000, <http://www.rfc-editor.org/info/rfc2827>. May 2000, <http://www.rfc-editor.org/info/rfc2827>.
[RFC4942] Davies, E., Krishnan, S., and P. Savola, "IPv6 Transition/ [RFC4942] Davies, E., Krishnan, S., and P. Savola, "IPv6 Transition/
Co-existence Security Considerations", RFC 4942, Co-existence Security Considerations", RFC 4942,
DOI 10.17487/RFC4942, September 2007, DOI 10.17487/RFC4942, September 2007,
<http://www.rfc-editor.org/info/rfc4942>. <http://www.rfc-editor.org/info/rfc4942>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[RFC6554] Hui, J., Vasseur, JP., Culler, D., and V. Manral, "An IPv6 [RFC6554] Hui, J., Vasseur, JP., Culler, D., and V. Manral, "An IPv6
Routing Header for Source Routes with the Routing Protocol Routing Header for Source Routes with the Routing Protocol
for Low-Power and Lossy Networks (RPL)", RFC 6554, for Low-Power and Lossy Networks (RPL)", RFC 6554,
DOI 10.17487/RFC6554, March 2012, DOI 10.17487/RFC6554, March 2012,
<http://www.rfc-editor.org/info/rfc6554>. <http://www.rfc-editor.org/info/rfc6554>.
[RFC7855] Previdi, S., Ed., Filsfils, C., Ed., Decraene, B., [RFC7855] Previdi, S., Ed., Filsfils, C., Ed., Decraene, B.,
Litkowski, S., Horneffer, M., and R. Shakir, "Source Litkowski, S., Horneffer, M., and R. Shakir, "Source
Packet Routing in Networking (SPRING) Problem Statement Packet Routing in Networking (SPRING) Problem Statement
and Requirements", RFC 7855, DOI 10.17487/RFC7855, May and Requirements", RFC 7855, DOI 10.17487/RFC7855, May
2016, <http://www.rfc-editor.org/info/rfc7855>. 2016, <http://www.rfc-editor.org/info/rfc7855>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<http://www.rfc-editor.org/info/rfc8126>.
Authors' Addresses Authors' Addresses
Stefano Previdi (editor) Stefano Previdi (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Via Del Serafico, 200
Rome 00142
Italy Italy
Email: sprevidi@cisco.com Email: stefano@previdi.net
Clarence Filsfils Clarence Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
Brussels Brussels
BE BE
Email: cfilsfil@cisco.com Email: cfilsfil@cisco.com
Kamran Raza Kamran Raza
Cisco Systems, Inc. Cisco Systems, Inc.
 End of changes. 18 change blocks. 
36 lines changed or deleted 35 lines changed or added

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