One document matched: draft-ietf-idr-ls-trill-01.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC4271 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4271.xml">
<!ENTITY RFC6325 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6325.xml">
<!ENTITY RFC6952 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6952.xml">
<!ENTITY RFC7153 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7153.xml">
<!ENTITY RFC7172 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7172.xml">
<!ENTITY RFC7176 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7176.xml">
<!ENTITY RFC7357 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7357.xml">
<!ENTITY RFC7606 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7606.xml">
<!ENTITY RFC7752 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7752.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<?rfc iprnotified="no" ?>
<?rfc strict="no" ?>
<rfc category="std" docName="draft-ietf-idr-ls-trill-01.txt" ipr="trust200902">
<front>
<title abbrev="BGP LS for TRILL">Distribution of TRILL Link-State using BGP</title>
<author fullname=" Weiquo Hao " initials="W," surname="Hao">
<organization>Huawei Technologies</organization>
<address>
<postal>
<street>101 Software Avenue,</street>
<city>Nanjing</city>
<region></region>
<code>210012</code>
<country>China</country>
</postal>
<phone>+86-25-56623144</phone>
<email>haoweiguo@huawei.com</email>
</address>
</author>
<author fullname="Donald E. Eastlake " initials="D." surname="Eastlake">
<organization>Huawei Technologies</organization>
<address>
<postal>
<street>155 Beaver Street </street>
<city>Milford </city>
<region>MA</region>
<code>01757</code>
<country>USA</country>
</postal>
<phone>+1-508-333-2270 </phone>
<email>d3e3e3@gmail.com </email>
</address>
</author>
<author fullname="Susan Hares" initials="S." surname="Hares">
<organization>Huawei Technologies</organization>
<address>
<postal>
<street>7453 Hickory</street>
<city>Saline </city>
<region>MI</region>
<code>48176</code>
<country>USA</country>
</postal>
<phone>+1-734-604-0332 </phone>
<email>shares@ndzh.com</email>
</address>
</author>
<author fullname="Sujay Gupta" initials="B" surname="Pithawala">
<organization>IP Infusion</organization>
<address>
<postal>
<street></street>
<city></city>
<region></region>
<code> </code>
<country></country>
</postal>
<email>sujay.gupta@ipinfusion.com</email>
</address>
</author>
<author fullname=" Muhammad Durrani" initials="M" surname="Durrani">
<organization>Cisco Systems</organization>
<address>
<postal>
<street></street>
<city></city>
<region></region>
<code></code>
<country></country>
</postal>
<phone>+1-408-527-6921</phone>
<email>mdurrani@cisco.com </email>
</address>
</author>
<author fullname="Yizhou Li" initials="Y" surname="Li">
<organization>Huawei Technologies</organization>
<address>
<postal>
<street> 101 Software Avenue, </street>
<city>Nanjing</city>
<region></region>
<code>210012</code>
<country>China</country>
</postal>
<email>liyizhou@huawei.com</email>
</address>
</author>
<date year="2016" />
<area>Routing Area</area>
<workgroup>IDR Working Group</workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<keyword>BGP LS</keyword>
<keyword>TRILL</keyword>
<abstract>
<t> This draft describes a TRILL link state and MAC address reachability
information distribution mechanism using a BGP LS extension.
External components such as an SDN Controller can use the
information for topology visibility, troubleshooting, network
automation, etc.
</t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<t>BGP has been extended to distribute IGP link-state and traffic
engineering information to some external components <xref target="RFC7752"></xref>
such as the PCE and ALTO servers. The information
can be used by these external components to compute a MPLS-TE path
across IGP areas, visualize and abstract network topology, and the
like.
</t>
<t>TRILL (Transparent Interconnection of Lots of Links) protocol
<xref target="RFC6325"></xref> provides a solution for least cost transparent routing in
multi-hop networks with arbitrary topologies and link technologies,
using [IS-IS] <xref target="RFC7176"></xref> link-state routing and a hop count. TRILL
switches are sometimes called RBridges (Routing Bridges).
</t>
<t>
The TRILL protocol has been deployed in many data center networks.
Data center automation is a vital step to increase the speed and
agility of business. An SDN controller as an external component
normally can be used to provide centralized control and automation
for the data center network. Making a holistic view of whole network
topology available to the SDN controller is an important part for
data center network automation and troubleshooting.
</t>
<t>
<figure>
<artwork>
+-------------+
| SDN |
--------| Controller |--------
| +-------------+ |
| |
+ + + +
+ +-----------+ +
| |
+--------+ |IP Network | +--------+
| | +----+ +----+ | |
+---+ +---+ | | | | | | | | +---+ +---+
|ES1|-|RB1|-| Area 1 |-|BRB1| |BRB2|-| Area 2 |-|RB2|-|ES2|
+---+ +---+ | | +----+ +----+ | | +---+ +---+
| | | | | |
+--------+ +-----------+ +--------+
|<----TRILL ------>|<IP tunnel>|<-----TRILL ----->|
Figure 1: TRILL interconnection
</artwork>
</figure>
</t>
<t>
In Data Center interconnection scenario illustrated in figure 1, a
single SDN Controller or network management system (NMS) can be used
for end-to-end network management. End-to-end topology visibility on
the SDN controller or NMS is very useful for whole network
automation and troubleshooting. BGP LS can be used by the external
SDN controller to collect multiple TRILL domain's link-state.
</t>
<t>
If ESADI (End Station Address Distribution Information) protocol
<xref target="RFC7357"></xref> is used for control plane MAC learning in each data center,
BGP LS also can be used for MAC address reachability information
synchronization across multiple TRILL domains. End-to-end unicast
forwarding paths can be calculated based on the synchronized
information.
</t>
<t>This document describes the detailed BGP LS extension mechanisms for
TRILL link state and MAC address reachability information
distribution.
</t>
</section>
<section title="Conventions used in this document">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <xref target="RFC2119"></xref>
</t>
<t>BGP - Border Gateway Protocol
</t>
<t>BGP-LS - BGP Link-State
</t>
<t>Data label - VLAN or FGL (Fine Grained Label) <xref target="RFC7172"></xref>
</t>
<t>IS - Intermediate System (for this document, all relevant
intermediate systems are RBridges). </t>
<t>NLRI - Network Layer Reachability Information</t>
<t>SDN - Software Defined Networking </t>
<t>RBridge - A device implementing the TRILL protocol </t>
<t>TRILL - Transparent Interconnection of Lots of Links </t>
</section>
<section title="Carrying Trill Link-State Information in BGP">
<t>In <xref target="RFC7752"></xref>, four NLRI types are defined
as follows: Node NLRI, Link NLRI, IPv4 Topology Prefix NLRI and IPv6
Topology Prefix NLRI. For TRILL link-state distribution, the Node
NLRI and Link NLRI are extended to carry layer 3 gateway role and
link MTU information. TRILL specific attributes are carried using
opaque Node Attribute TLVs, such as nickname, distribution tree
number and identifiers, interested VLANs/Fine Grained Label, and
multicast group address, and etc.
</t>
<t> To differentiate TRILL protocol from layer 3 IGP protocol, a new
TRILL Protocol-ID is defined.
</t>
<t>
<figure>
<artwork>
+-------------+----------------------------------+
| Protocol-ID | NLRI information source protocol |
+-------------+----------------------------------+
| 1 | IS-IS Level 1 |
| 2 | IS-IS Level 2 |
| 3 | OSPFv2 |
| 4 | Direct |
| 5 | Static configuration |
| 6 | OSPFv3 |
| TBD | TRILL |
+-------------+----------------------------------+
Table 1: Protocol Identifiers
</artwork>
</figure>
</t>
<t>
ESADI (End Station Address Distribution Information) protocol
[RFC7357] is a per data label control plane MAC learning solution.
MAC address reachability information is carried in ESADI packets.
Compared with data plane MAC learning solution, ESADI protocol has
security and fast update advantage that are pointed out in [RFC7357].
</t>
<t>For an RBridge that is announcing participation in ESADI, the
RBridge can distribute MAC address reachability information to
external components using BGP. A new NLRI type of ''MAC Reachability
NLRI'' is requested for the MAC address reachability distribution.
</t>
<t>
<figure>
<artwork>
+------+---------------------------+
| Type | NLRI Type |
+------+---------------------------+
| 1 | Node NLRI |
| 2 | Link NLRI |
| 3 | IPv4 Topology Prefix NLRI |
| 4 | IPv6 Topology Prefix NLRI |
| TBD | MAC Reachability NLRI |
+------+---------------------------+
Table 2: NLRI Types
</artwork>
</figure>
</t>
<t>
The MAC Reachability NLRI uses the format as shown in the following
figure.
</t>
<t>
<figure>
<artwork>
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
+-+-+-+-+-+-+-+-+
| Protocol-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier |
| (64 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// Local Node Descriptor (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// MAC Address Descriptors (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: The MAC Reachability NLRI format
</artwork>
</figure>
</t>
<section title="Node Descriptors">
<t>The Node Descriptor Sub-TLV types include Autonomous System and BGP-
LS Identifier, iS-IS Area-ID and IGP Router-ID. TRILL uses a fixed
zero Area Address as specified in [RFC6325], Section 4.2.3. This is
encoded in a 4-byte Area Address TLV (TLV #1) as follows:
</t>
<t>
<figure>
<artwork>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x01, Area Address Type | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x02, Length of Value | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x01, Length of Address | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00, zero Area Address | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Area Address TLV
</artwork>
</figure>
</t>
<section title="IGP Router-ID">
<t>
Similar to layer 3 IS-IS, TRILL protocol uses 7-octet "IS-IS ID" as
the identity of an RBridge or a pseudonode, IGP Router ID sub-TLV in
Node Descriptor TLVs contains the 7-octet "IS-IS ID". In TRILL
network, each RBridge has a unique 48-bit (6-octet) IS-IS System ID.
This ID may be derived from any of the RBridge's unique MAC
addresses or configured. A pseudonode is assigned a 7-octet ID by
the DRB (Designated RBridge) that created it, the DRB is similar to
the "Designated Intermediate System" (DIS) corresponding to a LAN.
</t>
</section>
</section>
<section title="MAC Address Descriptors">
<t> The ''MAC Address Descriptor'' field is a set of Type/Length/Value
(TLV) triplets. ''MAC Address Descriptor'' TLVs uniquely identify an
MAC address reachable by a Node. The following attributes TLVs are
defined:
</t>
<t>
<figure>
<artwork>
+--------------+-----------------------+----------+-----------------+
| TLV Code | Description | Length | Value defined |
| Point | | | in: |
+--------------+-----------------------+----------+-----------------+
| 1 | MAC-Reachability | variable | section 3.2.1 |
+--------------+-----------------------+----------+-----------------+
Table 3: MAC Address Descriptor TLVs
</artwork>
</figure>
</t>
<section title="MAC-Reachability TLV">
<t>
<figure>
<artwork>
+-+-+-+-+-+-+-+-+
| Type= MAC-RI | (1 byte)
+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...+-+-+-+-+-+-+-+
|V|F| RESV | Data Label | (4 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC (1) (6 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC (N) (6 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: MAC-Reachability TLV format
</artwork>
</figure>
</t>
<t>Length is 4 plus a multiple of 6.
</t>
<t> The bits of 'V' and 'F' are used to identify Data Label type and are
defined as follows:
</t>
<t>
<figure>
<artwork>
+----------+-------------------------+
| Bit | Description |
+----------+-------------------------+
| 'V' | VLAN |
| 'F' | Fine Grained Label |
+----------+-------------------------+
Table 4: Data Label Type Bits Definitions
</artwork>
</figure>
</t>
<t>Notes: If BGP LS is used for NVO3 network MAC address distribution
between external SDN Controller and NVE, Data Label can be used to
represent 24 bits VN ID.
</t>
</section>
</section>
<section title="BGP-LS attribute">
<section title="Node Attribute TLVs">
<section title="Node Flag Bits TLV">
<t>A new Node Flag bit is added as follows:
<figure>
<artwork>
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|O|T|E|B|G| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Node Flag Bits TLV format
</artwork>
</figure>
</t>
<t> The new bit and remaining reserved bits are defined as follows:
<figure>
<artwork>
+----------+----------------------------+-----------+
| Bit | Description | Reference |
+----------+----------------------------+-----------+
| 'G' | Layer 3 Gateway Bit | [RFC7176] |
| Reserved | Reserved for future use | |
+----------+----------------------------+-----------+
Table 5: Node Flag Bits Definitions
</artwork>
</figure>
</t>
</section>
<section title="Opaque Node Attribute TLV">
<t>
The Opaque Node Attribute TLV is used as the envelope to
transparently carry TRILL specific information. In <xref target="RFC7176"></xref>,
there are the following Sub-TLVs in the Router Capability and MT-
Capability TLVs and the Group Address (GADDR) TLV that need to be
carried. Future possible TRILL TLVs/Sub-TLVs extension also can be
carried using the Opaque Node Attribute TLV.
</t>
<t>
<figure>
<artwork>
Descriptions IS-IS TLV/Sub-TLV
------------------------------------
TRILL-VER 22/13
NICKNAME 22/6
TREES 22/7
TREE-RT-IDs 22/8
TREE-USE-IDs 22/9
INT-VLAN 22/10
VLAN-GROUP 22/14
INT-LABEL 22/15
RBCHANNELS 22/16
AFFINITY 22/17
LABEL-GROUP 22/18
GMAC-ADDR 142/1
GIP-ADDR 142/2
GIPV6-ADDR 142/3
GLMAC-ADDR 142/4
GLIP-ADDR 142/5
GLIPV6-ADDR 142/6
Table 6: TRILL TLVs/Sub-TLVs
</artwork>
</figure>
</t>
</section>
</section>
<section title="Link Attribute TLVs">
<t>
Link attribute TLVs are TLVs that may be encoded in the BGP-LS
attribute with a link NLRI. Besides the TLVs that has been defined
in <xref target="RFC7752"></xref> section 3.3.2 table 9, the
following 'Link Attribute' TLV is provided for TRILL.
</t>
<t>
<figure>
<artwork>
+-----------+----------------+--------------+------------------+
| TLV Code | Description | IS-IS TLV | Defined in: |
| Point | | /Sub-TLV | |
+-----------+----------------+--------------+------------------+
| TBD | Link MTU | 22/28 | [RFC7176]/2.4 |
+-----------+----------------+--------------+------------------+
Table 7: Link Attribute TLVs
</artwork>
</figure>
</t>
</section>
</section>
</section>
<section title="Operational Considerations">
<t>This document does not require any MIB or Yang model to configure
operational parameters.
</t>
<t>
An implementation of this specification[idr-ls-trill], MUST do the
malformed attribute checks below, and if it detects a malformed
attribute, it should use the 'Attribute Discard' action per
<xref target="RFC7606"></xref> section 2.
</t>
<t>An implementation MUST perform the following expanded [BGP-LS]
syntactic check for determining if the message is malformed:
<list style="symbols">
<t>Does the sum of all TLVs found in the BGP LS attribute
correspond to the BGP LS path attribute length ?
</t>
<t> Does the sum of all TLVs found in the BGP MP_REACH_NLRI
attribute correspond to the BGP MP_REACH_NLRI length ?
</t>
<t> Does the sum of all TLVs found in the BGP MP_UNREACH_NLRI
attribute correspond to the BGP MP_UNREACH_NLRI length ?
</t>
<t>Does the sum of all TLVs found in a Node-, Link, prefix (IPv4
or IPv6) NLRI attribute correspond to the Node-, Link- or Prefix
Descriptors 'Total NLRI Length' field ?
</t>
<t>Does any fixed length TLV correspond to the TLV Length field
in this document ?
</t>
<t>Does the sum of MAC reachability TLVs equal the length of the
field?
</t>
</list>
</t>
<t>In addition, the following checks need to be made for the fields
specific to the BGP LS for TRILL:
<list style="symbols">
<t>PROTOCOL ID is TRILL, </t>
<t>NLRI types are valid per table 2, </t>
<t> MAC Reachability NLRI has correct format including:
<list style="symbols">
<t>Identifier (64 bits),
</t>
<t>local node descriptor with AREA address TLV has the
form found in figure 2,
</t>
</list>
</t>
<t>opaque TLV support the range of ISIS-TLV/SUB-TLV shown in
table 3, and link TLVs support the range in figure 8.</t>
</list>
</t>
</section>
<section title="Security Considerations">
<t>
Procedures and protocol extensions defined in this document do not
affect the BGP security model. See <xref target="RFC6952"></xref> for details.
</t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>This section complies with <xref target="RFC7153"></xref>.
For all of the following assignments, [this document] is the
reference.
</t>
<t>
IANA is requested to requested to assign one Protocol-ID for "TRILL" from the
BGP-LS registry of Protocol-IDs
</t>
<t> IANA is requested to assign one NLRI Type for "MAC Reachability"
from the BGP-LS registry of NLRI Types.
</t>
<t>IANA is requested to assign one Node Flag bit for "Layer 3 Gateway"
from the BGP-LS registry of BGP-LS Attribute TLVs.
</t>
<t>IANA is requested to assign one new TLV type for "Link MTU" from the
BGP-LS registry of BGP-LS Attribute TLVs.
</t>
</section>
<section title="Acknowledgements">
<t> Authors like to thank Andrew Qu, Jie Dong, Mingui Zhang, Qin Wu,
Shunwan Zhuang, Zitao Wang, Lili Wang for their valuable inputs.
</t>
</section>
</middle>
<back>
<references title="Normative References">
&RFC2119;
&RFC4271;
&RFC6325;
&RFC6952;
&RFC7153;
&RFC7172;
&RFC7176;
&RFC7357;
&RFC7606;
&RFC7752;
</references>
</back>
</rfc>| PAFTECH AB 2003-2026 | 2026-04-23 16:31:32 |