draft-ietf-idr-bgpls-segment-routing-epe-06.txt   draft-ietf-idr-bgpls-segment-routing-epe-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 Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: May 17, 2017 S. Ray Expires: August 12, 2017 S. Ray
Individual Contributor Individual Contributor
K. Patel K. Patel
Cisco Systems, Inc. Individual
J. Dong J. Dong
M. Chen M. Chen
Huawei Technologies Huawei Technologies
November 13, 2016 February 8, 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-06 draft-ietf-idr-bgpls-segment-routing-epe-07
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 May 17, 2017. This Internet-Draft will expire on August 12, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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
skipping to change at page 2, line 49 skipping to change at page 2, line 49
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 H . . . . . . . . . . . . . . 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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 16
8. Manageability Considerations . . . . . . . . . . . . . . . . 16 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 8.1. New BGP-LS Protocol-ID . . . . . . . . . . . . . . . . . 17
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17 8.2. Node Descriptors and Link Attribute TLVs . . . . . . . . 17
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 9. Manageability Considerations . . . . . . . . . . . . . . . . 18
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18
12.1. Normative References . . . . . . . . . . . . . . . . . . 17 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18
12.2. Informative References . . . . . . . . . . . . . . . . . 17 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
13.1. Normative References . . . . . . . . . . . . . . . . . . 19
13.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
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 5, line 10 skipping to change at page 5, line 10
While an egress point topology usually refers to eBGP sessions While an egress point topology usually refers to eBGP sessions
between external peers, there's nothing in the extensions defined in between external peers, there's nothing in the extensions defined in
this document that would prevent the use of these extensions in the this document that would prevent the use of these extensions in the
context of iBGP sessions. context of iBGP sessions.
4. Link NLRI for BGP-EPE Connectivity Description 4. Link NLRI for BGP-EPE Connectivity Description
This section describes the NLRI used for describing the connectivity This section describes the NLRI used for describing the connectivity
of the BGP Egress router. The connectivity is based on links and of the BGP Egress router. The connectivity is based on links and
remote peers/ASs and therefore the existing Link-Type NLRI (defined remote peers/ASs and therefore the existing Link-Type NLRI (defined
in [RFC7752]) is used. A new Protocol ID is used (codepoint to be in [RFC7752]) is used. A new Protocol ID is used: BGP (codepoint to
assigned by IANA, suggested value 7). be assigned by IANA).
The use of a new Protocol-ID allows separation and differentiation The use of a new Protocol-ID allows separation and differentiation
between the NLRIs carrying BGP-EPE descriptors from the NLRIs between the NLRIs carrying BGP-EPE descriptors from the NLRIs
carrying IGP link-state information as defined in [RFC7752]. The carrying IGP link-state information as defined in [RFC7752]. The
Link NLRI Type uses descriptors and attributes already defined in Link NLRI Type uses descriptors and attributes already defined in
[RFC7752] in addition to new TLVs defined in the following sections [RFC7752] in addition to new TLVs defined in the following sections
of this document. of this document.
The extensions defined in this document apply to both internal and The extensions defined in this document apply to both internal and
external BGP-LS EPE advertisements. external BGP-LS EPE advertisements.
skipping to change at page 5, line 48 skipping to change at page 5, line 48
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Node Descriptors and Link Descriptors are defined in [RFC7752]. Node Descriptors and Link Descriptors are defined in [RFC7752].
4.1. BGP Router ID and Member ASN 4.1. BGP Router ID and Member ASN
Two new Node Descriptors Sub-TLVs are defined in this document: Two new Node Descriptors Sub-TLVs are defined in this document:
o BGP Router Identifier (BGP Router-ID): o BGP Router Identifier (BGP Router-ID):
Type: TBA (suggested value 516). Type: TBD2 (to be assigned by IANA from the registry "BGP-LS
Node Descriptor, Link Descriptor, Prefix Descriptor, and
Attribute TLVs").
Length: 4 octets Length: 4 octets
Value: 4 octet unsigned integer representing the BGP Identifier Value: 4 octet unsigned integer representing the BGP Identifier
as defined in [RFC4271] and [RFC6286]. as defined in [RFC4271] and [RFC6286].
o Confederation Member ASN (Member-ASN) o Confederation Member ASN (Member-ASN)
Type: TBA (suggested value 517). Type: TBD3 (to be assigned by IANA from the registry "BGP-LS
Node Descriptor, Link Descriptor, Prefix Descriptor, and
Attribute TLVs").
Length: 4 octets Length: 4 octets
Value: 4 octet unsigned integer representing the Member ASN Value: 4 octet unsigned integer representing the Member ASN
inside the Confederation.[RFC5065]. inside the Confederation.[RFC5065].
4.2. BGP-EPE Node Descriptors 4.2. BGP-EPE Node Descriptors
The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI
as Local Node Descriptors: as Local Node Descriptors:
skipping to change at page 7, line 19 skipping to change at page 7, line 22
4.3. Link Attributes 4.3. Link Attributes
The following BGP-LS Link attributes TLVs are used with the Link The following BGP-LS Link attributes TLVs are used with the Link
NLRI: NLRI:
+----------+---------------------------+----------+ +----------+---------------------------+----------+
| TLV Code | Description | Length | | TLV Code | Description | Length |
| Point | | | | Point | | |
+----------+---------------------------+----------+ +----------+---------------------------+----------+
| 1101 | Peer Node Segment | variable | | TBD4 | Peer Node Segment | variable |
| | Identifier (Peer-Node-SID)| | | | Identifier (Peer-Node-SID)| |
| 1102 | Peer Adjacency Segment | variable | | TBD5 | Peer Adjacency Segment | variable |
| | Identifier (Peer-Adj-SID) | | | | Identifier (Peer-Adj-SID) | |
| 1103 | Peer Set Segment | variable | | TBD6 | Peer Set Segment | variable |
| | Identifier (Peer-Set-SID) | | | | Identifier (Peer-Set-SID) | |
+----------+---------------------------+----------+ +----------+---------------------------+----------+
Figure 1: BGP-LS TLV code points for BGP-EPE Figure 1: BGP-LS TLV code points for BGP-EPE
Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID have all the same format Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID have all the same format
defined here below: defined here below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 7, line 46 skipping to change at page 7, line 49
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Weight | Reserved | | Flags | Weight | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label/Index (variable) | | SID/Label/Index (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Figure 2 Figure 2
o Type: To be assigned by IANA. The suggested values are defined in o Type: TBD4 or TBD5 or TBD6, to be assigned by IANA.
Figure 1.
o Length: variable. o Length: variable.
o Flags: following flags have been defined: o Flags: following flags have been defined:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|V|L| | |V|L| |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
skipping to change at page 16, line 5 skipping to change at page 16, line 5
o Link Descriptors (local interface identifier, IPv4 peer interface o Link Descriptors (local interface identifier, IPv4 peer interface
address): 0.0.0.2.0.0.0.0 , 1.0.4.2 address): 0.0.0.2.0.0.0.0 , 1.0.4.2
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. IANA Considerations 7. Implementation Status
Note to RFC Editor: Please remove this section prior to publication,
as well as the reference to RFC 7942.
This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in [RFC7942].
The description of implementations in this section is intended to
assist the IETF in its decision processes in progressing drafts to
RFCs. Please note that the listing of any individual implementation
here does not imply endorsement by the IETF. Furthermore, no effort
has been spent to verify the information presented here that was
supplied by IETF contributors. This is not intended as, and must not
be construed to be, a catalog of available implementations or their
features. Readers are advised to note that other implementations may
exist.
According to [RFC7942], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as
they see fit".
Several early implementations exist and will be reported in detail in
a forthcoming version of this document. For purposes of early
interoperability testing, when no FCFS code point was available,
implementations have made use of the following values:
+---------------------------------------+
| Codepoint | Description |
+---------------------------------------+
| 7 | Protocol-ID BGP |
| 516 | BGP Router ID |
| 517 | BGP Confederation Member |
| 1101 | Peer-Node-SID |
| 1102 | Peer-Adj-SID |
| 1103 | Peer-Set-SID |
+------------+--------------------------+
It will ease implementation interoperability and deployment if the
value could be preserved. However, when IANA-assigned values are
available, implementations will be updated to use them.
8. IANA Considerations
This document defines: This document defines:
Two new Node Descriptors Sub-TLVs: BGP-Router-ID and BGP A new Protocol-ID: BGP. The codepoint is from the "BGP-LS
Confederation Member. Protocol-IDs" registry.
A new Protocol-ID: BGP-EPE. Two new TLVs: BGP-Router-ID and BGP Confederation Member. The
codepoints are in the "BGP-LS Node Descriptor, Link Descriptor,
Prefix Descriptor, and Attribute TLVs" registry.
Three new BGP-LS Attribute Sub-TLVs: Peer-Node-SID, Peer-Adj-SID Three new BGP-LS Attribute TLVs: Peer-Node-SID, Peer-Adj-SID and
and Peer-Set-SID. Peer-Set-SID. The codepoints are in the "BGP-LS Node Descriptor,
Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry.
The codepoints are to be assigned by IANA. The following are the 8.1. New BGP-LS Protocol-ID
suggested values:
+---------------------+--------------------------+-------------+ This document defines a new value in the registry "BGP-LS Protocol-
| Suggested Codepoint | Description | Defined in: | IDs":
+---------------------+--------------------------+-------------+
| 7 | Protocol-ID | Section 4 |
| 516 | BGP Router ID | Section 4.1 |
| 517 | BGP Confederation Member | Section 4.1 |
| 1101 | Peer-Node-SID | Section 4.3 |
| 1102 | Peer-Adj-SID | Section 4.3 |
| 1103 | Peer-Set-SID | Section 4.3 |
+---------------------+--------------------------+-------------+
Table 1: Summary Table of BGP-LS Codepoints for BGP-EPE +---------------------------------------+
| Codepoint | Description |
+---------------------------------------+
| TBD1 | BGP |
+---------------------------------------+
8. Manageability Considerations 8.2. Node Descriptors and Link Attribute TLVs
This document defines 5 new TLVs in the registry "BGP-LS Node
Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs":
o Two new node descriptor TLVs
o Three new link attribute TLVs
All the new 5 codepoints are in the same registry: "BGP-LS Node
Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs".
However, the registry is organized in ranges (node descriptors, link
descriptors, node attributes, link attributes). The allocation
should be done accordingly.
The following new Node Descriptors TLVs are defined:
+---------------------------------------+
| Codepoint | Description |
+---------------------------------------+
| TBD2 | BGP Router ID |
| TBD3 | BGP Confederation Member |
+------------+--------------------------+
The following new Link Attribute TLVs are defined:
+---------------------------------------+
| Codepoint | Description |
+---------------------------------------+
| TBD4 | Peer-Node-SID |
| TBD5 | Peer-Adj-SID |
| TBD6 | Peer-Set-SID |
+------------+--------------------------+
9. Manageability Considerations
TBD TBD
9. Security Considerations 10. Security Considerations
[RFC7752] defines BGP-LS NLRIs to which the extensions defined in [RFC7752] defines BGP-LS NLRIs to which the extensions defined in
this document apply. this document apply.
The Security Section of [RFC7752] also applies to: The Security Section of [RFC7752] also applies to:
o New Node Descriptors Sub-TLVs: BGP-Router-ID and BGP- o New Node Descriptors Sub-TLVs: BGP-Router-ID and BGP-
Confederation-Member; Confederation-Member;
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.
10. Contributors 11. Contributors
Acee Lindem gave a substantial contribution to this document. Acee Lindem gave a substantial contribution to this document.
11. 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, and Arjun Sreekantiah
for their feedback and comments. for their feedback and comments.
12. References 13. References
12.1. Normative References 13.1. Normative References
[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 17, line 43 skipping to change at page 19, line 33
[RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions
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>.
12.2. Informative References 13.2. Informative References
[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-09 (work in progress), July 2016. spring-segment-routing-10 (work in progress), November
2016.
[I-D.ietf-spring-segment-routing-central-epe] [I-D.ietf-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Aries, E., Ginsburg, D., and D. Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev,
Afanasiev, "Segment Routing Centralized BGP Peer "Segment Routing Centralized BGP Peer Engineering", draft-
Engineering", draft-ietf-spring-segment-routing-central- ietf-spring-segment-routing-central-epe-03 (work in
epe-02 (work in progress), September 2016. progress), November 2016.
[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
Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016,
<http://www.rfc-editor.org/info/rfc7942>.
Authors' Addresses Authors' Addresses
Stefano Previdi (editor) Stefano Previdi (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Via Del Serafico, 200 Via Del Serafico, 200
Rome 00142 Rome 00142
Italy Italy
Email: sprevidi@cisco.com Email: sprevidi@cisco.com
skipping to change at page 18, line 40 skipping to change at page 20, line 33
BE BE
Email: cfilsfil@cisco.com Email: cfilsfil@cisco.com
Saikat Ray Saikat Ray
Individual Contributor Individual Contributor
Email: raysaikat@gmail.com Email: raysaikat@gmail.com
Keyur Patel Keyur Patel
Cisco Systems, Inc. Individual
170, West Tasman Drive
San Jose, CA 95134
US
Email: keyupate@cisco.com
Jie Dong Jie Dong
Huawei Technologies Huawei Technologies
Huawei Campus, No. 156 Beiqing Rd. Huawei Campus, No. 156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: jie.dong@huawei.com Email: jie.dong@huawei.com
Mach (Guoyi) Chen Mach (Guoyi) Chen
Huawei Technologies Huawei Technologies
Huawei Campus, No. 156 Beiqing Rd. Huawei Campus, No. 156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: mach.chen@huawei.com Email: mach.chen@huawei.com
 End of changes. 34 change blocks. 
61 lines changed or deleted 145 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/