draft-ietf-idr-bgpls-segment-routing-epe-10.txt   draft-ietf-idr-bgpls-segment-routing-epe-11.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 Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: September 10, 2017 K. Patel Expires: September 14, 2017 K. Patel
Arrcus, Inc. Arrcus, Inc.
S. Ray S. Ray
Individual Contributor Individual Contributor
J. Dong J. Dong
M. Chen M. Chen
Huawei Technologies Huawei Technologies
March 9, 2017 March 13, 2017
Segment Routing BGP Egress Peer Engineering BGP-LS Extensions Segment Routing BGP Egress Peer Engineering BGP-LS Extensions
draft-ietf-idr-bgpls-segment-routing-epe-10 draft-ietf-idr-bgpls-segment-routing-epe-11
Abstract Abstract
Segment Routing (SR) leverages source routing. A node steers a Segment Routing (SR) leverages source routing. A node steers a
packet through a controlled set of instructions, called segments, by packet through a controlled set of instructions, called segments, by
prepending the packet with an SR header. A segment can represent any prepending the packet with an SR header. A segment can represent any
instruction, topological or service-based. SR allows to enforce a instruction, topological or service-based. SR allows to enforce a
flow through any topological path and service chain while maintaining flow through any topological path and service chain while maintaining
per-flow state only at the ingress node of the SR domain. per-flow state only at the ingress node of the SR domain.
skipping to change at page 2, line 12 skipping to change at page 2, line 12
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 10, 2017. This Internet-Draft will expire on September 14, 2017.
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 2, line 45 skipping to change at page 2, line 45
4.1. BGP Router ID and Member ASN . . . . . . . . . . . . . . 5 4.1. BGP Router ID and Member ASN . . . . . . . . . . . . . . 5
4.2. BGP-EPE Node Descriptors . . . . . . . . . . . . . . . . 6 4.2. BGP-EPE Node Descriptors . . . . . . . . . . . . . . . . 6
4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 7 4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 7
5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 9 5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 9
5.1. Peer Node Segment (Peer-Node-SID) . . . . . . . . . . . . 9 5.1. Peer Node Segment (Peer-Node-SID) . . . . . . . . . . . . 9
5.2. Peer Adjacency Segment (Peer-Adj-SID) . . . . . . . . . . 10 5.2. Peer Adjacency Segment (Peer-Adj-SID) . . . . . . . . . . 10
5.3. Peer Set Segment . . . . . . . . . . . . . . . . . . . . 11 5.3. Peer Set Segment . . . . . . . . . . . . . . . . . . . . 11
6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 12 6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 12
6.2. Peer Node Segment for Node D . . . . . . . . . . . . . . 14 6.2. Peer Node Segment for Node D . . . . . . . . . . . . . . 14
6.3. Peer Node Segment for Node H . . . . . . . . . . . . . . 14 6.3. Peer Node Segment for Node F . . . . . . . . . . . . . . 14
6.4. Peer Node Segment for Node E . . . . . . . . . . . . . . 14 6.4. Peer Node Segment for Node E . . . . . . . . . . . . . . 14
6.5. Peer Adjacency Segment for Node E, Link 1 . . . . . . . . 15 6.5. Peer Adjacency Segment for Node E, Link 1 . . . . . . . . 15
6.6. Peer Adjacency Segment for Node E, Link 2 . . . . . . . . 15 6.6. Peer Adjacency Segment for Node E, Link 2 . . . . . . . . 15
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 16 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
8.1. New BGP-LS Protocol-ID . . . . . . . . . . . . . . . . . 17 8.1. New BGP-LS Protocol-ID . . . . . . . . . . . . . . . . . 17
8.2. Node Descriptors and Link Attribute TLVs . . . . . . . . 17 8.2. Node Descriptors and Link Attribute TLVs . . . . . . . . 17
9. Manageability Considerations . . . . . . . . . . . . . . . . 18 9. Manageability Considerations . . . . . . . . . . . . . . . . 18
10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18
skipping to change at page 8, line 37 skipping to change at page 8, line 37
the purpose of load balancing. An example use of the weight is the purpose of load balancing. An example use of the weight is
described in [I-D.ietf-spring-segment-routing]. described in [I-D.ietf-spring-segment-routing].
o SID/Index/Label. According to the TLV length and to the V and L o SID/Index/Label. According to the TLV length and to the V and L
flags settings, it contains either: flags settings, it contains either:
* A 3 octet local label where the 20 rightmost bits are used for * A 3 octet local label where the 20 rightmost bits are used for
encoding the label value. In this case the V and L flags MUST encoding the label value. In this case the V and L flags MUST
be set. be set.
* A 4 octet index defining the offset in the SID/Label space * A 4 octet index defining the offset in the SRGB (Segment
advertised by this router using the encodings defined in Routing Global Block as defined in
Section 3.1. In this case V and L flags MUST be unset. [I-D.ietf-spring-segment-routing] advertised by this router.
In this case the SRGB MUST be advertised using the extensions
defined in [I-D.ietf-idr-bgp-ls-segment-routing-ext].
* A 16 octet IPv6 address. In this case the V flag MUST be set. * A 16 octet IPv6 address. In this case the V flag MUST be set.
The L flag MUST be unset if the IPv6 address is globally The L flag MUST be unset if the IPv6 address is globally
unique. unique.
The values of the Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID Sub- The values of the Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID Sub-
TLVs SHOULD be persistent across router restart. TLVs SHOULD be persistent across router restart.
The Peer-Node-SID MUST be present when BGP-LS is used for the use The Peer-Node-SID MUST be present when BGP-LS is used for the use
case described in [I-D.ietf-spring-segment-routing-central-epe] and case described in [I-D.ietf-spring-segment-routing-central-epe] and
skipping to change at page 12, line 10 skipping to change at page 12, line 10
The Peer Set Attribute contains the Peer-Set-SID TLV, defined in The Peer Set Attribute contains the Peer-Set-SID TLV, defined in
Section 4.3 identifying the set of which the Peer Node Segment or Section 4.3 identifying the set of which the Peer Node Segment or
Peer Adjacency Segment is a member. Peer Adjacency Segment is a member.
6. Illustration 6. Illustration
6.1. Reference Diagram 6.1. Reference Diagram
The following reference diagram is used throughout this document. The following reference diagram is used throughout this document.
The solution is illustrated for IPv4 with MPLS-based segments and the The solution is illustrated for IPv6 with MPLS-based segments and the
BGP-EPE topology is based on eBGP sessions between external peers. BGP-EPE topology is based on eBGP sessions between external peers.
As stated in Section 3, the solution illustrated hereafter is equally As stated in Section 3, the solution illustrated hereafter is equally
applicable to an iBGP session topology. In other words, the solution applicable to an iBGP session topology. In other words, the solution
also applies to the case where C, D, H, and E are in the same AS and also applies to the case where C, D, F, and E are in the same AS and
run iBGP sessions between each other. run iBGP sessions between each other.
+------+ +------+
| | | |
+---D F +---D H
+---------+ / | AS 2 |\ +------+ +---------+ / | AS 2 |\ +------+
| X |/ +------+ \ | Z |---L/8 | X |/ +------+ \ | Z |---L/8
A C---+ \| | A C---+ \| |
| |\\ \ +------+ /| AS 4 |---M/8 | |\\ \ +------+ /| AS 4 |---M/8
| AS1 | \\ +-H |/ +------+ | AS1 | \\ +-F |/ +------+
| | \\ | G | | \\ | G
+----P----+ +===E AS 3 | +----P----+ +===E AS 3 |
| +--Q---+ | +--Q---+
| | | |
+----------------+ +----------------+
Figure 3: Reference Diagram Figure 3: Reference Diagram
IPv4 addressing: IP addressing:
o C's IPv4 address of interface to D: 1.0.1.1/24, D's interface: o C's IP address of interface to D: 2001:db8:cd::c/64, D's
1.0.1.2/24 interface: 2001:db8:cd::d/64
o C's IPv4 address of interface to H: 1.0.2.1/24, H's interface: o C's IP address of interface to F: 2001:db8:cf::c/64, F's
1.0.2.2/24 interface: 2001:db8:cf::f/64
o C's IPv4 address of upper interface to E: 1.0.3.1/24, E's o C's IP address of upper interface to E: 2001:db8:ce1::c/64, E's
interface: 1.0.3.2/24 interface: 2001:db8:ce1::e
o C's local identifier of upper interface to E: 0.0.0.1.0.0.0.0 o C's local identifier of upper interface to E: 0.0.0.1.0.0.0.0
o C's IPv4 address of lower interface to E: 1.0.4.1/24, E's o C's IP address of lower interface to E: 2001:db8:ce2::c, E's
interface: 1.0.4.2/24 interface: 2001:db8:ce2::e
o C's local identifier of lower interface to E: 0.0.0.2.0.0.0.0 o C's local identifier of lower interface to E: 0.0.0.2.0.0.0.0
o Loopback of E used for eBGP multi-hop peering to C:
2001:db8:e::e/128
o Loopback of E used for eBGP multi-hop peering to C: 1.0.5.2/32 o C's loopback is 2001:db8:c::c/128 with SID 64
o C's loopback is 3.3.3.3/32 with SID 64
BGP Router-IDs are C, D, H and E. BGP Router-IDs are C, D, F and E.
o C's BGP Router-ID: 3.3.3.3 o C's BGP Router-ID: 192.0.2.3
o D's BGP Router-ID: 4.4.4.4 o D's BGP Router-ID: 192.0.2.4
o E's BGP Router-ID: 5.5.5.5 o E's BGP Router-ID: 192.0.2.5
o H's BGP Router-ID: 6.6.6.6 o F's BGP Router-ID: 192.0.2.6
C's BGP peering: C's BGP peering:
o Single-hop eBGP peering with neighbor 1.0.1.2 (D) o Single-hop eBGP peering with neighbor 2001:db8:cd::d (D)
o Single-hop eBGP peering with neighbor 1.0.2.2 (H) o Single-hop eBGP peering with neighbor 2001:db8:cf::f (F)
o Multi-hop eBGP peering with E on ip address 1.0.5.2 (E) o Multi-hop eBGP peering with E on ip address 2001:db8:e::e (E)
C's resolution of the multi-hop eBGP session to E: C's resolution of the multi-hop eBGP session to E:
o Static route 1.0.5.2/32 via 1.0.3.2 o Static route 2001:db8:e::e/128 via 2001:db8:ce1::e
o Static route 1.0.5.2/32 via 1.0.4.2 o Static route 2001:db8:e::e/128 via 2001:db8:ce2::e
Node C configuration is such that: Node C configuration is such that:
o A Peer Node segment (Peer-Node-SID) is allocated to each peer (D, o A Peer Node segment (Peer-Node-SID) is allocated to each peer (D,
H and E). F and E).
o An Peer Adjacency segment (Peer-Adj-SID) is defined for each o An Peer Adjacency segment (Peer-Adj-SID) is defined for each
recursing interface to a multi-hop peer (CE upper and lower recursing interface to a multi-hop peer (CE upper and lower
interfaces). interfaces).
o A Peer Set segment (Peer-Set-SID) is defined to include all peers o A Peer Set segment (Peer-Set-SID) is defined to include all peers
in AS3 (peers H and E). in AS3 (peers F and E).
Local BGP-LS Identifier in router C is set to 10000. Local BGP-LS Identifier in router C is set to 10000.
The Link NLRI Type is used in order to encode C's connectivity. The The Link NLRI Type is used in order to encode C's connectivity. The
Link NLRI uses the new Protocol-ID value (to be assigned by IANA) Link NLRI uses the Protocol-ID value (to be assigned by IANA)
Once the BGP-LS update is originated by C, it may be advertised to Once the BGP-LS update is originated by C, it may be advertised to
internal (iBGP) as well as external (eBGP) neighbors supporting the internal (iBGP) as well as external (eBGP) neighbors supporting the
BGP-LS EPE extensions defined in this document. BGP-LS EPE extensions defined in this document.
6.2. Peer Node Segment for Node D 6.2. Peer Node Segment for Node D
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, local ASN, BGP-LS o Local Node Descriptors (BGP Router-ID, local ASN, BGP-LS
Identifier): 3.3.3.3 , AS1, 10000 Identifier): 192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID, peer ASN): 4.4.4.4, AS2 o Remote Node Descriptors (BGP Router-ID, peer ASN): 192.0.2.4, AS2
o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 o Link Descriptors (BGP session IPv6 local address, BGP session IPv6
neighbor address): 1.0.1.1, 1.0.1.2 neighbor address): 2001:db8:cd::c, 2001:db8:cd::d
Attributes: Attributes:
o Peer-Node-SID: 1012 o Peer-Node-SID: 1012
o Link Attributes: see section 3.3.2 of [RFC7752] o Link Attributes: see section 3.3.2 of [RFC7752]
6.3. Peer Node Segment for Node H 6.3. Peer Node Segment for Node F
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGPLS Identifier): o Local Node Descriptors (BGP Router-ID, ASN, BGPLS Identifier):
3.3.3.3 , AS1, 10000 192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID ASN): 6.6.6.6, AS3 o Remote Node Descriptors (BGP Router-ID ASN): 192.0.2.6, AS3
o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 o Link Descriptors (BGP session IPv6 local address, BGP session IPv6
peer address): 1.0.2.1, 1.0.2.2 peer address): 2001:db8:cf::c, 2001:db8:cf::f
Attributes: Attributes:
o Peer-Node-SID: 1022 o Peer-Node-SID: 1022
o Peer-Set-SID: 1060 o Peer-Set-SID: 1060
o Link Attributes: see section 3.3.2 of [RFC7752] o Link Attributes: see section 3.3.2 of [RFC7752]
6.4. Peer Node Segment for Node E 6.4. Peer Node Segment for Node E
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier):
3.3.3.3 , AS1, 10000 192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3
o Link Descriptors (BGP session IPv4 local address, BGP session IPv4
peer address): 3.3.3.3, 1.0.5.2 o Link Descriptors (BGP session IPv6 local address, BGP session IPv6
peer address): 2001:db8:c::c, 2001:db8:e::e
Attributes: Attributes:
o Peer-Node-SID: 1052 o Peer-Node-SID: 1052
o Peer-Set-SID: 1060 o Peer-Set-SID: 1060
6.5. Peer Adjacency Segment for Node E, Link 1 6.5. Peer Adjacency Segment for Node E, Link 1
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier):
3.3.3.3 , AS1, 10000 192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3
o Link Descriptors (local interface identifier, IPv4 peer interface o Link Descriptors (local interface identifier, IPv6 peer interface
address): 0.0.0.1.0.0.0.0 , 1.0.3.2 address): 0.0.0.1.0.0.0.0 , 2001:db8:ce1::e
Attributes: Attributes:
o Peer-Adj-SID: 1032 o Peer-Adj-SID: 1032
o LinkAttributes: see section 3.3.2 of [RFC7752] o LinkAttributes: see section 3.3.2 of [RFC7752]
6.6. Peer Adjacency Segment for Node E, Link 2 6.6. Peer Adjacency Segment for Node E, Link 2
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier):
3.3.3.3 , AS1, 10000 192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3
o Link Descriptors (local interface identifier, IPv4 peer interface o Link Descriptors (local interface identifier, IPv6 peer interface
address): 0.0.0.2.0.0.0.0 , 1.0.4.2 address): 0.0.0.2.0.0.0.0 , 2001:db8:ce2::e
Attributes: Attributes:
o Peer-Adj-SID: 1042 o Peer-Adj-SID: 1042
o LinkAttributes: see section 3.3.2 of [RFC7752] o LinkAttributes: see section 3.3.2 of [RFC7752]
7. Implementation Status 7. Implementation Status
Note to RFC Editor: Please remove this section prior to publication, Note to RFC Editor: Please remove this section prior to publication,
skipping to change at page 18, line 51 skipping to change at page 18, line 51
o New BGP-LS Attributes TLVs: Peer-Node-SID, Peer-Adj-SID and Peer- o New BGP-LS Attributes TLVs: Peer-Node-SID, Peer-Adj-SID and Peer-
Set-SID. Set-SID.
11. Contributors 11. Contributors
Acee Lindem gave a substantial contribution to this document. Acee Lindem gave a substantial contribution to this document.
12. Acknowledgements 12. Acknowledgements
The authors would like to thank Jakob Heitz, Howard Yang, Hannes The authors would like to thank Jakob Heitz, Howard Yang, Hannes
Gredler, Peter Psenak, Ketan Jivan Talaulikar, and Arjun Sreekantiah Gredler, Peter Psenak, Ketan Jivan Talaulikar, Arjun Sreekantiah and
for their feedback and comments. Bruno Decraene for their feedback and comments.
13. References 13. References
13.1. Normative References 13.1. Normative References
[I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
and R. Shakir, "Segment Routing Architecture", draft-ietf-
spring-segment-routing-11 (work in progress), February
2017.
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[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,
<http://www.rfc-editor.org/info/rfc4271>. <http://www.rfc-editor.org/info/rfc4271>.
skipping to change at page 19, line 35 skipping to change at page 19, line 41
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008,
<http://www.rfc-editor.org/info/rfc5307>. <http://www.rfc-editor.org/info/rfc5307>.
[RFC6286] Chen, E. and J. Yuan, "Autonomous-System-Wide Unique BGP [RFC6286] Chen, E. and J. Yuan, "Autonomous-System-Wide Unique BGP
Identifier for BGP-4", RFC 6286, DOI 10.17487/RFC6286, Identifier for BGP-4", RFC 6286, DOI 10.17487/RFC6286,
June 2011, <http://www.rfc-editor.org/info/rfc6286>. June 2011, <http://www.rfc-editor.org/info/rfc6286>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-spring-segment-routing] [I-D.ietf-idr-bgp-ls-segment-routing-ext]
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., Previdi, S., Psenak, P., Filsfils, C., Gredler, H., Chen,
and R. Shakir, "Segment Routing Architecture", draft-ietf- M., and j. jefftant@gmail.com, "BGP Link-State extensions
spring-segment-routing-11 (work in progress), February for Segment Routing", draft-ietf-idr-bgp-ls-segment-
2017. routing-ext-01 (work in progress), February 2017.
[I-D.ietf-spring-segment-routing-central-epe] [I-D.ietf-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev, Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev,
"Segment Routing Centralized BGP Egress Peer Engineering", "Segment Routing Centralized BGP Egress Peer Engineering",
draft-ietf-spring-segment-routing-central-epe-04 (work in draft-ietf-spring-segment-routing-central-epe-05 (work in
progress), February 2017. progress), March 2017.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<http://www.rfc-editor.org/info/rfc7752>. <http://www.rfc-editor.org/info/rfc7752>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
 End of changes. 49 change blocks. 
67 lines changed or deleted 76 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/