draft-ietf-bess-srv6-services-00.txt   draft-ietf-bess-srv6-services-01.txt 
BESS Working Group BESS Working Group
Internet-Draft Internet-Draft
Intended status: Standards Track G. Dawra, Ed. Intended status: Standards Track G. Dawra, Ed.
Expires: April 17, 2020 LinkedIn Expires: May 6, 2020 LinkedIn
C. Filsfils C. Filsfils
P. Brissette
S. Agrawal
Cisco Systems Cisco Systems
J. Leddy
Individual
D. Voyer
D. Bernier
Bell Canada
D. Steinberg
Steinberg Consulting
R. Raszuk R. Raszuk
Bloomberg LP Bloomberg LP
B. Decraene B. Decraene
Orange Orange
S. Matsushima
SoftBank
S. Zhuang S. Zhuang
Huawei Technologies Huawei Technologies
J. Rabadan J. Rabadan
Nokia Nokia
October 15, 2019 November 3, 2019
SRv6 BGP based Overlay services SRv6 BGP based Overlay services
draft-ietf-bess-srv6-services-00 draft-ietf-bess-srv6-services-01
Abstract Abstract
This draft defines procedures and messages for SRv6-based BGP This draft defines procedures and messages for SRv6-based BGP
services including L3VPN, EVPN and Internet services. It builds on services including L3VPN, EVPN and Internet services. It builds on
RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and RFC7432 RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and RFC7432
"BGP MPLS-Based Ethernet VPN". "BGP MPLS-Based Ethernet VPN".
Requirements Language Requirements Language
skipping to change at page 2, line 20 skipping to change at page 2, line 7
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 April 17, 2020. This Internet-Draft will expire on May 6, 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 2, line 42 skipping to change at page 2, line 29
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. SRv6 Services TLVs . . . . . . . . . . . . . . . . . . . . . 4 2. SRv6 Services TLVs . . . . . . . . . . . . . . . . . . . . . 4
2.1. SRv6 Service Sub-TLVs . . . . . . . . . . . . . . . . . . 5 2.1. SRv6 Service Sub-TLVs . . . . . . . . . . . . . . . . . . 5
2.1.1. SRv6 SID Information Sub-TLV . . . . . . . . . . . . 6 2.1.1. SRv6 SID Information Sub-TLV . . . . . . . . . . . . 5
2.1.2. SRv6 Service Data Sub-Sub-TLVs . . . . . . . . . . . 7 2.1.2. SRv6 Service Data Sub-Sub-TLVs . . . . . . . . . . . 6
3. BGP based L3 service over SRv6 . . . . . . . . . . . . . . . 9 3. BGP based L3 service over SRv6 . . . . . . . . . . . . . . . 9
3.1. IPv4 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 10 3.1. IPv4 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 9
3.2. IPv6 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 10 3.2. IPv6 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 10
3.3. Global IPv4 over SRv6 Core . . . . . . . . . . . . . . . 11 3.3. Global IPv4 over SRv6 Core . . . . . . . . . . . . . . . 10
3.4. Global IPv6 over SRv6 Core . . . . . . . . . . . . . . . 11 3.4. Global IPv6 over SRv6 Core . . . . . . . . . . . . . . . 10
4. BGP based Ethernet VPN (EVPN) over SRv6 . . . . . . . . . . . 12 4. BGP based Ethernet VPN (EVPN) over SRv6 . . . . . . . . . . . 11
4.1. Ethernet Auto-discovery route over SRv6 Core . . . . . . 12 4.1. Ethernet Auto-discovery route over SRv6 Core . . . . . . 11
4.1.1. Per-ES A-D route . . . . . . . . . . . . . . . . . . 13 4.1.1. Per-ES A-D route . . . . . . . . . . . . . . . . . . 12
4.1.2. Per-EVI A-D route . . . . . . . . . . . . . . . . . . 13 4.1.2. Per-EVI A-D route . . . . . . . . . . . . . . . . . . 12
4.2. MAC/IP Advertisement route over SRv6 Core . . . . . . . . 13
4.2. MAC/IP Advertisement route over SRv6 Core . . . . . . . . 14 4.3. Inclusive Multicast Ethernet Tag Route over SRv6 Core . . 15
4.3. Inclusive Multicast Ethernet Tag Route over SRv6 Core . . 16 4.4. Ethernet Segment route over SRv6 Core . . . . . . . . . . 16
4.4. Ethernet Segment route over SRv6 Core . . . . . . . . . . 17
4.5. IP prefix route over SRv6 Core . . . . . . . . . . . . . 17 4.5. IP prefix route over SRv6 Core . . . . . . . . . . . . . 17
4.6. EVPN multicast routes (Route Types 6, 7, 8) over SRv6 4.6. EVPN multicast routes (Route Types 6, 7, 8) over SRv6
core . . . . . . . . . . . . . . . . . . . . . . . . . . 18 core . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5. Encoding SRv6 SID information . . . . . . . . . . . . . . . . 18 5. Encoding SRv6 SID information . . . . . . . . . . . . . . . . 18
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 19
7. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 20 7. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 19
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
8.1. BGP Prefix-SID TLV Types registry . . . . . . . . . . . . 21 8.1. BGP Prefix-SID TLV Types registry . . . . . . . . . . . . 21
8.2. SRv6 Service Sub-TLV Types registry . . . . . . . . . . . 22 8.2. SRv6 Service Sub-TLV Types registry . . . . . . . . . . . 21
8.3. SRv6 Service Data Sub-Sub-TLV Types registry . . . . . . 22 8.3. SRv6 Service Data Sub-Sub-TLV Types registry . . . . . . 21
9. Security Considerations . . . . . . . . . . . . . . . . . . . 22 9. Security Considerations . . . . . . . . . . . . . . . . . . . 22
10. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 23 10. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 22
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
11.1. Normative References . . . . . . . . . . . . . . . . . . 23 11.1. Normative References . . . . . . . . . . . . . . . . . . 22
11.2. Informative References . . . . . . . . . . . . . . . . . 24 11.2. Informative References . . . . . . . . . . . . . . . . . 23
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 26 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
1. Introduction 1. Introduction
SRv6 refers to Segment Routing instantiated on the IPv6 dataplane [I- SRv6 refers to Segment Routing instantiated on the IPv6 dataplane [I-
D.ietf-spring-srv6-network-programming][I-D.ietf-6man-segment-routing D.ietf-spring-srv6-network-programming][I-D.ietf-6man-segment-routing
-header]. -header].
SRv6 based BGP services refers to the L3 and L2 overlay services with SRv6 based BGP services refers to the L3 and L2 overlay services with
BGP as control plane and SRv6 as dataplane. BGP as control plane and SRv6 as dataplane.
skipping to change at page 8, line 40 skipping to change at page 8, line 34
achieve more efficient packing of those service prefix NLRIs in BGP achieve more efficient packing of those service prefix NLRIs in BGP
update messages. The SRv6 SID Structure Sub-Sub-TLV MUST be included update messages. The SRv6 SID Structure Sub-Sub-TLV MUST be included
with the appropriate length fields when the SRv6 Service SID is with the appropriate length fields when the SRv6 Service SID is
signaled in split parts to enable the receiver to put together the signaled in split parts to enable the receiver to put together the
SID accurately. SID accurately.
Transposition Offset indicates the bit position and Transposition Transposition Offset indicates the bit position and Transposition
Length indicates the number of bits that are being taken out of the Length indicates the number of bits that are being taken out of the
SRv6 SID value and put into high order bits of label field. The bits SRv6 SID value and put into high order bits of label field. The bits
that have been shifted out MUST be set to 0 in the SID value. that have been shifted out MUST be set to 0 in the SID value.
Transposition Offset MUST be byte aligned.
Transposition Length of 0 indicates nothing is transposed and that Transposition Length of 0 indicates nothing is transposed and that
the entire SRv6 SID value is encoded in the SID Information sub-TLV. the entire SRv6 SID value is encoded in the SID Information sub-TLV.
In this case, the Transposition Offset MUST be set to 0. In this case, the Transposition Offset MUST be set to 0.
Since size of label field is 24 bits, only that many bits can be Since size of label field is 24 bits, only that many bits can be
transposed from the SRv6 SID value into it. transposed from the SRv6 SID value into it.
The SRv6 SID Structure Sub-Sub-TLV is optional and MAY be included The SRv6 SID Structure Sub-Sub-TLV is optional and MAY be included
when the entire SRv6 Service SID value is encoded in the SID when the entire SRv6 Service SID value is encoded in the SID
skipping to change at page 9, line 48 skipping to change at page 9, line 44
Service SID. Service SID.
Assuming best-effort connectivity to the egress PE, the SR policy has Assuming best-effort connectivity to the egress PE, the SR policy has
a path with a SID list made up of a single SID - the SRv6 Service SID a path with a SID list made up of a single SID - the SRv6 Service SID
received with the related BGP route update. received with the related BGP route update.
However, when the received route is colored with an extended color However, when the received route is colored with an extended color
community 'C' and Next-Hop 'N', and the ingress PE has a valid SRv6 community 'C' and Next-Hop 'N', and the ingress PE has a valid SRv6
Policy (C, N) associated with SID list <S1,S2, S3> [I-D.filsfils- Policy (C, N) associated with SID list <S1,S2, S3> [I-D.filsfils-
spring-segment-routing-policy], then the effective SR Policy is <S1, spring-segment-routing-policy], then the effective SR Policy is <S1,
S2, S3, SRv6-Service-SID>. S2, S3-Service-SID>.
Multiple VPN routes MAY resolve recursively via the same SR Policy. Multiple VPN routes MAY resolve recursively via the same SR Policy.
3.1. IPv4 VPN Over SRv6 Core 3.1. IPv4 VPN Over SRv6 Core
IPv4 VPN Over IPv6 Core is defined in [RFC5549]. The MP_REACH_NLRI The MP_REACH_NLRI for SRv6 core is encoded according to IPv4 VPN Over
is encoded as follows for an SRv6 Core: IPv6 Core defined in [RFC5549].
o AFI = 1
o SAFI = 128
o Length of Next Hop Network Address = 16 (or 32)
o Network Address of Next Hop = IPv6 address of the egress PE
o NLRI = IPv4-VPN routes
o Label = It is set to Implicit NULL when the SID Structure Sub-Sub- Label field of IPv4-VPN NLRI is set to Implicit NULL when the SID
TLV is not present or when it is present and indicates that the Structure Sub-Sub-TLV is not present or when it is present and
Function is encoded in the SID value (refer Section 5 for indicates that the Function is encoded in the SID value (refer
details). Otherwise it carries the Function part of SRv6 SID when Section 5 for details). Otherwise it carries the Function part of
indicated as such by the SID Structure Sub-Sub-TLV. SRv6 SID when indicated as such by the SID Structure Sub-Sub-TLV.
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
behavior of the SRv6 SID is entirely up to the originator of the behavior of the SRv6 SID is entirely up to the originator of the
advertisement. In practice, the behavior SHOULD be End.DX4 or advertisement. In practice, the behavior SHOULD be End.DX4 or
End.DT4. End.DT4.
3.2. IPv6 VPN Over SRv6 Core 3.2. IPv6 VPN Over SRv6 Core
IPv6 VPN over IPv6 Core is defined in [RFC4659]. The MP_REACH_NLRI The MP_REACH_NLRI for SRv6 core is encoded according to IPv6 VPN over
is encoded as follows for an SRv6 Core: IPv6 Core is defined in [RFC4659].
o AFI = 2
o SAFI = 128
o Length of Next Hop Network Address = 24 (or 48)
o Network Address of Next Hop = 8 octets of RD set to 0 followed by
IPv6 address of the egress PE
o NLRI = IPv6-VPN routes
o Label = It is set to Implicit NULL when the SID Structure Sub-Sub- Label field set to Implicit NULL when the SID Structure Sub-Sub-TLV
TLV is not present or when it is present and indicates that the is not present or when it is present and indicates that the Function
Function is encoded in the SID value (refer Section 5 for is encoded in the SID value (refer Section 5 for details). Otherwise
details). Otherwise it carries the Function part of SRv6 SID when it carries the Function part of SRv6 SID when indicated as such by
indicated as such by the SID Structure Sub-Sub-TLV. the SID Structure Sub-Sub-TLV.
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
behavior of the SRv6 SID is entirely up to the originator of the behavior of the SRv6 SID is entirely up to the originator of the
advertisement. In practice, the behavior SHOULD be End.DX6 or advertisement. In practice, the behavior SHOULD be End.DX6 or
End.DT6. End.DT6.
3.3. Global IPv4 over SRv6 Core 3.3. Global IPv4 over SRv6 Core
IPv4 over IPv6 Core is defined in [RFC5549]. The MP_REACH_NLRI is The MP_REACH_NLRI for SRv6 core is encoded according to IPv4 over
encoded with: IPv6 Core is defined in [RFC5549].
o AFI = 1
o SAFI = 1
o Length of Next Hop Network Address = 16 (or 32)
o Network Address of Next Hop = IPv6 address of Next Hop
o NLRI = IPv4 routes
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
behavior of the SRv6 SID is entirely up to the originator of the behavior of the SRv6 SID is entirely up to the originator of the
advertisement. In practice, the behavior SHOULD be End.DX4 or advertisement. In practice, the behavior SHOULD be End.DX4 or
End.DT4. End.DT4.
3.4. Global IPv6 over SRv6 Core 3.4. Global IPv6 over SRv6 Core
The MP_REACH_NLRI is encoded with: The MP_REACH_NLRI for SRv6 core is encoded according to [RFC2545]
o AFI = 2
o SAFI = 1
o Length of Next Hop Network Address = 16 (or 32)
o Network Address of Next Hop = IPv6 address of Next Hop
o NLRI = IPv6 routes
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
behavior of the SRv6 SID is entirely up to the originator of the behavior of the SRv6 SID is entirely up to the originator of the
advertisement. In practice, the behavior SHOULD be End.DX4 or advertisement. In practice, the behavior SHOULD be End.DX6 or
End.DT6. End.DT6.
Also, by utilizing the SRv6 L3 Service TLV to encode the Global SID, Also, by utilizing the SRv6 L3 Service TLV to encode the Global SID,
a BGP free core is possible by encapsulating all BGP traffic from a BGP free core is possible by encapsulating all BGP traffic from
edge to edge over SRv6 dataplane. edge to edge over SRv6 dataplane.
4. BGP based Ethernet VPN (EVPN) over SRv6 4. BGP based Ethernet VPN (EVPN) over SRv6
Ethernet VPN(EVPN), as defined in [RFC7432] provides an extendable Ethernet VPN(EVPN), as defined in [RFC7432] provides an extendable
method of building an EVPN overlay. It primarily focuses on MPLS method of building an EVPN overlay. It primarily focuses on MPLS
skipping to change at page 21, line 19 skipping to change at page 20, line 25
atleast one constituent SRv6 Service TLV that is malformed. In such atleast one constituent SRv6 Service TLV that is malformed. In such
cases, the attribute MUST be discarded [RFC7606]and not propagated cases, the attribute MUST be discarded [RFC7606]and not propagated
further. Note that if a path whose BGP Prefix-SID attribute is further. Note that if a path whose BGP Prefix-SID attribute is
discarded in this manner is selected as the best path to be installed discarded in this manner is selected as the best path to be installed
in the RIB, traffic forwarding for the corresponding prefix may be in the RIB, traffic forwarding for the corresponding prefix may be
affected. Implementations MAY choose to make such paths less affected. Implementations MAY choose to make such paths less
preferable or even ineligible during the selection of best path for preferable or even ineligible during the selection of best path for
the corresponding prefix. the corresponding prefix.
SRv6 SID value in SRv6 Service Sub-TLV is invalid when SID Structure SRv6 SID value in SRv6 Service Sub-TLV is invalid when SID Structure
Sub-Sub-TLV is present and transposition length is greater than 24. Sub-Sub-TLV is present and transposition length is greater than 24 or
addition of transposition offset and length is greater than 128.
Path pointing to such Prefix-SID Attribute should be ineligible Path pointing to such Prefix-SID Attribute should be ineligible
during the selection of best path for the corresponding prefix. during the selection of best path for the corresponding prefix.
A BGP speaker receiving a path containing BGP Prefix-SID Attribute A BGP speaker receiving a path containing BGP Prefix-SID Attribute
with one or more SRv6 Service TLVs observes the following rules when with one or more SRv6 Service TLVs observes the following rules when
advertising the received path to other peers: advertising the received path to other peers:
o if the nexthop is unchanged during advertisement, the SRv6 Service o if the nexthop is unchanged during advertisement, the SRv6 Service
TLVs, including any unrecognized Types of Sub-TLV and Sub-Sub-TLV, TLVs, including any unrecognized Types of Sub-TLV and Sub-Sub-TLV,
SHOULD be propagated further. In addition, all Reserved fields in SHOULD be propagated further. In addition, all Reserved fields in
skipping to change at page 23, line 25 skipping to change at page 22, line 34
Filsfils, C., Sivabalan, S., Hegde, S., Filsfils, C., Sivabalan, S., Hegde, S.,
daniel.voyer@bell.ca, d., Lin, S., bogdanov@google.com, daniel.voyer@bell.ca, d., Lin, S., bogdanov@google.com,
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.ietf-6man-segment-routing-header] [I-D.ietf-6man-segment-routing-header]
Filsfils, C., Dukes, D., Previdi, S., Leddy, J., Filsfils, C., Dukes, D., Previdi, S., Leddy, J.,
Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header
Routing Header (SRH)", draft-ietf-6man-segment-routing- (SRH)", draft-ietf-6man-segment-routing-header-26 (work in
header-25 (work in progress), October 2019. progress), October 2019.
[I-D.ietf-spring-srv6-network-programming] [I-D.ietf-spring-srv6-network-programming]
Filsfils, C., Camarillo, P., Leddy, J., Filsfils, C., Camarillo, P., Leddy, J., Voyer, D.,
daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 Matsushima, S., and Z. Li, "SRv6 Network Programming",
Network Programming", draft-ietf-spring-srv6-network- draft-ietf-spring-srv6-network-programming-05 (work in
programming-04 (work in progress), October 2019. progress), October 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route
Reflection: An Alternative to Full Mesh Internal BGP Reflection: An Alternative to Full Mesh Internal BGP
(IBGP)", RFC 4456, DOI 10.17487/RFC4456, April 2006, (IBGP)", RFC 4456, DOI 10.17487/RFC4456, April 2006,
<https://www.rfc-editor.org/info/rfc4456>. <https://www.rfc-editor.org/info/rfc4456>.
skipping to change at page 25, line 17 skipping to change at page 24, line 17
Gredler, H., and B. Decraene, "IS-IS Extensions for Gredler, H., and B. Decraene, "IS-IS Extensions for
Segment Routing", draft-ietf-isis-segment-routing- Segment Routing", draft-ietf-isis-segment-routing-
extensions-25 (work in progress), May 2019. extensions-25 (work in progress), May 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-02 (work in progress), spring-srv6-deployment-status-02 (work in progress),
October 2019. October 2019.
[RFC2545] Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol
Extensions for IPv6 Inter-Domain Routing", RFC 2545,
DOI 10.17487/RFC2545, March 1999,
<https://www.rfc-editor.org/info/rfc2545>.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001,
<https://www.rfc-editor.org/info/rfc3032>. <https://www.rfc-editor.org/info/rfc3032>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>. <https://www.rfc-editor.org/info/rfc4271>.
skipping to change at page 26, line 12 skipping to change at page 25, line 16
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
July 2018, <https://www.rfc-editor.org/info/rfc8402>. July 2018, <https://www.rfc-editor.org/info/rfc8402>.
Appendix A. Contributors Appendix A. Contributors
Satoru Matsushima
SoftBank
Email: satoru.matsushima@g.softbank.co.jp
Dirk Steinberg
Steinberg Consulting
Email: dws@steinberg.net
Daniel Bernier
Bell Canada
Email: daniel.bernier@bell.ca
Daniel Voyer
Bell Canada
Email: daniel.voyer@bell.ca
Jonn Leddy
Individual
Email: john@leddy.net
Swadesh Agrawal
Cisco
Email: swaagraw@cisco.com
Patrice Brissette
Cisco
Email: pbrisset@cisco.com
Ali Sajassi Ali Sajassi
Cisco Cisco
Email: sajassi@cisco.com Email: sajassi@cisco.com
Bart Peirens Bart Peirens
Proximus Proximus
Belgium Belgium
Email: bart.peirens@proximus.com Email: bart.peirens@proximus.com
skipping to change at page 27, line 4 skipping to change at page 26, line 41
Cisco Cisco
Email: zali@cisco.com Email: zali@cisco.com
Ketan Talaulikar Ketan Talaulikar
Cisco Cisco
Email: ketant@cisco.com Email: ketant@cisco.com
Authors' Addresses Authors' Addresses
Gaurav Dawra (editor) Gaurav Dawra (editor)
LinkedIn LinkedIn
USA USA
Email: gdawra.ietf@gmail.com Email: gdawra.ietf@gmail.com
Clarence Filsfils Clarence Filsfils
Cisco Systems Cisco Systems
Belgium Belgium
Email: cfilsfil@cisco.com Email: cfilsfil@cisco.com
Patrice Brissette
Cisco Systems
Canada
Email: pbrisset@cisco.com
Swadesh Agrawal
Cisco Systems
USA
Email: swaagraw@cisco.com
Jonn Leddy
Individual
USA
Email: john@leddy.net
Daniel Voyer
Bell Canada
Canada
Email: daniel.voyer@bell.ca
Daniel Bernier
Bell Canada
Canada
Email: daniel.bernier@bell.ca
Dirk Steinberg
Steinberg Consulting
Germany
Email: dws@steinberg.net
Robert Raszuk Robert Raszuk
Bloomberg LP Bloomberg LP
USA USA
Email: robert@raszuk.net Email: robert@raszuk.net
Bruno Decraene Bruno Decraene
Orange Orange
France France
Email: bruno.decraene@orange.com Email: bruno.decraene@orange.com
Satoru Matsushima
SoftBank
1-9-1,Higashi-Shimbashi,Minato-Ku
Japan 105-7322
Email: satoru.matsushima@g.softbank.co.jp
Shunwan Zhuang Shunwan Zhuang
Huawei Technologies Huawei Technologies
China China
Email: zhuangshunwan@huawei.com Email: zhuangshunwan@huawei.com
Jorge Rabadan Jorge Rabadan
Nokia Nokia
USA USA
 End of changes. 32 change blocks. 
149 lines changed or deleted 95 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/