Debian Codegraph @

rfc7179.html

raw
1 <pre>Internet Engineering Task Force (IETF) D. Eastlake 3rd
2 Request for Comments: 7179 Huawei
3 Updates: <a href="./rfc6325">6325</a> A. Ghanwani
4 Category: Standards Track Dell
5 ISSN: 2070-1721 V. Manral
6 Ionos Corp.
7 Y. Li
8 Huawei
9 C. Bestler
10 Nexenta Systems
11 May 2014
12
13
14 <span class="h1">Transparent Interconnection of Lots of Links (TRILL): Header Extension</span>
15
16 Abstract
17
18 The IETF Transparent Interconnection of Lots of Links (TRILL) base
19 protocol (<a href="./rfc6325">RFC 6325</a>) specifies minimal hooks to safely support TRILL
20 Header extensions. This document specifies an initial extension
21 providing additional flag bits and specifies some of those bits. It
22 updates <a href="./rfc6325">RFC 6325</a>.
23
24 Status of This Memo
25
26 This is an Internet Standards Track document.
27
28 This document is a product of the Internet Engineering Task Force
29 (IETF). It represents the consensus of the IETF community. It has
30 received public review and has been approved for publication by the
31 Internet Engineering Steering Group (IESG). Further information on
32 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
33
34 Information about the current status of this document, any errata,
35 and how to provide feedback on it may be obtained at
36 <a href="http://www.rfc-editor.org/info/rfc7179">http://www.rfc-editor.org/info/rfc7179</a>.
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2014 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-3">3</a>
75 <a href="#section-1.1">1.1</a>. Conventions Used in This Document ..........................<a href="#page-3">3</a>
76 <a href="#section-2">2</a>. TRILL Header Extensions .........................................<a href="#page-3">3</a>
77 <a href="#section-2.1">2.1</a>. RBridge Extended Flag Handling Requirements ................<a href="#page-5">5</a>
78 <a href="#section-2.2">2.2</a>. No Critical Surprises ......................................<a href="#page-5">5</a>
79 <a href="#section-2.3">2.3</a>. Extended Header Flags ......................................<a href="#page-6">6</a>
80 <a href="#section-2.3.1">2.3.1</a>. Critical Summary Bits ...............................<a href="#page-7">7</a>
81 <a href="#section-2.4">2.4</a>. Conflict of Extensions .....................................<a href="#page-8">8</a>
82 <a href="#section-3">3</a>. Specific Extended Header Flags ..................................<a href="#page-9">9</a>
83 <a href="#section-3.1">3.1</a>. RBridge Channel Alert Extended Flags .......................<a href="#page-9">9</a>
84 <a href="#section-4">4</a>. Additions to IS-IS ..............................................<a href="#page-9">9</a>
85 <a href="#section-5">5</a>. IANA Considerations ............................................<a href="#page-10">10</a>
86 <a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-10">10</a>
87 <a href="#section-7">7</a>. Acknowledgements ...............................................<a href="#page-11">11</a>
88 <a href="#section-8">8</a>. References .....................................................<a href="#page-11">11</a>
89 <a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-11">11</a>
90 <a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-11">11</a>
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 The base IETF Transparent Interconnection of Lots of Links (TRILL)
116 protocol [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>] provides a TRILL Header extension feature and
117 describes minimal hooks to safely support header extensions. (This
118 feature is called "options" in <a href="./rfc6325#section-3.8">Section&nbsp;3.8 of [RFC6325]</a>.) But,
119 except for the first two bits, the TRILL base protocol document does
120 not specify the structure of extensions to the TRILL Header nor the
121 details of any particular extension.
122
123 This document is consistent with [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>] and provides further
124 details. It specifies an initial extension word providing additional
125 flag bits and specifies some of those bits. Additional extensions,
126 including TLV-encoded options, may be specified in later documents,
127 for example, [<a href="#ref-Options" title="&quot;RBridges: Further TRILL Header Extensions&quot;">Options</a>] and [<a href="#ref-Options2" title="&quot;RBridges: More Proposed TRILL Header Options&quot;">Options2</a>].
128
129 <a href="#section-2">Section 2</a> below describes some general principles of TRILL Header
130 extensions and an initial extension. <a href="#section-3">Section 3</a> specifies a pair of
131 flags in this initial extension.
132
133 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used in This Document</span>
134
135 The terminology and acronyms defined in [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>] are used herein
136 with the same meaning. Devices implementing the TRILL protocol are
137 referred to as RBridges (Routing Bridges) or TRILL Switches.
138
139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
140 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
141 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
142
143 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. TRILL Header Extensions</span>
144
145 The base TRILL protocol includes a feature for extension of the TRILL
146 Header (see [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>], Sections <a href="#section-3.5">3.5</a> and <a href="#section-3.8">3.8</a>). The 5-bit Op-Length
147 header field gives the length of the extensions to the TRILL Header
148 in units of 4 octets, which allows up to 124 octets of header
149 extension. If Op-Length is zero, there are no header extensions
150 present; else, the extension area follows immediately after the
151 Ingress RBridge Nickname field of the TRILL Header. The first 32-bit
152 word of the optional extensions area consists of an extended flags
153 area and critical summary bits as specified in this document.
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
167
168
169 As described below, provision is made for
170
171 o hop-by-hop flags, which might affect any RBridge that receives a
172 TRILL Data frame with such a flag set,
173
174 o ingress-to-egress flags, which would only necessarily affect the
175 RBridge(s) where a TRILL frame is decapsulated,
176
177 o flags affecting an as-yet-unspecified class of RBridges, for
178 example, border RBridges in a TRILL campus extended to support
179 multi-level IS-IS (Intermediate System to Intermediate System)
180 [<a href="#ref-MultiLevel" title="&quot;Flexible Multilevel TRILL (Transparent Interconnection of Lots of Links)&quot;">MultiLevel</a>], and
181
182 o both "critical" and "non-critical" flags.
183
184 Any RBridge receiving a frame with a critical hop-by-hop extension
185 that it does not implement MUST discard the frame because it is
186 unsafe to process the frame without understanding such a critical
187 extension.
188
189 Any egress RBridge receiving a frame with a critical ingress-to-
190 egress extension it does not implement MUST drop the frame if it is a
191 unicast frame (TRILL Header M bit = 0); if it is a multi-destination
192 TRILL Data frame (M=1), then it MUST NOT be egressed at that RBridge,
193 but the egress RBridge still forwards such a frame on the
194 distribution tree.
195
196 Non-critical extensions can be safely ignored.
197
198 Any extended flag indicating a significant change in the structure or
199 interpretation of later parts of the frame that, if the extended flag
200 were ignored, could cause a failure of service or violation of
201 security policy MUST be a critical extension. If such an extended
202 flag affects any fields that transit RBridges will examine, it MUST
203 be a hop-by-hop critical extended flag.
204
205 Note: Most RBridge implementations are expected to be optimized
206 for simple and common cases of frame forwarding and processing.
207 Although the hard limit on the header extensions area length, the
208 32-bit alignment of the extension area, and the presence of
209 critical extension summary bits, as described below, are intended
210 to assist in the efficient hardware processing of frames with a
211 TRILL Header extensions area, nevertheless the inclusion of
212 extensions may cause frame processing using a "slow path" with
213 inferior performance to "fast path" processing. Limited slow path
214 throughput of such frames could cause some of them to be
215 discarded.
216
217
218
219
220 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
223
224
225 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. RBridge Extended Flag Handling Requirements</span>
226
227 All RBridges MUST check whether there are any critical flags set that
228 are necessarily applicable to their processing of the frame. To
229 assist in this task, critical summary bits are provided that cover
230 not only the extended flags specified herein but will cover any
231 further extensions that may be specified in future documents, for
232 example, [<a href="#ref-Options" title="&quot;RBridges: Further TRILL Header Extensions&quot;">Options</a>] and [<a href="#ref-Options2" title="&quot;RBridges: More Proposed TRILL Header Options&quot;">Options2</a>]. If an RBridge does not implement
233 all critical flags in a TRILL Data frame, it MUST treat the frame as
234 having an unimplemented critical extension as described in <a href="#section-2">Section 2</a>.
235 A transit or egress RBridge may assume that the critical summary bits
236 are correct.
237
238 In addition, a transit RBridge:
239
240 o MAY set or clear hop-by-hop flags as specified for such flags;
241
242 o MUST adjust the length of the extensions area, including changing
243 Op-Length in the TRILL Header, as appropriate if it adds or
244 removes the extended header flags word;
245
246 o MUST, if it adds the word of extended header flags or changes any
247 critical flags, correctly set the critical summary bits in the
248 extended header flags word;
249
250 o MUST NOT remove the extended header flags word unless it is all
251 zero (either on arrival or after permitted modifications); and
252
253 o MUST NOT set or clear ingress-to-egress or reserved extended
254 header flags except as specifically permitted in the specification
255 of such flags.
256
257 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. No Critical Surprises</span>
258
259 RBridges advertise the extended header flags they support in IS-IS
260 PDUs (Protocol Data Units) [<a href="./rfc7176" title="&quot;Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS&quot;">RFC7176</a>]. Unless an RBridge advertises
261 support for a critical extended header flag, it will not normally
262 receive frames with that flag set. An RBridge is not required to
263 support any extensions.
264
265 An RBridge SHOULD NOT set a critical extended flag in a frame unless,
266
267 o for a critical hop-by-hop extended header flag, it has determined
268 that the next hop RBridge or RBridges that will accept the frame
269 support that flag,
270
271
272
273
274
275
276 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
279
280
281 o for a critical ingress-to-egress extended header flag, it has
282 determined that the RBridge or RBridges that will egress the frame
283 support that flag, or
284
285 o for a critical reserved extended header flag, it may set such a
286 flag only if it understands which RBridges it is applicable to and
287 has determined that those RBridges that will accept the frame
288 support that flag.
289
290 "SHOULD NOT" is specified above since there may be cases where it is
291 acceptable for those frames, particularly for the multi-destination
292 case, to be discarded or not egressed by any RBridges that do not
293 implement the extended flag.
294
295 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Extended Header Flags</span>
296
297 If any extensions are present in a TRILL Header, as indicated by a
298 non-zero Op-Length field, the first 32 bits of the extensions area
299 consist of extended header flags, as described below. The remainder
300 of the extensions area, if any, after the initial 32 bits may be
301 specified in later documents, for example, [<a href="#ref-Options" title="&quot;RBridges: Further TRILL Header Extensions&quot;">Options</a>] and [<a href="#ref-Options2" title="&quot;RBridges: More Proposed TRILL Header Options&quot;">Options2</a>].
302
303 Any RBridge adding an extensions area to a TRILL Header must set the
304 first 32 bits to zero except when permitted or required to set one or
305 more of those bits as specified. For TRILL Data frames with
306 extensions present, any transit RBridge that does not discard the
307 frame MUST transparently copy the extended flags word, except for
308 modifications permitted by an extension implemented by that RBridge.
309
310 The extended header flags word is illustrated below and the meanings
311 of these bits is further described in the list following the figure.
312
313 0 1 2 3
314 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
315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
316 |Crit.| CHbH | NCHbH |CRSV | NCRSV | CItE | NCItE |
317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
318 | ... additional optional 32-bit aligned words of extension |
319 | possibly including TLV extensions ...
320
321 (The first two critical summary bits are as specified in [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>].
322 In this document, an "S", for Summary, has been added at the end of
323 their acronyms. A third critical summary bit is also specified
324 herein and its acronym also ends with an "S" for consistency.)
325
326
327
328
329
330
331
332 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
335
336
337 Bits Description
338 --------------------
339
340 0-2 Crit.: Critical summary bits.
341 0 CHbHS: Critical Hop-by-Hop extension(s) are present.
342 1 CItES: Critical Ingress-to-Egress extension(s) are present.
343 2 CRSVS: Critical Reserved extension(s) are present.
344
345 3-7 CHbH: Critical Hop-by-Hop extended flag bits.
346 8-13 NCHbH: Non-critical Hop-by-Hop extended flag bits.
347
348 14-16 CRSV: Critical Reserved extended flag bits.
349 17-20 NCRSV: Non-critical Reserved extended flag bits.
350
351 21-26 CItE: Critical Ingress-to-Egress extended flag bits.
352 27-31 NCItE: Non-critical Ingress-to-Egress extended flag bits.
353
354 <span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>. Critical Summary Bits</span>
355
356 The top three bits of the extended header flags area, bits 0, 1, and
357 2 above, are called the critical summary bits. They summarize the
358 presence of critical extensions as follows:
359
360 CHbHS: If the CHbHS (Critical Hop-by-Hop Summary) bit is one, one or
361 more critical hop-by-hop extensions are present. These might be
362 critical hop-by-hop extended header flags or critical hop-by-hop
363 extensions after the first word in the extensions area. Transit
364 RBridges that do not support all of the critical hop-by-hop
365 extensions present, for example, an RBridge that supported no
366 critical hop-by-hop extensions, MUST drop the frame. If the CHbHS
367 bit is zero, the frame is safe, from the point of view of
368 extensions processing, for a transit RBridge to forward,
369 regardless of what extensions that RBridge does or does not
370 support.
371
372 CItES: If the CItES (Critical Ingress-to-Egress Summary) bit is a
373 one, one or more critical ingress-to-egress extensions are
374 present. These might be critical ingress-to-egress extended
375 header flags or critical ingress-to-egress extensions after the
376 first word in the extensions area. If the CItES bit is zero, no
377 such extensions are present. If either CHbHS or CItES is non-
378 zero, egress RBridges that do not support all critical extensions
379 present, for example, an RBridge that supports no critical
380 extensions, MUST drop the frame. If both CHbHS and CItES are
381 zero, the frame is safe, from the point of view of extensions, for
382 an egress RBridge to process, regardless of what extensions that
383 RBridge does or does not support.
384
385
386
387
388 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
391
392
393 CRSVS: If the CRSVS (Critical Reserved Summary) bit is a one, one or
394 more critical extensions are present that are reserved to apply to
395 a class of RBridges to be specified in the future, for example,
396 border RBridges in a TRILL campus extended to support multi-level
397 IS-IS. This class will be a subset of transit RBridges. RBridges
398 in this class MUST drop frames with the CRSVS bit set unless they
399 implement all critical hop-by-hop and all critical reserved
400 extensions present in the frame.
401
402 The critical summary bits enable simple and efficient processing of
403 TRILL Data frames by egress RBridges that support no critical
404 extensions, by transit RBridges that support no critical hop-by-hop
405 extensions, and by RBridges in the reserved class that support no
406 critical hop-by-hop or reserved extensions. Such RBridges need only
407 check whether Op-Length is non-zero and, if it is, check the top one,
408 two, or three bits just after the fixed portion of the TRILL Header.
409 Based on those three bits, such RBridges can decide whether to
410 discard or forward/process the frame.
411
412 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Conflict of Extensions</span>
413
414 Defining TRILL extensions including extended header flags that
415 conflict with each other would be undesirable. Should conflicting
416 extensions appear in the same packet, the results would be
417 unpredictable if different implementations processed them in
418 different orders. While rules could be defined to specify how to
419 predictably process conflicting extensions, such rules would also
420 limit implementation flexibility and could impose substantial
421 processing burdens.
422
423 Conflicting extensions SHOULD NOT be defined, but if they are,
424 careful thought should be given as to whether and how to specify the
425 handling of conflicting extensions.
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
447
448
449 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Specific Extended Header Flags</span>
450
451 The table below shows the state of TRILL Header extended flag
452 assignments. See <a href="#section-5">Section 5</a> for IANA Considerations.
453
454 Bits Purpose Section
455 ----------------------------------------------------------------
456 0-2 Critical Summary Bits 2.3.1
457 3-6 available critical hop-by-hop flags
458 7 Critical Channel Alert flag 3.1
459 8 Non-critical Channel Alert flag 3.1
460 9-13 available non-critical hop-by-hop flags
461 14-16 available critical reserved flags
462 17-20 available non-critical reserved flags
463 21-26 available critical ingress-to-egress flags
464 27-31 available non-critical ingress-to-egress flags
465
466 Table 1: Extended Header Flags Area
467
468 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. RBridge Channel Alert Extended Flags</span>
469
470 The RBridge Channel Alert extended header flags indicate that the
471 frame is an RBridge Channel frame [<a href="./rfc7178" title="&quot;Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support&quot;">RFC7178</a>] that requests processing
472 at each hop.
473
474 If the Critical Channel Alert flag (bit 7) is a one and the RBridge
475 does not implement the RBridge Channel feature or the particular
476 RBridge Channel protocol involved [<a href="./rfc7178" title="&quot;Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support&quot;">RFC7178</a>] or the frame does not
477 actually appear to be an RBridge Channel message, then the frame is
478 discarded. This permits implementation, for example, of a channel
479 message requiring strict source routing or the like, with assurance
480 that it will be discarded rather than deviate from the directed path.
481
482 If the frame is not discarded as described above, then the presence
483 of either the Critical or Non-critical Channel Alert flag alerts
484 transit RBridges to the presence of an RBridge Channel message
485 [<a href="./rfc7178" title="&quot;Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support&quot;">RFC7178</a>] that may require special handling. The non-critical alert
486 flag supports, for example, an RBridge Channel protocol message
487 including a "record route" function where not recording transit
488 RBridges that do not support this function is acceptable.
489
490 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Additions to IS-IS</span>
491
492 RBridges use IS-IS Link State PDUs (LSPs) to inform other RBridges
493 which extended header flags they support. The IS-IS PDU(s), TLV(s),
494 or sub-TLV(s) used to encode and advertise this information are
495 specified in a separate document [<a href="./rfc7176" title="&quot;Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS&quot;">RFC7176</a>].
496
497
498
499
500 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
503
504
505 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
506
507 IANA has created a "TRILL Extended Header Flags" subregistry within
508 the TRILL Parameters registry. The "TRILL Extended Header Flags"
509 subregistry is initially populated as specified in Table 1 in <a href="#section-3">Section</a>
510 <a href="#section-3">3</a>. References in that table to sections of this document have been
511 replaced in the IANA subregistry by references to this document as an
512 RFC.
513
514 New TRILL extended header flags are allocated by IETF Review
515 [<a href="./rfc5226" title="">RFC5226</a>].
516
517 To indicate support of extended header flags, IANA has assigned the
518 following bits in the TRILL-VER and PORT-TRILL-VER Sub-TLV Capability
519 Flag registries created by [<a href="./rfc7176" title="&quot;Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS&quot;">RFC7176</a>]:
520
521 o Bits 3-13 of the PORT-TRILL-VER Sub-TLV Capability Flags have been
522 assigned to indicate support of TRILL hop-by-hop extended header
523 flags 3-13.
524
525 o Bits 14-31 of the TRILL-VER Sub-TLV Capability Flags have been
526 assigned to indicate support of TRILL extended header flags 14-31.
527
528 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
529
530 For general TRILL protocol security considerations, see [<a href="./rfc6325" title="&quot;Routing Bridges (RBridges): Base Protocol Specification&quot;">RFC6325</a>].
531
532 For security considerations related to extended header flags, see the
533 document where the flag is specified.
534
535 It is important that the critical summary bits in the extended header
536 flags word be set properly. If set when critical extensions of the
537 appropriate category are not present, frames may be unnecessarily
538 discarded. If not set when critical extensions are present, frames
539 may be mishandled or corrupted, and intended security policies may be
540 violated.
541
542 The RBridge Channel Alert extended header flags have the following
543 security considerations. Implementations should keep in mind that
544 they might be erroneously set in a frame. If either RBridge Channel
545 Alert flag is found set in a frame that is not an RBridge Channel
546 message [<a href="./rfc7178" title="&quot;Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support&quot;">RFC7178</a>], the flag MAY be cleared and should have no effect
547 except, possibly, delaying processing of the frame. If either
548 RBridge Channel Alert flag is erroneously omitted from a frame,
549 desired per-hop processing for the frame may not occur.
550
551
552
553
554
555
556 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
559
560
561 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
562
563 The following, listed in alphabetic order, are thanked for their
564 valuable contributions: Ben Campbell, Adrian Farrel, Barry Leiba,
565 and Thomas Narten.
566
567 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
568
569 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
570
571 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
572 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
573
574 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing
575 an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC</a>
576 <a href="./rfc5226">5226</a>, May 2008.
577
578 [<a id="ref-RFC6325">RFC6325</a>] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and
579 A. Ghanwani, "Routing Bridges (RBridges): Base Protocol
580 Specification", <a href="./rfc6325">RFC 6325</a>, July 2011.
581
582 [<a id="ref-RFC7176">RFC7176</a>] Eastlake 3rd, D., Senevirathne, T., Ghanwani, A., Dutt,
583 D., and A. Banerjee, "Transparent Interconnection of
584 Lots of Links (TRILL) Use of IS-IS", <a href="./rfc7176">RFC 7176</a>, May
585 2014.
586
587 [<a id="ref-RFC7178">RFC7178</a>] Eastlake 3rd, D., Manral, V., Li, Y., Aldrin, S., and
588 D. Ward, "Transparent Interconnection of Lots of Links
589 (TRILL): RBridge Channel Support", <a href="./rfc7178">RFC 7178</a>, May 2014.
590
591 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
592
593 [<a id="ref-MultiLevel">MultiLevel</a>] Perlman, R., Eastlake 3rd, D., Ghanwani, A., and H.
594 Zhai, "Flexible Multilevel TRILL (Transparent
595 Interconnection of Lots of Links)", Work in Progress,
596 January 2014.
597
598 [<a id="ref-Options">Options</a>] Eastlake 3rd, D., Ghanwani, A., Manral, V., and C.
599 Bestler, "RBridges: Further TRILL Header Extensions",
600 Work in Progress, June 2012.
601
602 [<a id="ref-Options2">Options2</a>] Eastlake 3rd, D., "RBridges: More Proposed TRILL Header
603 Options", Work in Progress, October 2011.
604
605
606
607
608
609
610
611
612 <span class="grey">Eastlake, 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="./rfc7179">RFC 7179</a> TRILL: Header Extension May 2014</span>
615
616
617 Authors' Addresses
618
619 Donald Eastlake 3rd
620 Huawei R&amp;D USA
621 155 Beaver Street
622 Milford, MA 01757
623 USA
624
625 Phone: +1-508-333-2270
626 EMail: [email protected]
627
628
629 Anoop Ghanwani
630 Dell
631 5450 Great America Parkway
632 Santa Clara, CA 95054
633 USA
634
635 EMail: [email protected]
636
637
638 Vishwas Manral
639 Ionos Corp.
640 4100 Moorpark Ave.
641 San Jose, CA 95117
642 USA
643
644 EMail: [email protected]
645
646
647 Yizhou Li
648 Huawei Technologies
649 101 Software Avenue,
650 Nanjing 210012
651 China
652
653 Phone: +86-25-56622310
654 EMail: [email protected]
655
656
657 Caitlin Bestler
658 Nexenta Systems
659 455 El Camino Real
660 Santa Clara, CA 95050
661 USA
662
663 EMail: [email protected]
664
665
666
667
668 Eastlake, et al. Standards Track [Page 12]
669 </pre>