Debian Codegraph @

rfc6439.html

raw
1 <pre>Internet Engineering Task Force (IETF) R. Perlman
2 Request for Comments: 6439 Intel Labs
3 Updates: <a href="./rfc6325">6325</a> D. Eastlake 3rd
4 Category: Standards Track Y. Li
5 ISSN: 2070-1721 Huawei Technologies
6 A. Banerjee
7 Cisco Systems
8 F. Hu
9 ZTE Corporation
10 November 2011
11
12
13 <span class="h1">Routing Bridges (RBridges): Appointed Forwarders</span>
14
15 Abstract
16
17 The IETF TRILL (TRansparent Interconnection of Lots of Links)
18 protocol provides least cost pair-wise data forwarding without
19 configuration in multi-hop networks with arbitrary topology, safe
20 forwarding even during periods of temporary loops, and support for
21 multipathing of both unicast and multicast traffic. TRILL
22 accomplishes this by using IS-IS (Intermediate System to Intermediate
23 System) link state routing and by encapsulating traffic using a
24 header that includes a hop count. Devices that implement TRILL are
25 called "RBridges" (Routing Bridges).
26
27 TRILL supports multi-access LAN (Local Area Network) links that can
28 have multiple end stations and RBridges attached. Where multiple
29 RBridges are attached to a link, native traffic to and from end
30 stations on that link is handled by a subset of those RBridges called
31 "Appointed Forwarders", with the intent that native traffic in each
32 VLAN (Virtual LAN) be handled by at most one RBridge. The purpose of
33 this document is to improve the documentation of the Appointed
34 Forwarder mechanism; thus, it updates <a href="./rfc6325">RFC 6325</a>.
35
36 Status of This Memo
37
38 This is an Internet Standards Track document.
39
40 This document is a product of the Internet Engineering Task Force
41 (IETF). It represents the consensus of the IETF community. It has
42 received public review and has been approved for publication by the
43 Internet Engineering Steering Group (IESG). Further information on
44 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
45
46 Information about the current status of this document, any errata,
47 and how to provide feedback on it may be obtained at
48 <a href="http://www.rfc-editor.org/info/rfc6439">http://www.rfc-editor.org/info/rfc6439</a>.
49
50
51
52 <span class="grey">Perlman, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2011 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
75 <a href="#section-1.1">1.1</a>. Terminology and Acronyms ...................................<a href="#page-3">3</a>
76 <a href="#section-2">2</a>. Appointed Forwarders and Their Appointment ......................<a href="#page-4">4</a>
77 <a href="#section-2.1">2.1</a>. Appointment Effects of DRB Elections .......................<a href="#page-5">5</a>
78 <a href="#section-2.2">2.2</a>. Appointment and Removal by the DRB .........................<a href="#page-5">5</a>
79 <a href="#section-2.2.1">2.2.1</a>. Processing Forwarder Appointments ...................<a href="#page-6">6</a>
80 <a href="#section-2.2.2">2.2.2</a>. Frequency of Appointments ...........................<a href="#page-7">7</a>
81 <a href="#section-2.2.3">2.2.3</a>. Appointed Forwarders Limit ..........................<a href="#page-8">8</a>
82 <a href="#section-2.3">2.3</a>. Local Configuration Action Appointment Effects .............<a href="#page-8">8</a>
83 <a href="#section-2.4">2.4</a>. VLAN Mapping within a Link .................................<a href="#page-9">9</a>
84 <a href="#section-3">3</a>. The Inhibition Mechanism ........................................<a href="#page-9">9</a>
85 <a href="#section-4">4</a>. Inhibited Appointed Forwarder Behavior .........................<a href="#page-11">11</a>
86 <a href="#section-5">5</a>. Multiple Ports on the Same Link ................................<a href="#page-12">12</a>
87 <a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-12">12</a>
88 <a href="#section-7">7</a>. Acknowledgements ...............................................<a href="#page-13">13</a>
89 <a href="#section-8">8</a>. References .....................................................<a href="#page-13">13</a>
90 <a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-13">13</a>
91 <a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-13">13</a>
92 Appendix. VLAN Inhibition Example .................................<a href="#page-14">14</a>
93
94 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
95
96 The IETF TRILL (TRansparent Interconnection of Lots of Links)
97 protocol [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>] provides optimal pair-wise data frame forwarding
98 without configuration in multi-hop networks with arbitrary topology,
99 safe forwarding even during periods of temporary loops, and support
100 for multipathing of both unicast and multicast traffic. TRILL
101 accomplishes this by using IS-IS (Intermediate System to Intermediate
102 System) [<a href="#ref-IS-IS" title="&quot;Intermediate System to Intermediate System Intra-Domain Routeing Exchange Protocol for use in Conjunction with the Protocol for Providing the Connectionless-mode Network Service (ISO 8473)&quot;">IS-IS</a>] [<a href="./rfc1195" title="&quot;Use of OSI IS-IS for routing in TCP/IP and dual environments&quot;">RFC1195</a>] link state routing and encapsulating
103 traffic using a header that includes a hop count. The design
104
105
106
107
108 <span class="grey">Perlman, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
111
112
113 supports VLANs (Virtual Local Area Networks) and optimization of the
114 distribution of multi-destination frames based on VLANs and IP-
115 derived multicast groups. Devices that implement TRILL are called
116 "RBridges" (Routing Bridges).
117
118 <a href="./rfc6327#section-2">Section&nbsp;2 of [RFC6327]</a> explains the environment for which the TRILL
119 protocol is designed and the differences between that environment and
120 the typical Layer 3 routing environment.
121
122 TRILL supports multi-access LAN (Local Area Network) links that can
123 have multiple end stations and RBridges attached. Where multiple
124 RBridges are attached to a link, native traffic to and from end
125 stations on that link is handled by a subset of those RBridges called
126 "Appointed Forwarders", with the intent that native traffic in each
127 VLAN be handled by at most one RBridge. An RBridge can be Appointed
128 Forwarder for many VLANs.
129
130 The purpose of this document is to improve the documentation of the
131 Appointed Forwarder mechanism; thus, it updates <a href="./rfc6325">RFC 6325</a>. It
132 includes reference implementation details. Alternative
133 implementations that interoperate on the wire are permitted.
134
135 The Appointed Forwarder mechanism is irrelevant to any link on which
136 end station service is not offered. This includes links configured
137 as point-to-point IS-IS links and any link with all RBridge ports on
138 that link configured as trunk ports. (In TRILL, configuration of a
139 port as a "trunk port" just means that no end station service will be
140 provided. It does not imply that all VLANs are enabled on that
141 port.)
142
143 The Appointed Forwarder mechanism has no effect on the formation of
144 adjacencies, the election of the Designated RBridge (DRB) for a link,
145 MTU matching, or pseudonode formation. Those topics are covered in
146 [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>]. Furthermore, Appointed Forwarder status has no effect on
147 the forwarding of TRILL Data frames. It only affects the handling of
148 native frames.
149
150 For other aspects of the TRILL base protocol, see [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>] and
151 [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>]. Familiarity with [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>] and [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>] is assumed in
152 this document. In case of conflict between this document and
153 [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>], this document prevails.
154
155 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology and Acronyms</span>
156
157 This document uses the acronyms defined in [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>].
158
159 A "trunk port" is a port configured with the "end station service
160 disable" bit on, as described in <a href="./rfc6325#section-4.9.1">Section&nbsp;4.9.1 of [RFC6325]</a>.
161
162
163
164 <span class="grey">Perlman, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
167
168
169 In this document, the term "link" means "bridged LAN", that is to say
170 some combination of physical links with zero or more bridges, hubs,
171 repeaters, or the like.
172
173 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
174 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
175 "OPTIONAL" in this document are to be interpreted as described in
176 [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
177
178 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Appointed Forwarders and Their Appointment</span>
179
180 The Appointed Forwarder on a link for VLAN-x is the RBridge that
181 ingresses native frames from the link and egresses native frames to
182 the link in VLAN-x. By default, the DRB (Designated RBridge) on a
183 link is in charge of native traffic for all VLANs on the link. The
184 DRB may, if it wishes, act as Appointed Forwarder for any VLAN and it
185 may appoint other RBridges that have ports on the link as Appointed
186 Forwarder for one or more VLANs.
187
188 It is important that there not be two Appointed Forwarders on a link
189 that are ingressing and egressing native frames for the same VLAN at
190 the same time. Should this occur, it could form a loop where frames
191 are not protected by a TRILL Hop Count for part of the loop. (Such a
192 condition can even occur through two Appointed Forwarders for two
193 different VLANs, VLAN-x and VLAN-y, if ports or bridges inside the
194 link are configured to map frames between VLAN-x and VLAN-y as
195 discussed in <a href="#section-2.4">Section 2.4</a>.) While TRILL tries to avoid such
196 situations, for loop safety there is also an "inhibition" mechanism
197 (see <a href="#section-3">Section 3</a>) that can cause an RBridge that is an Appointed
198 Forwarder to not ingress or egress native frames.
199
200 As discussed in <a href="#section-5">Section 5</a>, an RBridge may have multiple ports on a
201 link. As discussed in [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>], if there are multiple ports with
202 the same Media Access Control (MAC) address on a link, all but one
203 will be suspended. The case of multiple ports on a link for one
204 RBridge and the case of multiple ports with the same MAC address on a
205 link and combinations of these cases are fully accommodated; however,
206 multiple ports on a link for one RBridge is expected to be a rare
207 condition and duplicate MAC addresses are not recommended by either
208 TRILL or IEEE 802.1 standards.
209
210 Appointed Forwarder status has no effect on the forwarding of TRILL
211 Data frames. It only affects the handling of native frames.
212
213
214
215
216
217
218
219
220 <span class="grey">Perlman, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
223
224
225 There are three mechanisms by which an RBridge can be appointed or
226 un-appointed as Appointed Forwarder: as a result of the DRB elections
227 [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>] as discussed in <a href="#section-2.1">Section 2.1</a>, as a result of action by the
228 DRB as discussed in <a href="#section-2.2">Section 2.2</a>, as a result of a local configuration
229 action as discussed in <a href="#section-2.3">Section 2.3</a>.
230
231 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Appointment Effects of DRB Elections</span>
232
233 When an RBridge believes that it has become the DRB on a link, by
234 default, it can act as Appointed Forwarder for any VLANs on that link
235 that it chooses as long as its port is not configured as a trunk port
236 and has that VLAN enabled (or at least one of its ports meets these
237 criteria, if it has more than one port on the link).
238
239 An RBridge loses all Appointed Forwarder status when:
240
241 1. it decides that it has lost the status of being the DRB for a
242 link; or
243
244 2. it observes a change in the RBridge that is the DRB for the link
245 without itself becoming the DRB.
246
247 In the rare corner case where an RBridge has more than one port on a
248 link, one of which was previously the DRB election winner but has
249 just lost the DRB election to a different port of the same RBridge
250 (possibly due to management configuration of port priorities), there
251 is no change in which RBridge is the DRB. Therefore, neither of the
252 above points applies and there is no change in Appointed Forwarder
253 status.
254
255 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Appointment and Removal by the DRB</span>
256
257 The DRB may appoint other RBridges on the link through inclusion of
258 one or more Appointed Forwarders sub-TLVs [<a href="./rfc6326" title="&quot;Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS&quot;">RFC6326</a>] in a TRILL Hello
259 it sends on the Designated VLAN out the port that won the DRB
260 election. When the DRB sends any appointments in a TRILL Hello, it
261 must send all appointments for that link in that Hello. Any previous
262 appointment not included is implicitly revoked.
263
264 Although the DRB does not need to announce the VLANs for which it has
265 chosen to act as Appointed Forwarder by sending appoints for itself,
266 if the DRB wishes to revoke all appointments for RBridges other than
267 itself on the link, it is recommended that it send a TRILL Hello with
268 an appointment for itself for some VLAN.
269
270 The DRB MUST NOT send any appointments on a link unless its DRB
271 inhibition timer (see <a href="#section-3">Section 3</a>) for that link is expired.
272
273
274
275
276 <span class="grey">Perlman, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
279
280
281 How the DRB decides what other RBridges on the link, if any, to
282 appoint forwarder for which VLANs is beyond the scope of this
283 document.
284
285 <span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. Processing Forwarder Appointments</span>
286
287 When a non-DRB RBridge that can offer end station service on a link
288 receives a TRILL Hello that is not discarded for one of the reasons
289 given in [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>], it checks the source MAC address and the Port ID
290 and System ID in the Hello to determine if it is from the winning DRB
291 port. If it is not from that port, any Appointed Forwarder sub-TLVs
292 in the Hello are ignored, and there is no change in the receiving
293 RBridge's Appointed Forwarder status. Also, if no Appointed
294 Forwarder sub-TLVs are present in the TRILL Hello, there is no change
295 in the receiver's Appointed Forwarder status.
296
297 However, if the TRILL Hello is from the winning DRB port and the
298 Hello includes one or more Appointed Forwarder sub-TLVs, then the
299 receiving RBridge becomes appointed for the VLANs that are both
300 listed for it in the Hello and are enabled on the receiving port.
301 (If the appointment includes VLAN IDs 0x000 or 0xFFF, they are
302 ignored, but any other VLAN IDs are still effective.) If the
303 receiver was Appointed Forwarder for any other VLANs, its Appointed
304 Forwarder status for such other VLANs is revoked. For example, if
305 none of these sub-TLVs in a Hello appoints the receiving RBridge,
306 then it loses all Appointed Forwarder status and is no longer
307 Appointed Forwarder for any VLAN on the port where the Hello was
308 received.
309
310 The handling of one or more Appointed Forwarder sub-TLVs in a Hello
311 from the winning port that appoints the receiving RBridge is as
312 follows. An appointment in an Appointed Forwarder sub-TLV is for a
313 specific RBridge and a contiguous interval of VLAN IDs; however, as
314 stated above, it actually appoints that RBridge forwarder only for
315 the VLAN(s) in that range that are enabled on one or more ports that
316 RBridge has on the link (ignoring any ports configured as trunk ports
317 or as IS-IS point-to-point ports). If the RBridge was Appointed
318 Forwarder for any additional VLANs beyond the VLANs for which it was
319 being appointed, it loses Appointed Forwarder status for such
320 additional VLANs.
321
322 There is no reason for an RBridge to remember that it received a
323 valid appointment message for a VLAN that was ineffective because the
324 VLAN was not enabled on the port where the message was received or
325 because the port was a trunk or point-to-point port. It does not
326 become Appointed Forwarder for such a VLAN just because that VLAN is
327 later enabled or the port later reconfigured.
328
329
330
331
332 <span class="grey">Perlman, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
335
336
337 It should be straightforward for the DRB to send, within one Hello,
338 the appointments for several dozen VLAN IDs or several dozen blocks
339 of contiguous VLAN IDs. Should the VLANs the DRB wishes to appoint
340 be inconveniently distributed, for example, the proverbial case where
341 the DRB RB1 wishes to appoint RB2 forwarder for all even-numbered
342 VLANs and appoint RB3 forwarder for all odd-numbered VLANs, the
343 following method may be used. The network manager normally controls
344 what VLANs are enabled on RBridge port. Thus, the network manager
345 can appoint an RBridge forwarder for an arbitrary set of scattered
346 VLANs by enabling only those VLANs on the relevant port (or ports)
347 and then having the DRB send an appointment that appears to appoint
348 the target RBridge forwarder for all VLANs. However, for proper
349 operation and inter-RBridge communication, the Designated VLAN for a
350 link SHOULD be enabled on all RBridge ports on that link, and it may
351 not be desired to appoint the RBridge forwarder for the Designated
352 VLAN. Thus, in the general case, it would require two appointments,
353 although it would still only require one appointment if the
354 Designated VLAN were an extreme low or high value such as VLAN 0xFFE
355 or the default VLAN 1.
356
357 For example, assume the DRB wants RB2 to be Appointed Forwarder for
358 all even-numbered VLANs and the Designated VLAN for the link is VLAN
359 101. The network manager could cause all even-numbered VLANs plus
360 VLAN 101 to be enabled on the relevant port of RB2 and then, with the
361 desired effect, cause the DRB to send appointments to RB2 appointing
362 it forwarder for all VLANs from 1 through 100 and from 102 through
363 4,094.
364
365 Should the network manager have misconfigured the enabled VLANs and
366 Appointed Forwarders, resulting in two RBridges believing they are
367 Appointed Forwarders for the same VLAN, then item 4 in <a href="#section-3">Section 3</a> will
368 cause one or more of the RBridges to be inhibited for that VLAN.
369
370 <span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>. Frequency of Appointments</span>
371
372 It is not necessary for the DRB to include the forwarder appointments
373 in every TRILL Hello that it sends on the Designated VLAN for a link.
374 For loop safety, every RBridge is required to indicate, in every
375 TRILL Hello it sends in VLAN-x on a link, whether it is an Appointed
376 Forwarder for VLAN-x for that link (see item 4 in <a href="#section-3">Section 3</a>). It is
377 also RECOMMENDED that the DRB have all VLANs for which end station
378 service will be offered on the link as well as the Designated VLAN,
379 enabled. Thus, the DRB will generally be informed by other RBridges
380 on the link of the VLANs for which they believe they are Appointed
381 Forwarder. If this matches the appointments the DRB wishes to make,
382 it is not required to re-send its forwarder appointments; however,
383 for robustness, especially in cases such as VLAN misconfigurations in
384
385
386
387
388 <span class="grey">Perlman, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
391
392
393 a bridged LAN link, it is RECOMMENDED that the DRB send its forwarder
394 appointments on the Designated VLAN at least once per its Holding
395 Time on the port that won the DRB election.
396
397 <span class="h4"><a class="selflink" id="section-2.2.3" href="#section-2.2.3">2.2.3</a>. Appointed Forwarders Limit</span>
398
399 The mechanism of DRB forwarder appointment and the limited length of
400 TRILL Hellos impose a limit on the number of RBridges on a link that
401 can be Appointed Forwarders. To obtain a conservative estimate,
402 assume that no more than 1000 bytes are available in a TRILL Hello
403 for such appointments. Assume it is desired to appoint various
404 RBridges on a link forwarder for arbitrary non-intersecting sets of
405 VLANs. Using the technique discussed above would generally require
406 two appointments, or 12 bytes, per RBridge. With allowance for
407 sub-TLV and TLV overhead, appointments for 83 RBridges would fit in
408 under 1000 bytes. Including the DRB, this implies a link with 84 or
409 more RBridges attached. Links with more than a handful of RBridges
410 attached are expected to be rare.
411
412 Note: If the Designated VLAN were an extreme low or high value, such
413 as VLAN 1, which is the default and may be a common value in
414 practice, only 6 bytes per RBridge would be required. This would
415 permit twice as many different Appointed Forwarder RBridges than
416 indicated by the general analysis above or, alternatively, would take
417 only half as much space to appoint the same number of Appointed
418 Forwarders.
419
420 Unnecessary changes in Appointed Forwarders SHOULD NOT be made as
421 they may result in transient lack of end station service. Large
422 numbers of Appointed Forwarders on a link (in excess of 65) are NOT
423 RECOMMENDED due to the complexity of their establishment and
424 maintenance.
425
426 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Local Configuration Action Appointment Effects</span>
427
428 Disabling VLAN-x at an RBridge port cancels any Appointed Forwarder
429 status that RBridge has for VLAN-x unless VLAN-x is enabled on some
430 other port that the RBridge has connected to the same link.
431 Configuring a port as a trunk port or point-to-point port revokes any
432 Appointed Forwarder status that depends on enabled VLANs at that
433 port.
434
435 Causing a port to no longer be configured as a trunk or point-to-
436 point port or enabling VLAN-x on a port does not, in itself, cause
437 the RBridge to become an Appointed Forwarder for the link that port
438 is on. However, such actions can allow the port's RBridge to become
439 Appointed Forwarder by choice if it is the DRB or by appointment, if
440 it is not the DRB on the link.
441
442
443
444 <span class="grey">Perlman, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
447
448
449 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. VLAN Mapping within a Link</span>
450
451 TRILL Hellos include a field that is set to the VLAN in which they
452 are sent. If they arrive on a different VLAN, then VLAN mapping is
453 occurring within the link. (Such VLAN mapping within a link between
454 RBridges should not be confused with VLAN mapping inside an RBridge
455 [<a href="#ref-VLANMAP" title="&quot;RBridges: Campus VLAN and Priority Regions&quot;">VLANMAP</a>]). VLAN mapping between VLAN-x and VLAN-y can lead to a
456 loop if the Appointed Forwarders for the VLANs are different. If
457 such mapping within a link was allowed and occurred on two or more
458 links so that there was a cycle of VLAN mappings, a broadcast frame,
459 for example, would loop forever.
460
461 To prevent this potential problem, if the DRB on a link detects VLAN
462 mapping by receiving a Hello in VLAN-x that was sent on VLAN-y, it
463 MUST make or revoke appointments so as to assure that the same
464 RBridge (possibly the DRB) is the Appointed Forwarder on the link for
465 both VLAN-x and VLAN-y.
466
467 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Inhibition Mechanism</span>
468
469 An RBridge has, for every link on which it can offer end station
470 service (that is every link for which it can act as an Appointed
471 Forwarder), the following timers denominated in seconds:
472
473 - a DRB inhibition timer,
474
475 - a root change inhibition timer, and
476
477 - up to 4,094 VLAN inhibition timers, one for each legal VLAN ID.
478
479 The DRB and root change inhibition timers MUST be implemented.
480
481 The loss of native traffic due to inhibition will be minimized by
482 logically implementing a VLAN inhibition timer per each VLAN for
483 which end station service will ever be offered by the RBridge on the
484 link; this SHOULD be done. (See the Appendix for an example
485 motivating VLAN inhibition timers.) However, if implementation
486 limitations make a full set of such timers impractical, the VLAN
487 inhibition timers for more than one VLAN can, with care, be merged
488 into one timer. In particular, an RBridge MUST NOT merge the VLAN
489 inhibition timers together for two VLANs if it is the Appointer
490 Forwarder for one and not for the other, as this can lead to
491 unnecessary indefinitely prolonged inhibition. In the limit, there
492 will be safe operations, albeit with more native frame loss than
493 would otherwise be required, even if only two VLAN inhibition timers
494 are provided: one for VLANs for which the RBridge is the Appointed
495 Forwarder and one for all other VLANs. At least two VLAN inhibition
496
497
498
499
500 <span class="grey">Perlman, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
503
504
505 timers MUST be implemented. Where a VLAN inhibition timer represents
506 more than one VLAN, an update or test that would have been done to
507 the timer for any of the VLANs is performed on the merged timer.
508
509 These timers are set as follows:
510
511 1. On booting or management reset, each port will have its own set
512 of timers, even if two or more such ports are on the same link,
513 because the RBridge will not have had a chance to learn that yet.
514 All inhibition timers are set to expired except the DRB
515 inhibition timer that is set in accordance with item 2 below.
516 The DRB inhibition timer is handled differently because each port
517 will initially believe it is the DRB.
518
519 2. When an RBridge decides that it has become the DRB on a link,
520 including when it is first booted or reset by management, it sets
521 the DRB inhibition timer to the Holding Time of its port on that
522 link that won the DRB election.
523
524 3. When an RBridge decides that it has lost DRB status on a link, it
525 sets the DRB inhibition timer to expired.
526
527 Note: In the rare corner case where one port of an RBridge was
528 the DRB election winner, but later lost the DRB election to a
529 different port of the same RBridge on that link (perhaps due to
530 management configuration of port priority), neither 2 nor 3 above
531 applies, and the DRB timer is not changed.
532
533 4. When an RBridge RB1 receives a TRILL Hello asserting that the
534 sender is the Appointed Forwarder that either (1) arrives on
535 VLAN-x or (2) was sent on VLAN-x as indicated inside the Hello,
536 then RB1 sets its VLAN-x inhibition timer for the link to the
537 maximum of that timer's existing value and the Holding Time in
538 the received Hello. An RBridge MUST maintain VLAN inhibition
539 timers for a link to which it connects if it can offer end
540 station service on that link even if it is not currently
541 Appointed Forwarder for any VLAN on that link.
542
543 5. When an RBridge RB1 enables VLAN-x on a port connecting to a link
544 and VLAN-x was previously not enabled on any of RB1's ports on
545 that link, it sets its VLAN inhibition timer for VLAN-x for that
546 link to its Holding Time for that port. This is done even if the
547 port is configured as a trunk or point-to-point port as long as
548 there is some chance it might later be configured not to be a
549 trunk or point-to-point port.
550
551
552
553
554
555
556 <span class="grey">Perlman, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
559
560
561 6. When an RBridge detects a change in the common spanning tree root
562 bridge on a port, it sets its root change inhibition timer for
563 the link to an amount of time that defaults to 30 seconds and is
564 configurable to any value from 30 down to zero seconds. This
565 condition will not occur unless the RBridge is receiving Bridge
566 PDU (BPDUs) on the port from an attached bridged LAN. It is safe
567 to configure this inhibition time to the settling time of an
568 attached bridged LAN. For example, if it is known that Rapid
569 Spanning Tree Protocol (RSTP [<a href="#ref-802.1Q" title="&quot;IEEE Standard for Local and metropolitan area networks - Virtual Bridged Local Area Networks&quot;">802.1Q</a>]) is running throughout the
570 attached bridged LAN, it should be safe to configure this
571 inhibition time to 7 seconds or, if the attached bridges have
572 been configured to have a minimum Bridge Hello Timer, safe to
573 configure it to 4 seconds. Note that, while an RBridge could
574 determine what version of spanning tree is running on the
575 physical link between it and any directly connected bridge by
576 examination of the BPDUs it receives, it could not tell if
577 inter-bridge links beyond those directly connected bridges were
578 running classic Spanning Tree Protocol (STP), which might require
579 the root change inhibition timer to be set to 30 seconds for
580 safety.
581
582 7. When an RBridge decides that one of its ports (or a set of its
583 ports) P1 is on the same link as another of its ports (or set of
584 its ports) P2, then the inhibition timers are merged to a single
585 set of inhibition timers by using the maximum value of the
586 corresponding timers.
587
588 8. When an RBridge decides that a set of its ports that it had been
589 treating as being on the same link are no longer on the same
590 link, those ports will necessarily be on two or more links (one
591 link per port in the limit). This is handled by cloning a copy
592 of the timers for each of the two or more links to which the
593 RBridge has decided these ports connect.
594
595 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Inhibited Appointed Forwarder Behavior</span>
596
597 An Appointed Forwarder for a link is inhibited for VLAN-x if:
598
599 1. its DRB inhibition timer for that link is not expired, or
600
601 2. its root change inhibition timer for that link is not expired, or
602
603 3. its VLAN inhibition timer for that link for VLAN-x is not
604 expired.
605
606 If a VLAN-x Appointed Forwarder for a link is inhibited and receives
607 a TRILL Data frame whose encapsulated frame is in VLAN-x and would
608 normally be egressed to that link, it decapsulates the native frame
609
610
611
612 <span class="grey">Perlman, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
615
616
617 as usual. However, it does not output it to or queue it for that
618 link, although, if appropriate (for example, the frame is multi-
619 destination), it may output it to or queue it for other links.
620
621 If a VLAN-x Appointed Forwarder for a link is inhibited and receives
622 a native frame in VLAN-x that would normally be ingressed from that
623 link, the native frame is ignored except for address learning.
624
625 An RBridge with one or more unexpired inhibition timers, possibly
626 including an unexpired inhibition timer for VLAN-x, is still required
627 to indicate in TRILL Hellos it sends on VLAN-x whether or not it is
628 Appointed Forwarder for VLAN-x for the port on which it sends the
629 Hello.
630
631 Inhibition has no effect on the receipt or forwarding of TRILL Data
632 frames.
633
634 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Multiple Ports on the Same Link</span>
635
636 An RBridge may have multiple ports on the same link. Some of these
637 ports may be suspended due to MAC address duplication as described in
638 [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>]. Suspended ports never ingress or egress native frames.
639
640 If an RBridge has one or more non-suspended ports on a link and those
641 ports offer end station service, that is, those ports are not
642 configured as point-to-point or trunk ports, then that RBridge is
643 eligible to be an Appointed Forwarder for that link. It can become
644 Appointed Forwarder either by its choice, because it is the DRB, or
645 by appointment by the DRB as described in Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a>.
646
647 If an RBridge that is the Appointed Forwarder for VLAN-x on a link
648 has multiple non-suspended ports on that link, it may load share the
649 task of ingressing and egressing VLAN-x native frames across those
650 ports however it chooses, as long as there is no case in which a
651 frame it egresses onto the link from one port can be ingressed on
652 another of its ports, creating a loop. If the RBridge is the
653 Appointed Forwarder for multiple VLANs, a straightforward thing to do
654 would be to partition those VLANs among the ports it has on the link.
655
656 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
657
658 This memo provides improved documentation of the TRILL Appointed
659 Forwarder mechanism. It does not change the security considerations
660 of the TRILL base protocol. See <a href="./rfc6325#section-6">Section&nbsp;6 of [RFC6325]</a>.
661
662
663
664
665
666
667
668 <span class="grey">Perlman, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
671
672
673 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
674
675 The authors of [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>] and [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>], those listed in the
676 Acknowledgements section of [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>] and [<a href="./rfc6327" title="&quot;Routing Bridges (RBridges): Adjacency&quot;">RFC6327</a>], and Ron Bonica,
677 Stewart Bryant, Linda Dunbar, Les Ginsberg, Erik Nordmark, Dan
678 Romascanu, and Mike Shand are hereby thanked for their contributions.
679
680 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
681
682 Normative and Informative references for this document are listed
683 below.
684
685 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
686
687 [<a id="ref-802.1Q">802.1Q</a>] IEEE 802.1, "IEEE Standard for Local and metropolitan
688 area networks - Virtual Bridged Local Area Networks",
689 IEEE Std 802.1Q-2011, May 2011.
690
691 [<a id="ref-IS-IS">IS-IS</a>] ISO/IEC 10589:2002, Second Edition, "Intermediate System
692 to Intermediate System Intra-Domain Routeing Exchange
693 Protocol for use in Conjunction with the Protocol for
694 Providing the Connectionless-mode Network Service (ISO
695 8473)", 2002.
696
697 [<a id="ref-RFC1195">RFC1195</a>] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
698 dual environments", <a href="./rfc1195">RFC 1195</a>, December 1990.
699
700 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
701 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
702
703 [<a id="ref-RFC6325">RFC6325</a>] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and A.
704 Ghanwani, "Routing Bridges (RBridges): Base Protocol
705 Specification", <a href="./rfc6325">RFC 6325</a>, July 2011.
706
707 [<a id="ref-RFC6326">RFC6326</a>] Eastlake, D., Banerjee, A., Dutt, D., Perlman, R., and A.
708 Ghanwani, "Transparent Interconnection of Lots of Links
709 (TRILL) Use of IS-IS", <a href="./rfc6326">RFC 6326</a>, July 2011.
710
711 [<a id="ref-RFC6327">RFC6327</a>] Eastlake 3rd, D., Perlman, R., Ghanwani, A., Dutt, D.,
712 and V. Manral, "Routing Bridges (RBridges): Adjacency",
713 <a href="./rfc6327">RFC 6327</a>, July 2011.
714
715 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
716
717 [<a id="ref-VLANMAP">VLANMAP</a>] Perlman, R., Dutt, D., Banerjee, A., Rijhsinghani, A.,
718 and D. Eastlake, "RBridges: Campus VLAN and Priority
719 Regions", Work in Progress, October 2011.
720
721
722
723
724 <span class="grey">Perlman, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
727
728
729 Appendix. VLAN Inhibition Example
730
731 The per-VLAN inhibition timers (or the equivalent) are needed to be
732 loop safe in the case of misconfigured bridges on a link.
733
734 For a simple example, assume that RB1 and RB2 are the only RBridges
735 on the link, that RB1 is higher priority to be the DRB, and that they
736 both want VLAN 1 (the default) to be the Designated VLAN. However,
737 there is a bridge between them configured so that RB1 can see all the
738 frames sent by RB2 but none of the frames from RB1 can get through to
739 RB2.
740
741 Both will think they are the DRB. RB1 because it is higher priority
742 even though it sees the Hellos from RB2, and RB2 because it doesn't
743 see the Hellos from RB1 and therefore thinks it is highest priority.
744
745 Say RB1 chooses to act as Appointed Forwarder for VLANs 2 and 3 while
746 RB2 chooses to act as Appointed Forwarder for VLANs 3 and 4. There
747 is no problem with VLANs 2 and 4 but if you do not do something about
748 it, you could have a loop involving VLAN 3. RB1 will see the Hellos
749 RB2 issues on VLAN 3 declaring itself Appointed Forwarder, so RB1
750 will be inhibited on VLAN 3. RB2 does not see the Hellos issued by
751 RB1 on VLAN 3, so RB2 will become uninhibited and will handle VLAN 3
752 native traffic.
753
754 However, this situation may change. RB2 might crash, the bridge
755 might crash, or RB2 might be reconfigured so it no longer tried to
756 act as Appointed Forwarder for VLAN 3, or other issues may occur.
757 So, RB1 has to maintain a VLAN 3 inhibition timer, and if it sees no
758 Hellos from any other RBridge on the link claiming to be Appointed
759 Forwarder for VLAN 3 in a long enough time, then RB1 becomes
760 uninhibited for that VLAN on the port in question and can handle end
761 station traffic in VLAN 3.
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780 <span class="grey">Perlman, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc6439">RFC 6439</a> RBridges: Appointed Forwarders November 2011</span>
783
784
785 Authors' Addresses
786
787 Radia Perlman
788 Intel Labs
789 2200 Mission College Blvd.
790 Santa Clara, CA 95054 USA
791
792 Phone: +1-408-765-8080
793 EMail: [email protected]
794
795
796 Donald Eastlake 3rd
797 Huawei Technologies
798 155 Beaver Street
799 Milford, MA 01757 USA
800
801 Phone: +1-508-333-2270
802 EMail: [email protected]
803
804
805 Yizhou Li
806 Huawei Technologies
807 101 Software Avenue,
808 Nanjing 210012, China
809
810 Phone: +86-25-56622310
811 EMail: [email protected]
812
813
814 Ayan Banerjee
815 Cisco Systems
816 170 West Tasman Drive
817 San Jose, CA 95134 USA
818
819 Phone: +1-408-333-7149
820 EMail: [email protected]
821
822
823 Fangwei Hu
824 ZTE Corporation
825 889 Bibo Road
826 Shanghai 201203
827 China
828
829 Phone: +86-21-68896273
830 EMail: [email protected]
831
832
833
834
835
836 Perlman, et al. Standards Track [Page 15]
837 </pre>