draft-ietf-idr-ls-trill-04.txt | draft-ietf-idr-ls-trill-05.txt | |||
---|---|---|---|---|
INTERNET-DRAFT D. Eastlake | INTERNET-DRAFT D. Eastlake | |||
Intended status: Proposed Standard W. Hao | Intended status: Proposed Standard W. Hao | |||
Updates: 7752 Y. Li | Updates: 7752 Y. Li | |||
Huawei | Huawei | |||
S. Gupta | S. Gupta | |||
IP Infusion | IP Infusion | |||
M. Durrani | M. Durrani | |||
Equinix | Equinix | |||
Expires: October 14, 2018 April 15, 2018 | Expires: April 12, 2018 October 13, 2018 | |||
Distribution of TRILL Link-State using BGP | Distribution of TRILL Link-State using BGP | |||
<draft-ietf-idr-ls-trill-04.txt> | <draft-ietf-idr-ls-trill-05.txt> | |||
Abstract | Abstract | |||
This draft describes a TRILL link state and MAC address reachability | This draft describes a TRILL link state and MAC address reachability | |||
information distribution mechanism using a BGP LS extension. | information distribution mechanism using a BGP LS extension. | |||
External components such as an SDN Controller can use the information | External components such as an SDN Controller can use the information | |||
for topology visibility, troubleshooting, network automation, and the | for topology visibility, troubleshooting, network automation, and the | |||
like. This document updates RFC 7752. | like. This document updates RFC 7752. | |||
Status of This Memo | Status of This Memo | |||
skipping to change at page 2, line 25 ¶ | skipping to change at page 2, line 25 ¶ | |||
3.2 MAC Address Descriptors................................7 | 3.2 MAC Address Descriptors................................7 | |||
3.2.1 MAC-Reachability TLV.................................8 | 3.2.1 MAC-Reachability TLV.................................8 | |||
3.3 The BGP-LS Attributes..................................8 | 3.3 The BGP-LS Attributes..................................8 | |||
3.3.1 Node Attribute TLVs..................................8 | 3.3.1 Node Attribute TLVs..................................8 | |||
3.3.1.1 Node Flag Bits TLV.................................9 | 3.3.1.1 Node Flag Bits TLV.................................9 | |||
3.3.1.2 Opaque Node Attribute TLV..........................9 | 3.3.1.2 Opaque Node Attribute TLV..........................9 | |||
3.3.2. Link Attribute TLVs.................................9 | 3.3.2. Link Attribute TLVs.................................9 | |||
4. Operational Considerations.............................10 | 4. Operational Considerations.............................10 | |||
5. Security Considerations................................11 | 5. Security Considerations................................11 | |||
6. IANA Considerations....................................11 | 6. IANA Considerations....................................12 | |||
Normative References......................................12 | Normative References......................................13 | |||
Informative References....................................13 | Informative References....................................14 | |||
Acknowledgments...........................................13 | Acknowledgments...........................................14 | |||
Authors' Addresses........................................14 | Authors' Addresses........................................15 | |||
INTERNET-DRAFT BGP LS For TRILL | INTERNET-DRAFT BGP LS For TRILL | |||
1. Introduction | 1. Introduction | |||
BGP has been extended to distribute IGP link-state and traffic | BGP has been extended to distribute IGP link-state and traffic | |||
engineering information to some external components [RFC7752], such | engineering information to some external components [RFC7752], such | |||
as the PCE and ALTO servers. The information can be used by these | as the PCE and ALTO servers. The information can be used by these | |||
external components to compute a MPLS-TE path across IGP areas, | external components to compute a MPLS-TE path across IGP areas, | |||
visualize and abstract network topology, and the like. | visualize and abstract network topology, and the like. | |||
TRILL (Transparent Interconnection of Lots of Links) protocol | TRILL (Transparent Interconnection of Lots of Links) protocol | |||
[RFC6325] provides a solution for least cost transparent routing in | [RFC6325] [RFC7780] provides a solution for least cost transparent | |||
multi-hop networks with arbitrary topologies and link technologies, | routing in multi-hop networks with arbitrary topologies and link | |||
using [IS-IS] [RFC7176] link-state routing and a hop count. TRILL | technologies, using [IS-IS] [RFC7176] link-state routing and a hop | |||
switches are sometimes called RBridges (Routing Bridges). | count. TRILL switches are sometimes called RBridges (Routing | |||
Bridges). | ||||
The TRILL protocol has been deployed in many data center networks. | The TRILL protocol has been deployed in many data center networks. | |||
Data center automation is a vital step to increase the speed and | Data center automation is a vital step to increase the speed and | |||
agility of business. An SDN controller as an external component | agility of business. An SDN controller as an external component | |||
normally can be used to provide centralized control and automation | normally can be used to provide centralized control and automation | |||
for the data center network. Providing a holistic view of whole | for the data center network. Providing a holistic view of whole | |||
network topology to the SDN controller is an important part of data | network topology to the SDN controller is an important part of data | |||
center network automation and troubleshooting. | center network automation and troubleshooting. | |||
+-------------+ | +-------------+ | |||
skipping to change at page 5, line 10 ¶ | skipping to change at page 5, line 10 ¶ | |||
This document describes the detailed BGP LS extension mechanisms for | This document describes the detailed BGP LS extension mechanisms for | |||
TRILL link state and MAC address reachability information | TRILL link state and MAC address reachability information | |||
distribution. This document updated [RFC7752] by creating a new IANA | distribution. This document updated [RFC7752] by creating a new IANA | |||
registry for BGP-LS Node Descriptor Flag Bits. | registry for BGP-LS Node Descriptor Flag Bits. | |||
INTERNET-DRAFT BGP LS For TRILL | INTERNET-DRAFT BGP LS For TRILL | |||
2. Conventions used in this document | 2. Conventions used in this document | |||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
document are to be interpreted as described in [RFC2119]. | "OPTIONAL" in this document are to be interpreted as described in BCP | |||
14 [RFC2119] [RFC8174] when, and only when, they appear in all | ||||
capitals, as shown here. | ||||
BGP - Border Gateway Protocol | BGP - Border Gateway Protocol | |||
BGP-LS - BGP Link-State | BGP-LS - BGP Link-State | |||
Data label - VLAN or FGL (Fine Grained Label [RFC7172]) | Data label - VLAN or FGL (Fine Grained Label [RFC7172]) | |||
IGP - Interior Gateway Protocol | IGP - Interior Gateway Protocol | |||
IS - Intermediate System (for this document, all relevant | IS - Intermediate System (for this document, all relevant | |||
skipping to change at page 5, line 33 ¶ | skipping to change at page 5, line 35 ¶ | |||
LS - Link State | LS - Link State | |||
NLRI - Network Layer Reachability Information | NLRI - Network Layer Reachability Information | |||
SDN - Software Defined Networking | SDN - Software Defined Networking | |||
RBridge - A device implementing the TRILL protocol | RBridge - A device implementing the TRILL protocol | |||
TRILL - Transparent Interconnection of Lots of Links [RFC6325] | TRILL - Transparent Interconnection of Lots of Links [RFC6325] | |||
[RFC7176] | [RFC7176] [RFC7780] | |||
INTERNET-DRAFT BGP LS For TRILL | INTERNET-DRAFT BGP LS For TRILL | |||
3. Carrying TRILL Link-State Information in BGP | 3. Carrying TRILL Link-State Information in BGP | |||
In [RFC7752], several BGP-LS NLRI types are defined. For TRILL link- | In [RFC7752], several BGP-LS NLRI types are defined. For TRILL link- | |||
state distribution, the Node NLRI and Link NLRI are extended to carry | state distribution, the Node NLRI and Link NLRI are extended to carry | |||
layer 3 gateway role and link MTU information. TRILL specific | layer 3 gateway role and link MTU information. TRILL specific | |||
attributes are carried using opaque Node Attribute TLVs. Examples of | attributes are carried using opaque Node Attribute TLVs. Examples of | |||
such attributes are nickname, distribution tree number and | such attributes are nickname, distribution tree number and | |||
skipping to change at page 11, line 12 ¶ | skipping to change at page 12, line 5 ¶ | |||
o local node descriptor with AREA address TLV has the form | o local node descriptor with AREA address TLV has the form | |||
found in Figure 2 | found in Figure 2 | |||
INTERNET-DRAFT BGP LS For TRILL | INTERNET-DRAFT BGP LS For TRILL | |||
5. Security Considerations | 5. Security Considerations | |||
Procedures and protocol extensions defined in this document do not | Procedures and protocol extensions defined in this document do not | |||
affect the BGP security model. See [RFC6952] for details. | affect the BGP security model. See [RFC6952] for details. | |||
INTERNET-DRAFT BGP LS For TRILL | ||||
6. IANA Considerations | 6. IANA Considerations | |||
For all of the following assignments, [this document] is the | For all of the following assignments, [this document] is the | |||
reference. | reference. | |||
IANA is requested to assign one Protocol-ID TBD1 for "TRILL" from the | IANA is requested to assign one Protocol-ID TBD1 for "TRILL" from the | |||
BGP-LS registry of Protocol-IDs. | BGP-LS registry of Protocol-IDs. | |||
IANA is requested to assign one NLRI Type TBD2 for "MAC Reachability" | IANA is requested to assign one NLRI Type TBD2 for "MAC Reachability" | |||
from the BGP-LS registry of NLRI Types. | from the BGP-LS registry of NLRI Types. | |||
skipping to change at page 12, line 51 ¶ | skipping to change at page 13, line 51 ¶ | |||
End Station Address Distribution Information (ESADI) Protocol", | End Station Address Distribution Information (ESADI) Protocol", | |||
RFC 7357, September 2014, <http://www.rfc- | RFC 7357, September 2014, <http://www.rfc- | |||
editor.org/info/rfc7357>. | editor.org/info/rfc7357>. | |||
[RFC7752] - Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., | [RFC7752] - Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., | |||
and S. Ray, "North-Bound Distribution of Link-State and Traffic | and S. Ray, "North-Bound Distribution of Link-State and Traffic | |||
Engineering (TE) Information Using BGP", RFC 7752, DOI | Engineering (TE) Information Using BGP", RFC 7752, DOI | |||
10.17487/RFC7752, March 2016, <https://www.rfc- | 10.17487/RFC7752, March 2016, <https://www.rfc- | |||
editor.org/info/rfc7752>. | editor.org/info/rfc7752>. | |||
[RFC7780] - Eastlake 3rd, D., Zhang, M., Perlman, R., Banerjee, A., | ||||
Ghanwani, A., and S. Gupta, "Transparent Interconnection of | ||||
Lots of Links (TRILL): Clarifications, Corrections, and | ||||
Updates", RFC 7780, DOI 10.17487/RFC7780, February 2016, | ||||
<https://www.rfc-editor.org/info/rfc7780>. | ||||
INTERNET-DRAFT BGP LS For TRILL | ||||
[RFC7956] - Hao, W., Li, Y., Qu, A., Durrani, M., and P. Sivamurugan, | [RFC7956] - Hao, W., Li, Y., Qu, A., Durrani, M., and P. Sivamurugan, | |||
"Transparent Interconnection of Lots of Links (TRILL) | "Transparent Interconnection of Lots of Links (TRILL) | |||
Distributed Layer 3 Gateway", RFC 7956, DOI 10.17487/RFC7956, | Distributed Layer 3 Gateway", RFC 7956, DOI 10.17487/RFC7956, | |||
September 2016, <https://www.rfc-editor.org/info/rfc7956>. | September 2016, <https://www.rfc-editor.org/info/rfc7956>. | |||
INTERNET-DRAFT BGP LS For TRILL | [RFC8174] - Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May | ||||
2017, <https://www.rfc-editor.org/info/rfc8174>. | ||||
Informative References | Informative References | |||
[ISO10589] - SO, "Intermediate System to Intermediate System intra- | [ISO10589] - SO, "Intermediate System to Intermediate System intra- | |||
domain routeing information exchange protocol for use in | domain routeing information exchange protocol for use in | |||
conjunction with the protocol for providing the connectionless- | conjunction with the protocol for providing the connectionless- | |||
mode network service (ISO 8473)", International Standard | mode network service (ISO 8473)", International Standard | |||
10589:2002, Second Edition, 2002. | 10589:2002, Second Edition, 2002. | |||
[RFC2328] - Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI | [RFC2328] - Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI | |||
skipping to change at page 14, line 12 ¶ | skipping to change at page 15, line 12 ¶ | |||
Dong, Mingui Zhang, Qin Wu, Shunwan Zhuang, Zitao Wang, Lili Wang for | Dong, Mingui Zhang, Qin Wu, Shunwan Zhuang, Zitao Wang, Lili Wang for | |||
their valuable inputs. | their valuable inputs. | |||
INTERNET-DRAFT BGP LS For TRILL | INTERNET-DRAFT BGP LS For TRILL | |||
Authors' Addresses | Authors' Addresses | |||
Weiguo Hao | Weiguo Hao | |||
Huawei Technologies | Huawei Technologies | |||
101 Software Avenue, | 101 Software Avenue, | |||
Nanjing 210012 | Nanjing 210012, China | |||
China | ||||
Phone: +86-25-56623144 | Phone: +86-25-56623144 | |||
Email: haoweiguo@huawei.com | Email: haoweiguo@huawei.com | |||
Donald E. Eastlake | Donald E. Eastlake | |||
Huawei Technologies | Huawei Technologies | |||
155 Beaver Street | 1424 Pro Shop Court | |||
Milford, MA 01757 USA | Davenport, FL 33896 USA | |||
Phone: +1-508-333-2270 | Phone: +1-508-333-2270 | |||
Email: d3e3e3@gmail.com | Email: d3e3e3@gmail.com | |||
Yizhou Li | Yizhou Li | |||
Huawei Technologies | Huawei Technologies | |||
101 Software Avenue, | 101 Software Avenue, | |||
Nanjing 210012, China | Nanjing 210012, China | |||
Phone: +86-25-56625375 | Phone: +86-25-56625375 | |||
End of changes. 13 change blocks. | ||||
19 lines changed or deleted | 33 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/ |