idnits 2.17.1 draft-ietf-isis-rfc6326bis-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1694 has weird spacing: '...Section sub...' -- The document date (January 22, 2014) is 3744 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '2' on line 1671 -- Looks like a reference, but probably isn't: '3' on line 1672 -- Looks like a reference, but probably isn't: '4' on line 1673 -- Looks like a reference, but probably isn't: '5' on line 1674 -- Looks like a reference, but probably isn't: '6' on line 1675 -- Looks like a reference, but probably isn't: '7' on line 1679 -- Looks like a reference, but probably isn't: '8' on line 1680 -- Looks like a reference, but probably isn't: '15' on line 1688 -- Looks like a reference, but probably isn't: '16' on line 1689 -- Looks like a reference, but probably isn't: '17' on line 1690 -- Looks like a reference, but probably isn't: '18' on line 1691 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-10589' ** Obsolete normative reference: RFC 4971 (Obsoleted by RFC 7981) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) ** Obsolete normative reference: RFC 6327 (Obsoleted by RFC 7177) ** Obsolete normative reference: RFC 6439 (Obsoleted by RFC 8139) -- Obsolete informational reference (is this intentional?): RFC 6326 (ref. 'Err2869') (Obsoleted by RFC 7176) -- Duplicate reference: RFC6326, mentioned in 'RFC6326', was also mentioned in 'Err2869'. -- Obsolete informational reference (is this intentional?): RFC 6326 (Obsoleted by RFC 7176) -- Obsolete informational reference (is this intentional?): RFC 7042 (Obsoleted by RFC 9542) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 17 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Donald Eastlake 2 INTERNET-DRAFT Huawei 3 Intended status: Proposed Standard Tissa Senevirathne 4 Obsoletes: 6326 Cisco 5 Anoop Ghanwani 6 Dell 7 Dinesh Dutt 8 Cumulus Networks 9 Ayan Banerjee 10 Insieme Networks 11 Expires: July 21, 2014 January 22, 2014 13 Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS 14 16 Abstract 18 The IETF TRILL (Transparent Interconnection of Lots of Links) 19 protocol provides optimal pair-wise data frame forwarding without 20 configuration in multi-hop networks with arbitrary topology and link 21 technology, and support for multipathing of both unicast and 22 multicast traffic. This document specifies the data formats and code 23 points for the IS-IS extensions to support TRILL. These data formats 24 and code points may also be used by technologies other than TRILL. 25 This document obsoletes RFC 6326. 27 Status of This Memo 29 This Internet-Draft is submitted to IETF in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Distribution of this document is unlimited. Comments should be sent 33 to the TRILL working group mailing list. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF), its areas, and its working groups. Note that 37 other groups may also distribute working documents as Internet- 38 Drafts. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 The list of current Internet-Drafts can be accessed at 46 http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft 47 Shadow Directories can be accessed at 48 http://www.ietf.org/shadow.html. 50 Table of Contents 52 1. Introduction............................................3 53 1.1 Conventions Used in This Document....................3 54 2. TLV and Sub-TLV Extensions to IS-IS for TRILL..........5 55 2.1 Group Address TLV....................................5 56 2.1.1 Group MAC Address Sub-TLV..........................5 57 2.1.2 Group IPv4 Address Sub-TLV.........................7 58 2.1.3 Group IPv6 Address Sub-TLV.........................8 59 2.1.4 Group Labeled MAC Address Sub-TLV..................8 60 2.1.5 Group Labeled IPv4 Address Sub-TLV................10 61 2.1.6 Group Labeled IPv6 Address Sub-TLV................11 62 2.2 Multi-Topology-Aware Port Capability Sub-TLVs.......11 63 2.2.1 Special VLANs and Flags Sub-TLV...................12 64 2.2.2 Enabled-VLANs Sub-TLV.............................13 65 2.2.3 Appointed Forwarders Sub-TLV......................14 66 2.2.4 Port TRILL Version Sub-TLV........................15 67 2.2.5 VLANs Appointed Sub-TLV...........................16 68 2.3 Sub-TLVs of the Router and MT Capability TLVs.......17 69 2.3.1 TRILL Version Sub-TLV.............................17 70 2.3.2 Nickname Sub-TLV..................................18 71 2.3.3 Trees Sub-TLV.....................................19 72 2.3.4 Tree Identifiers Sub-TLV..........................20 73 2.3.5 Trees Used Identifiers Sub-TLV....................21 74 2.3.6 Interested VLANs and Spanning Tree Roots Sub-TLV..21 75 2.3.7 VLAN Group Sub-TLV................................24 76 2.3.8 Interested Labels and Spanning Tree Roots Sub-TLV.24 77 2.3.9 RBridge Channel Protocols Sub-TLV.................26 78 2.3.10 Affinity Sub-TLV.................................28 79 2.3.11 Label Group Sub-TLV..............................30 80 2.4 MTU Sub-TLV for Ext. Reachability and MT ISN TLVs...30 81 2.5 TRILL Neighbor TLV..................................31 82 3. MTU PDUs...............................................34 83 4. Use of Existing PDUs and TLVs..........................35 84 4.1 TRILL IIH PDUs......................................35 85 4.2 Area Address........................................35 86 4.3 Protocols Supported.................................35 87 4.4 Link State PDUs (LSPs)..............................36 88 4.5 Originating LSP Buffer Size.........................36 89 5. IANA Considerations....................................37 90 5.1 TLVs................................................37 91 5.2 sub-TLVs............................................37 92 5.3 PDUs................................................39 93 5.4 Reserved and Capability Bits........................39 94 5.5 TRILL Neighbor Record Flags.........................40 95 6. Security Considerations................................41 96 7. Change from RFC 6326...................................42 97 8. Normative References...................................44 98 9. Informative References.................................45 99 Acknowledgements..........................................47 100 Authors' Addresses........................................48 102 1. Introduction 104 The IETF TRILL (Transparent Interconnection of Lots of Links) 105 protocol [RFC6325] [RFC6327] provides transparent forwarding in 106 multi-hop networks with arbitrary topology and link technologies 107 using a header with a hop count and link state routing. TRILL 108 provides optimal pair-wise forwarding without configuration, safe 109 forwarding even during periods of temporary loops, and support for 110 multipathing of both unicast and multicast traffic. Intermediate 111 Systems (ISs) implementing TRILL are called RBridges (Routing 112 Bridges) or TRILL Switches. 114 This document, in conjunction with [RFC6165], specifies the data 115 formats and code points for the IS-IS [ISO-10589] [RFC1195] 116 extensions to support TRILL. These data formats and code points may 117 also be used by technologies other than TRILL. 119 This document obsoletes [RFC6326], which generally corresponded to 120 the base TRILL protocol as the TRILL Working Group passed it up to 121 the IESG in 2009. There has been substantial development of TRILL 122 since them. The main changes from [RFC6326] are summarized below and 123 a full list is given in Section 7. 125 1. Addition of multicast group announcements by IPv4 and IPv6 126 address. 128 2. Addition of facilities for announcing capabilities supported. 130 3. Addition of a tree affinity sub-TLV whereby ISs can request 131 distribution tree association. 133 4. Addition of multi-topology support. 135 5. Addition of control plane support for TRILL Data frame fine- 136 grained labels. This support is independent of the data plane 137 representation. 139 6. Fix the reported errata [Err2869] in [RFC6326]. 141 Changes herein to TLVs and sub-TLVs specified in [RFC6326] are 142 backwards compatible. 144 1.1 Conventions Used in This Document 146 The terminology and acronyms defined in [RFC6325] are used herein 147 with the same meaning. 149 Additional acronyms and phrases used in this document are: 151 BVL - Bit Vector Length 153 BVO - Bit Vector Offset 155 IIH - IS-IS Hello 157 IS - Intermediate System. For this document, all relevant 158 intermediate systems are RBridges [RFC6325]. 160 NLPID - Network Layer Protocol Identifier 162 SNPA - SubNetwork Point of Attachment (MAC Address) 164 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 165 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 166 document are to be interpreted as described in [RFC2119]. 168 2. TLV and Sub-TLV Extensions to IS-IS for TRILL 170 This section, in conjunction with [RFC6165], specifies the data 171 formats and code points for the TLVs and sub-TLVs for IS-IS to 172 support the IETF TRILL protocol. Information as to the number of 173 occurrences allowed, such as for a TLV in a PDU or set of PDUs or for 174 a sub-TLV in a TLV, is summarized in Section 5. 176 2.1 Group Address TLV 178 The Group Address (GADDR) TLV, IS-IS TLV type 142, is carried in an 179 LSP PDU and carries sub-TLVs that in turn advertise multicast group 180 listeners. The sub-TLVs that advertises listeners are specified 181 below. The sub-TLVs under GADDR constitute a new series of sub-TLV 182 types (see Section 5.2). 184 GADDR has the following format: 186 +-+-+-+-+-+-+-+-+ 187 |Type=GADDR-TLV | (1 byte) 188 +-+-+-+-+-+-+-+-+ 189 | Length | (1 byte) 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-... 191 | sub-TLVs... 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-... 194 o Type: TLV Type, set to GADDR-TLV 142. 196 o Length: variable depending on the sub-TLVs carried. 198 o sub-TLVs: The Group Address TLV value consists of sub-TLVs 199 formatted as described in [RFC5305]. 201 2.1.1 Group MAC Address Sub-TLV 203 The Group MAC Address (GMAC-ADDR) sub-TLV is sub-TLV type number 1 204 within the GADDR TLV. In TRILL, it is used to advertise multicast 205 listeners by MAC address as specified in Section 4.5.5 of [RFC6325]. 206 It has the following format: 208 +-+-+-+-+-+-+-+-+ 209 |Type=GMAC-ADDR | (1 byte) 210 +-+-+-+-+-+-+-+-+ 211 | Length | (1 byte) 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | RESV | Topology-ID | (2 bytes) 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | RESV | VLAN ID | (2 bytes) 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 |Num Group Recs | (1 byte) 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 | GROUP RECORDS (1) | 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | GROUP RECORDS (2) | 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 | ................. | 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 | GROUP RECORDS (N) | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 where each group record is of the following form with k=6: 230 +-+-+-+-+-+-+-+-+ 231 | Num of Sources| (1 byte) 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | Group Address (k bytes) | 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 | Source 1 Address (k bytes) | 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | Source 2 Address (k bytes) | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 | ..... | 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 241 | Source M Address (k bytes) | 242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 244 o Type: GADDR sub-TLV type, set to 1 (GMAC-ADDR). 246 o Length: 5 + m + k*n = 5 + m + 6*n where m is the number of group 247 records and n is the sum of the number of group and source 248 addresses. 250 o RESV: Reserved. 4-bit fields that MUST be sent as zero and 251 ignored on receipt. 253 o Topology-ID: This field carries a topology ID [RFC5120] or zero if 254 topologies are not in use. 256 o VLAN ID: This carries the 12-bit VLAN identifier for all 257 subsequent MAC addresses in this sub-TLV, or the value zero if no 258 VLAN is specified. 260 o Number of Group Records: A 1-byte unsigned integer that is the 261 number of group records in this sub-TLV. 263 o Group Record: Each group record carries the number of sources. If 264 this field is zero, it indicates a listener for (*,G), that is, a 265 listener not restricted by source. It then has a 6-byte (48-bit) 266 multicast MAC address followed by 6-byte source MAC addresses. If 267 the sources do not fit in a single sub-TLV, the same group address 268 may be repeated with different source addresses in another sub-TLV 269 of another instance of the Group Address TLV. 271 The GMAC-ADDR sub-TLV is carried only within a GADDR TLV. 273 2.1.2 Group IPv4 Address Sub-TLV 275 The Group IPv4 Address (GIP-ADDR) sub-TLV is IS-IS sub-TLV type TBDa 276 [2 suggested] within the GADDR TLV. It has the same format as the 277 Group MAC Address sub-TLV described in Section 2.1.1 except that k=4. 278 The fields are as follows: 280 o Type: sub-TLV Type, set to TBDa [2 suggested] (GIP-ADDR). 282 o Length: 5 + m + k*n = 5 + m + 4*n where m is the number of group 283 records and n is the sum of the number of group and source 284 addresses. 286 o Topology-Id: This field carries a topology ID [RFC5120] or zero if 287 topologies are not in use. 289 o RESV: Must be sent as zero on transmission and is ignored on 290 receipt. 292 o VLAN-ID: This carries a 12-bit VLAN identifier that is valid for 293 all subsequent addresses in this sub-TLV, or the value zero if no 294 VLAN is specified. 296 o Number of Group Records: This is of length 1 byte and lists the 297 number of group records in this sub-TLV. 299 o Group Record: Each group record carries the number of sources. If 300 this field is zero, it indicates a listener for (*,G), that is, a 301 listener not restricted by source. It then has a 4-byte (32-bit) 302 IPv4 Group Address followed by 4-byte source IPv4 addresses. If 303 the number of sources do not fit in a single sub-TLV, it is 304 permitted to have the same group address repeated with different 305 source addresses in another sub-TLV of another instance of the 306 Group Address TLV. 308 The GIP-ADDR sub-TLV is carried only within a GADDR TLV. 310 2.1.3 Group IPv6 Address Sub-TLV 312 The Group IPv6 Address (GIPV6-ADDR) sub-TLV is IS-IS sub-TLV type 313 TBDb [3 suggested] within the GADDR TLV. It has the same format as 314 the Group MAC Address sub-TLV described in Section 2.1.1 except that 315 k=16. The fields are as follows: 317 o Type: sub-TLV Type, set to TBDb [3 suggested] (GIPV6-ADDR). 319 o Length: 5 + m + k*n = 5 + m + 16*n where m is the number of group 320 records and n is the sum of the number of group and source 321 addresses. 323 o Topology-Id: This field carries a topology ID [RFC5120] or zero if 324 topologies are not in use. 326 o RESV: Must be sent as zero on transmission and is ignored on 327 receipt. 329 o VLAN-ID: This carries a 12-bit VLAN identifier that is valid for 330 all subsequent addresses in this sub-TLV, or the value zero if no 331 VLAN is specified. 333 o Number of Group Records: This is of length 1 byte and lists the 334 number of group records in this sub-TLV. 336 o Group Record: Each group record carries the number of sources. If 337 this field is zero, it indicates a listener for (*,G), that is, a 338 listener not restricted by source. It then has a 16-byte (128-bit) 339 IPv6 Group Address followed by 16-byte source IPv6 addresses. If 340 the number of sources do not fit in a single sub-TLV, it is 341 permitted to have the same group address repeated with different 342 source addresses in another sub-TLV of another instance of the 343 Group Address TLV. 345 The GIPV6-ADDR sub-TLV is carried only within a GADDR TLV. 347 2.1.4 Group Labeled MAC Address Sub-TLV 349 The GMAC-ADDR sub-TLV of the Group Address (GADDR) TLV specified in 350 Section 2.1.1 provides for a VLAN-ID. The Group Labeled MAC Address 351 sub-TLV, below, extends this to a fine-grained label. 353 +-+-+-+-+-+-+-+-+ 354 |Type=GLMAC-ADDR| (1 byte) 355 +-+-+-+-+-+-+-+-+ 356 | Length | (1 byte) 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 | RESV | Topology-ID | (2 bytes) 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 360 | Fine-Grained Label | (3 bytes) 361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 362 |Num Group Recs | (1 byte) 363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 364 | GROUP RECORDS (1) | 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 366 | GROUP RECORDS (2) | 367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 | ................. | 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 370 | GROUP RECORDS (N) | 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 373 where each group record is of the following form with k=6: 375 +-+-+-+-+-+-+-+-+ 376 | Num of Sources| (1 byte) 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 | Group Address (k bytes) | 379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 | Source 1 Address (k bytes) | 381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 382 | Source 2 Address (k bytes) | 383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 384 | ..... | 385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 386 | Source M Address (k bytes) | 387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 389 o Type: GADDR sub-TLV Type, set to TBDc [4 suggested] (GLMAC-ADDR). 391 o Length: 6 + m + k*n = 6 + m + 6*n where m is the number of group 392 records and n is the sum of the number of group and source 393 addresses. 395 o RESV: Reserved. 4-bit field that MUST be sent as zero and ignored 396 on receipt. 398 o Topology-ID: This field carries a topology ID [RFC5120] or zero if 399 topologies are not in use. 401 o Label: This carries the fine-grained label [RFCfgl] identifier for 402 all subsequent MAC addresses in this sub-TLV, or the value zero if 403 no label is specified. 405 o Number of Group Records: A 1-byte unsigned integer that is the 406 number of group records in this sub-TLV. 408 o Group Record: Each group record carries the number of sources. If 409 this field is zero, it indicates a listener for (*,G), that is, a 410 listener not restricted by source. It then has a 6-byte (48-bit) 411 multicast address followed by 6-byte source MAC addresses. If the 412 sources do not fit in a single sub-TLV, the same group address may 413 be repeated with different source addresses in another sub-TLV of 414 another instance of the Group Address TLV. 416 The GLMAC-ADDR sub-TLV is carried only within a GADDR TLV. 418 2.1.5 Group Labeled IPv4 Address Sub-TLV 420 The Group Labeled IPv4 Address (GLIP-ADDR) sub-TLV is IS-IS sub-TLV 421 type TBDd [5 suggested] within the GADDR TLV. It has the same format 422 as the Group Labeled MAC Address sub-TLV described in Section 2.1.4 423 except that k=4. The fields are as follows: 425 o Type: sub-TLV Type, set to TBDd [5 suggested] (GLIP-ADDR). 427 o Length: 6 + m + k*n = 6 + m + 4*n where m is the number of group 428 records and n is the sum of the number of group and source 429 addresses. 431 o Topology-Id: This field carries a topology ID [RFC5120] or zero if 432 topologies are not in use. 434 o RESV: Must be sent as zero on transmission and is ignored on 435 receipt. 437 o Label: This carries the fine-grained label [RFCfgl] identifier for 438 all subsequent IPv4 addresses in this sub-TLV, or the value zero 439 if no label is specified. 441 o Number of Group Records: This is of length 1 byte and lists the 442 number of group records in this sub-TLV. 444 o Group Record: Each group record carries the number of sources. If 445 this field is zero, it indicates a listener for (*,G), that is, a 446 listener not restricted by source. It then has a 4-byte (32-bit) 447 IPv4 Group Address followed by 4-byte source IPv4 addresses. If 448 the number of sources do not fit in a single sub-TLV, it is 449 permitted to have the same group address repeated with different 450 source addresses in another sub-TLV of another instance of the 451 Group Address TLV. 453 The GLIP-ADDR sub-TLV is carried only within a GADDR TLV. 455 2.1.6 Group Labeled IPv6 Address Sub-TLV 457 The Group Labeled IPv6 Address (GLIPV6-ADDR) sub-TLV is IS-IS sub-TLV 458 type TBDe [6 suggested] within the GADDR TLV. It has the same format 459 as the Group Labeled MAC Address sub-TLV described in Section 2.1.4 460 except that k=16. The fields are as follows: 462 o Type: sub-TLV Type, set to TBDe [6 suggested] (GLIPV6-ADDR). 464 o Length: 6 + m + k*n = 6 + m + 16*n where m is the number of group 465 records and n is the sum of the number of group and source 466 addresses. 468 o Topology-Id: This field carries a topology ID [RFC5120] or zero if 469 topologies are not in use. 471 o RESV: Must be sent as zero on transmission and is ignored on 472 receipt. 474 o Label: This carries the fine-grained label [RFCfgl] identifier for 475 all subsequent IPv6 addresses in this sub-TLV, or the value zero 476 if no label is specified. 478 o Number of Group Records: This of length 1 byte and lists the 479 number of group records in this sub-TLV. 481 o Group Record: Each group record carries the number of sources. If 482 this field is zero, it indicates a listener for (*,G), that is, a 483 listener not restricted by source. It then has a 16-byte (128-bit) 484 IPv6 Group Address followed by 16-byte source IPv6 addresses. If 485 the number of sources do not fit in a single sub-TLV, it is 486 permitted to have the same group address repeated with different 487 source addresses in another sub-TLV of another instance of the 488 Group Address TLV. 490 The GLIPV6-ADDR sub-TLV is carried only within a GADDR TLV. 492 2.2 Multi-Topology-Aware Port Capability Sub-TLVs 494 TRILL makes use of the Multi-Topology-Aware Port Capability (MT-PORT- 495 CAP) TLV as specified in [RFC6165]. The following subsections of 496 this Section 2.2 specify the sub-TLVs transported by the MT-PORT-CAP 497 TLV for TRILL. 499 2.2.1 Special VLANs and Flags Sub-TLV 501 In TRILL, a Special VLANs and Flags (VLAN-Flags) sub-TLV is carried 502 in every IIH PDU. It has the following format: 504 +--+--+--+--+--+--+--+--+ 505 | Type | (1 byte) 506 +--+--+--+--+--+--+--+--+ 507 | Length | (1 byte) 508 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 509 | Port ID | (2 bytes) 510 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 511 | Sender Nickname | (2 bytes) 512 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 513 |AF|AC|VM|BY| Outer.VLAN | (2 bytes) 514 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 515 |TR|R |R |R | Designated-VLAN | (2 bytes) 516 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 518 o Type: sub-TLV type, set to MT-PORT-CAP VLAN-FLAGs sub-TLV 1. 520 o Length: 8. 522 o Port ID: An ID for the port on which the enclosing TRILL IIH 523 PDU is being sent as specified in [RFC6325], Section 4.4.2. 525 o Sender Nickname: If the sending IS is holding any nicknames as 526 discussed in [RFC6325], Section 3.7, one MUST be included here. 527 Otherwise, the field is set to zero. This field is to support 528 intelligent end stations that determine the egress IS (RBridge) 529 for unicast data through a directory service or the like and 530 that need a nickname for their first hop to insert as the 531 ingress nickname to correctly format a TRILL Data frame (see 532 [RFC6325], Section 4.6.2, point 8). It is also referenced in 533 connection with the VLANs Appointed Sub-TLV (see Section 2.2.5) 534 and can be used as the egress on one-hop RBridge Channel 535 messages [Channel], for example those use for BFD over TRILL 536 [RFCtrillBFD]. 538 o Outer.VLAN: A copy of the 12-bit outer VLAN ID of the TRILL IIH 539 frame containing this sub-TLV, as specified in [RFC6325], 540 Section 4.4.5. 542 o Designated-VLAN: The 12-bit ID of the Designated VLAN for the 543 link, as specified in [RFC6325], Section 4.2.4.2. 545 o AF, AC, VM, BY, and TR: These flag bits have the following 546 meanings when set to one, as specified in the listed section of 547 [RFC6325]: 549 RFC 6325 550 Bit Section Meaning if bit is one 551 -------------------------------------- 553 AF 4.4.2 Originating IS believes it is appointed 554 forwarder for the VLAN and port on which the 555 containing IIH PDU was sent. 557 AC 4.9.1 Originating port configured as an access port 558 (TRILL traffic disabled). 560 VM 4.4.5 VLAN mapping detected on this link. 562 BY 4.4.2 Bypass pseudonode. 564 TR 4.9.1 Originating port configured as a trunk port 565 (end-station service disabled). 567 o R: Reserved bit. MUST be sent as zero and ignored on receipt. 569 2.2.2 Enabled-VLANs Sub-TLV 571 The optional Enabled-VLANs sub-TLV specifies the VLANs enabled at the 572 port of the originating IS on which the containing Hello was sent, as 573 specified in [RFC6325], Section 4.4.2. It has the following format: 575 +-+-+-+-+-+-+-+-+ 576 | Type | (1 byte) 577 +-+-+-+-+-+-+-+-+ 578 | Length | (1 byte) 579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 580 | RESV | Start VLAN ID | (2 bytes) 581 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 582 | VLAN bit-map.... 583 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 585 o Type: sub-TLV type, set to MT-PORT-CAP Enabled-VLANs sub-TLV 2. 587 o Length: Variable, minimum 3. 589 o RESV: 4 reserved bits that MUST be sent as zero and ignored on 590 receipt. 592 o Start VLAN ID: The 12-bit VLAN ID that is represented by the high 593 order bit of the first byte of the VLAN bit-map. 595 o VLAN bit-map: The highest order bit indicates the VLAN equal to 596 the start VLAN ID, the next highest bit indicates the VLAN equal 597 to start VLAN ID + 1, continuing to the end of the VLAN bit-map 598 field. 600 If this sub-TLV occurs more than once in a Hello, the set of enabled 601 VLANs is the union of the sets of VLANs indicated by each of the 602 Enabled-VLAN sub-TLVs in the Hello. 604 2.2.3 Appointed Forwarders Sub-TLV 606 The DRB on a link uses the Appointed Forwarders sub-TLV to inform 607 other ISs on the link that they are the designated VLAN-x forwarder 608 for one or more ranges of VLAN IDs as specified in [RFC6439]. It has 609 the following format: 611 +-+-+-+-+-+-+-+-+ 612 | Type | (1 byte) 613 +-+-+-+-+-+-+-+-+ 614 | Length | (1 byte) 615 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 616 | Appointment Information (1) | (6 bytes) 617 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 618 | Appointment Information (2) | (6 bytes) 619 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 620 | ................. | 621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 622 | Appointment Information (N) | (6 bytes) 623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 625 where each appointment is of the form: 627 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 628 | Appointee Nickname | (2 bytes) 629 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 630 | RESV | Start.VLAN | (2 bytes) 631 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 632 | RESV | End.VLAN | (2 bytes) 633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 635 o Type: sub-TLV type, set to MT-PORT-CAP AppointedFwrdrs sub-TLV 3. 637 o Length: 6*n bytes, where there are n appointments. 639 o Appointee Nickname: The nickname of the IS being appointed a 640 forwarder. 642 o RESV: 4 bits that MUST be sent as zero and ignored on receipt. 644 o Start.VLAN, End.VLAN: These fields are the VLAN IDs of the 645 appointment range, inclusive. To specify a single VLAN, the VLAN's 646 ID appears as both the start and end VLAN. As specified in 647 [RFC6439], appointing an IS forwarder on a port for a VLAN not 648 enabled on that port has no effect. If the range specified is or 649 includes the value 0x000 or 0xFFF, such values are ignored as they 650 are not valid VLAN numbers and a port cannot be enabled for them. 652 An IS's nickname may occur as appointed forwarder for multiple VLAN 653 ranges by occurrences of this sub-TLV within the same or different MT 654 Port Capability TLVs within an IIH PDU. See [RFC6439]. 656 2.2.4 Port TRILL Version Sub-TLV 658 The Port TRILL Version (PORT-TRILL-VER) sub-TLV indicates the maximum 659 version of the TRILL standard supported and the support of optional 660 hop-by-hop capabilities. By implication, lower versions are also 661 supported. If this sub-TLV is missing from an IIH, it is assumed that 662 the originating IS only supports the base version (version zero) of 663 the protocol [RFC6325] and supports no optional capabilities 664 indicated by this sub-TLV. 666 +-+-+-+-+-+-+-+-+ 667 | Type | (1 byte) 668 +-+-+-+-+-+-+-+-+ 669 | Length | (1 byte) 670 +-+-+-+-+-+-+-+-+ 671 | Max-version | (1 byte) 672 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+ 673 | Capabilities and Header Flags Supported | (4 bytes) 674 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+ 675 0 1 3 676 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 0 1 678 o Type: MT-PORT-CAP sub-TLV type, set to TBDf [7 suggested] (PORT- 679 TRILL-VER). 681 o Length: 5. 683 o Max-version: A one byte unsigned integer set to maximum version 684 supported. 686 o Capabilities and Header Flags Supported: A bit vector of 32 bits 687 numbered 0 through 31 in network order. Bits 3 through 13 indicate 688 that the corresponding TRILL Header hop-by-hop extended flags 689 [ExtendHeader] are supported. Bits 0 through 2 and 14 to 31 are 690 reserved to indicate support of optional capabilities. A one bit 691 indicates that the flag or capability is supported by the sending 692 IS. Bits in this field MUST be set to zero except as permitted for 693 a capability being advertised or if a hop-by-hop extended header 694 flag is supported. 696 This sub-TLV, if present, MUST occur in an MT-PORT-CAP TLV in a TRILL 697 IIH. If there is more than one occurrence, the minimum of the 698 supported versions is assumed to be correct and a capability or 699 header flag is assumed to be supported only if indicated by all 700 occurrences. The flags and capabilities for which support can be 701 indicated in this sub-TLV are disjoint from those in the TRILL-VER 702 sub-TLV (Section 2.3.1) so they cannot conflict. The flags and 703 capabilities indicated in this sub-TLV relate to hop-by-hop 704 processing that can differ between the ports of an IS (RBridge), and 705 thus must be advertised in IIHs. For example, a capability requiring 706 cryptographic hardware assist might be supported on some ports and 707 not others. However, the TRILL version is the same as that in the 708 PORT-TRILL-VER sub-TLV. An IS, if it is adjacent to the sending IS of 709 TRILL version sub-TLV(s) uses the TRILL version it received in PORT- 710 TRILL-VER sub-TLV(s) in preference to that received in TRILL-VER sub- 711 TLV(s). 713 2.2.5 VLANs Appointed Sub-TLV 715 The optional VLANs sub-TLV specifies, for the port of the originating 716 IS on which the containing Hello was sent, the VLANs for which it is 717 appointed forwarder. This sub-TLV has the following format: 719 +-+-+-+-+-+-+-+-+ 720 | Type | (1 byte) 721 +-+-+-+-+-+-+-+-+ 722 | Length | (1 byte) 723 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 724 | RESV | Start VLAN ID | (2 bytes) 725 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 726 | VLAN bit-map.... 727 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 729 o Type: sub-TLV type, set to MT-PORT-CAP VLANS-Appointed sub-TLV 730 TBDg [8 suggested]. 732 o Length: Variable, minimum 3. 734 o RESV: 4 reserved bits that MUST be sent as zero and ignored on 735 receipt. 737 o Start VLAN ID: The 12-bit VLAN ID that is represented by the high 738 order bit of the first byte of the VLAN bit-map. 740 o VLAN bit-map: The highest order bit indicates the VLAN equal to 741 the start VLAN ID, the next highest bit indicates the VLAN equal 742 to start VLAN ID + 1, continuing to the end of the VLAN bit-map 743 field. 745 If this sub-TLV occurs more than once in a Hello, the originating IS 746 is declaring that it believes itself to be appointed forwarder on the 747 port on which the enclosing IIH was sent for the union of the sets of 748 VLANs indicated by each of the VLANs-Appointed sub-TLVs in the Hello. 750 2.3 Sub-TLVs of the Router and MT Capability TLVs 752 The Router Capability TLV is specified in [RFC4971] and the MT 753 Capability TLV in [RFC6329]. All of the sub-sections of this Section 754 2.3 below specify sub-TLVs that can be carried in the Router 755 Capability TLV (#242) and the MT (multi-topology) Capability TLV 756 (#144) with the same sub-TLV number for both TLVs. These TLVs are in 757 turn carried only by LSPs. 759 2.3.1 TRILL Version Sub-TLV 761 The TRILL Version (TRILL-VER) sub-TLV indicates the maximum version 762 of the TRILL standard supported and the support of optional 763 capabilities by the originating IS. By implication, lower versions 764 are also supported. If this sub-TLV is missing, it is assumed that 765 the originating IS only supports the base version (version zero) of 766 the protocol [RFC6325] and no optional capabilities indicated by this 767 sub-TLV are supported. 769 +-+-+-+-+-+-+-+-+ 770 | Type | (1 byte) 771 +-+-+-+-+-+-+-+-+ 772 | Length | (1 byte) 773 +-+-+-+-+-+-+-+-+ 774 | Max-version | (1 byte) 775 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+ 776 | Capabilities and Header Flags Supported | (4 bytes) 777 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+ 778 0 1 3 779 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 0 1 781 o Type: Router Capability sub-TLV type, set to 13 (TRILL-VER). 783 o Length: 5. 785 o Max-version: A one byte unsigned integer set to maximum version 786 supported. 788 o Capabilities and Header Flags Supported: A bit vector of 32 bits 789 numbered 0 through 31 in network order. Bits 14 through 31 790 indicate that the corresponding TRILL Header extended flags 791 [ExtendHeader] are supported. Bits 0 through 13 are reserved to 792 indicate support of optional capabilities. A one bit indicates 793 that the originating IS supports the flag or capability. For 794 example, support of multi-level TRILL IS-IS [MultiLevel]. Bits in 795 this field MUST be set to zero except as permitted for a 796 capability being advertised or an extended header flag supported. 798 This sub-TLV, if present in a Router Capabilities TLV, MUST occur in 799 the LSP number zero for the originating IS. If found in a Router 800 Capabilities TLV in other fragments, it is ignored. If there is more 801 than one occurrence in LSP number zero, the minimum of the supported 802 versions is assumed to be correct and an extended header flag or 803 capability is assumed to be supported only if indicated by all 804 occurrences. The flags and capabilities supported bits in this sub- 805 TLV are disjoint from those in the PORT-TRILL-VER sub-TLV (Section 806 2.2.4) so they cannot conflict. However, the TRILL version is the 807 same as that in the PORT-TRILL-VER sub-TLV and an IS that is adjacent 808 to the originating IS of TRILL-VER sub-TLV(s) uses the TRILL version 809 it received in PORT-TRILL-VER sub-TLV(s) in preference to that 810 received in TRILL-VER sub-TLV(s). 812 For multi-topology aware TRILL switches, the TRILL version and 813 capabilities announced for the base topology are assumed to apply to 814 all topologies for which a separate TRILL version announcement does 815 not occur in an MT Capabilities TLV. Such announcements for non-zero 816 topologies need not occur in fragment zero. 818 2.3.2 Nickname Sub-TLV 820 The Nickname (NICKNAME) Router Capability sub-TLV carries information 821 about the nicknames of the originating IS, along with information 822 about its priority to hold those nicknames and the priority for each 823 nickname to be a tree root as specified in [RFC6325] Section 3.7.3. 824 Multiple instances of this sub-TLV may occur. 826 +-+-+-+-+-+-+-+-+ 827 |Type = NICKNAME| (1 byte) 828 +-+-+-+-+-+-+-+-+ 829 | Length | (1 byte) 830 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 831 | NICKNAME RECORDS (1) | 832 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 833 | NICKNAME RECORDS (2) | 834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 835 | ................. | 836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 837 | NICKNAME RECORDS (N) | 838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 840 where each nickname record is of the form: 842 +-+-+-+-+-+-+-+-+ 843 | Nickname.Pri | (1 byte) 844 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 845 | Tree Root Priority | (2 byte) 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 | Nickname | (2 bytes) 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 850 o Type: Router and MT Capability sub-TLV type, set to 6 (NICKNAME). 852 o Length: 5*n, where n is the number of nickname records present. 854 o Nickname.Pri: An 8-bit unsigned integer priority to hold a 855 nickname as specified in Section 3.7.3 of [RFC6325]. 857 o Tree Root Priority: This is an unsigned 16-bit integer priority to 858 be a tree root as specified in Section 4.5 of [RFC6325]. 860 o Nickname: This is an unsigned 16-bit integer as specified in 861 Section 3.7 of [RFC6325]. 863 2.3.3 Trees Sub-TLV 865 Each IS providing TRILL service uses the TREES sub-TLV to announce 866 three numbers related to the computation of distribution trees as 867 specified in Section 4.5 of [RFC6325]. Its format is as follows: 869 +-+-+-+-+-+-+-+-+ 870 |Type = TREES | (1 byte) 871 +-+-+-+-+-+-+-+-+ 872 | Length | (1 byte) 873 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 874 | Number of trees to compute | (2 byte) 875 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 876 | Maximum trees able to compute | (2 byte) 877 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 878 | Number of trees to use | (2 byte) 879 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 881 o Type: Router and MT Capability sub-TLV type, set to 7 (TREES). 883 o Length: 6. 885 o Number of trees to compute: An unsigned 16-bit integer as 886 specified in Section 4.5 of [RFC6325]. 888 o Maximum trees able to compute: An unsigned 16-bit integer as 889 specified in Section 4.5 of [RFC6325]. 891 o Number of trees to use: An unsigned 16-bit integer as specified in 892 Section 4.5 of [RFC6325]. 894 2.3.4 Tree Identifiers Sub-TLV 896 The tree identifiers (TREE-RT-IDs) sub-TLV is an ordered list of 897 nicknames. When originated by the IS that has the highest priority to 898 be a tree root, it lists the distribution trees that the other ISs 899 are required to compute as specified in Section 4.5 of [RFC6325]. If 900 this information is spread across multiple sub-TLVs, the starting 901 tree number is used to allow the ordered lists to be correctly 902 concatenated. The sub-TLV format is as follows: 904 +-+-+-+-+-+-+-+-+ 905 |Type=TREE-RT-IDs| (1 byte) 906 +-+-+-+-+-+-+-+-+ 907 | Length | (1 byte) 908 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 909 |Starting Tree Number | (2 bytes) 910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 911 | Nickname (K-th root) | (2 bytes) 912 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 913 | Nickname (K+1 - th root) | (2 bytes) 914 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 915 | Nickname (...) | 916 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 918 o Type: Router and MT Capability sub-TLV type, set to 8 (TREE-RT- 919 IDs). 921 o Length: 2 + 2*n, where n is the number of nicknames listed. 923 o Starting Tree Number: This identifies the starting tree number of 924 the nicknames that are trees for the domain. This is set to 1 for 925 the sub-TLV containing the first list. Other Tree-Identifiers sub- 926 TLVs will have the number of the starting list they contain. In 927 the event the same tree identifier can be computed from two such 928 sub-TLVs and they are different, then it is assumed that this is a 929 transient condition that will get cleared. During this transient 930 time, such a tree SHOULD NOT be computed unless such computation 931 is indicated by all relevant sub-TLVs present. 933 o Nickname: The nickname at which a distribution tree is rooted. 935 2.3.5 Trees Used Identifiers Sub-TLV 937 This Router Capability sub-TLV has the same structure as the Tree 938 Identifiers sub-TLV specified in Section 2.3.4. The only difference 939 is that its sub-TLV type is set to 9 (TREE-USE-IDs), and the trees 940 listed are those that the originating IS wishes to use as specified 941 in [RFC6325], Section 4.5. 943 2.3.6 Interested VLANs and Spanning Tree Roots Sub-TLV 945 The value of this sub-TLV consists of a VLAN range and information in 946 common to all of the VLANs in the range for the originating IS. This 947 information consists of flags, a variable length list of spanning 948 tree root bridge IDs, and an appointed forwarder status lost counter, 949 all as specified in the sections of [RFC6325] listed with the 950 respective information items below. 952 In the set of LSPs originated by an IS, the union of the VLAN ranges 953 in all occurrences of this sub-TLV MUST be the set of VLANs for which 954 the originating IS is appointed forwarder on at least one port, and 955 the VLAN ranges in multiple VLANs sub-TLVs for an IS MUST NOT overlap 956 unless the information provided about a VLAN is the same in every 957 instance. However, as a transient state these conditions may be 958 violated. If a VLAN is not listed in any INT-VLAN sub-TLV for an IS, 959 that IS is assumed to be uninterested in receiving traffic for that 960 VLAN. If a VLAN appears in more than one INT-VLAN sub-TLV for an IS 961 with different information in the different instances, the following 962 apply: 964 - If those sub-TLVs provide different nicknames, it is unspecified 965 which nickname takes precedence. 966 - The largest appointed forwarder status lost counter, using serial 967 number arithmetic [RFC1982], is used. 968 - The originating IS is assumed to be attached to a multicast IPv4 969 router for that VLAN if any of the INT-VLAN sub-TLVs assert that 970 it is so connected and similarly for IPv6 multicast router 971 attachment. 972 - The root bridge lists from all of the instances of the VLAN for 973 the originating IS are merged. 975 To minimize such occurrences, wherever possible, an implementation 976 SHOULD advertise the update to an interested VLAN and Spanning Tree 977 Roots sub-TLV in the same LSP fragment as the advertisement that it 978 replaces. Where this is not possible, the two affected LSP fragments 979 should be flooded as an atomic action. An IS that receives an update 980 to an existing interested VLAN and Spanning Tree Roots sub-TLV can 981 minimize the potential disruption associated with the update by 982 employing a hold-down timer prior to processing the update so as to 983 allow for the receipt of multiple LSP fragments associated with the 984 same update prior to beginning processing. 986 The sub-TLV layout is as follows: 988 +-+-+-+-+-+-+-+-+ 989 |Type = INT-VLAN| (1 byte) 990 +-+-+-+-+-+-+-+-+ 991 | Length | (1 byte) 992 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 993 | Nickname | (2 bytes) 994 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+ 995 | Interested VLANS | (4 bytes) 996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+ 997 | Appointed Forwarder Status Lost Counter | (4 bytes) 998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+ 999 | Root Bridges | (6*n bytes) 1000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+ 1002 o Type: Router and MT Capability sub-TLV type, set to 10 (INT-VLAN). 1004 o Length: 10 + 6*n, where n is the number of root bridge IDs. 1006 o Nickname: As specified in [RFC6325], Section 4.2.4.4, this field 1007 may be used to associate a nickname held by the originating IS 1008 with the VLAN range indicated. When not used in this way, it is 1009 set to zero. 1011 o Interested VLANS: The Interested VLANs field is formatted as shown 1012 below. 1014 0 1 2 3 4 - 15 16 - 19 20 - 31 1015 +----+----+----+----+------------+----------+------------+ 1016 | M4 | M6 | R | R | VLAN.start | RESV | VLAN.end | 1017 +----+----+----+----+------------+----------+------------+ 1019 - M4, M6: These bits indicate, respectively, that there is an 1020 IPv4 or IPv6 multicast router on a link for which the 1021 originating IS is appointed forwarder for every VLAN in the 1022 indicated range as specified in [RFC6325], Section 4.2.4.4, 1023 item 5.1. 1025 - R, RESV: These reserved bits MUST be sent as zero and are 1026 ignored on receipt. 1028 - VLAN.start and VLAN.end: This VLAN ID range is inclusive. 1029 Setting both VLAN.start and VLAN.end to the same value 1030 indicates a range of one VLAN ID. If VLAN.start is not equal to 1031 VLAN.end and VLAN.start is 0x000, the sub-TLV is interpreted as 1032 if VLAN.start was 0x001. If VLAN.start is not equal to VLAN.end 1033 and VLAN.end is 0xFFF, the sub-TVL is interpreted as if 1034 VLAN.end was 0xFFE. If VLAN.end is less than VLAN.start, the 1035 sub-TLV is ignored. If both VLAN.start and VLAN.end are 0x000 1036 or both are 0xFFF, the sub-TLV is ignored. 1038 o Appointed Forwarder Status Lost Counter: This is a count of how 1039 many times a port that was appointed forwarder for the VLANs in 1040 the range given has lost the status of being an appointed 1041 forwarder for some port as discussed in Section 4.8.3 of 1042 [RFC6325]. It is initialized to zero at an IS when the zeroth LSP 1043 sequence number is initialized. No special action need be taken at 1044 rollover; the counter just wraps around. 1046 o Root Bridges: The list of zero or more spanning tree root bridge 1047 IDs is the set of root bridge IDs seen for all ports for which the 1048 IS is appointed forwarder for the VLANs in the specified range as 1049 discussed in [RFC6325], Section 4.9.3.2. While, of course, at most 1050 one spanning tree root could be seen on any particular port, there 1051 may be multiple ports in the same VLANs connected to different 1052 bridged LANs with different spanning tree roots. 1054 An INT-VLAN sub-TLV asserts that the information provided (multicast 1055 router attachment, appointed forwarder status lost counter, and root 1056 bridges) is the same for all VLANs in the range specified. If this is 1057 not the case, the range MUST be split into subranges meeting this 1058 criteria. It is always safe to use sub-TLVs with a "range" of one 1059 VLAN ID, but this may be too verbose. 1061 2.3.7 VLAN Group Sub-TLV 1063 The VLAN Group sub-TLV consists of two or more VLAN IDs as specified 1064 in [RFC6325], Section 4.8.4. This sub-TLV indicates that shared VLAN 1065 learning is occurring at the originating IS between the listed VLANs. 1066 It is structured as follows: 1068 +-+-+-+-+-+-+-+-+ 1069 |Type=VLAN-GROUP| (1 byte) 1070 +-+-+-+-+-+-+-+-+ 1071 | Length | (1 byte) 1072 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1073 | RESV | Primary VLAN ID | (2 bytes) 1074 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1075 | RESV | Secondary VLAN ID | (2 bytes) 1076 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1077 | more Secondary VLAN IDs ... (2 bytes each) 1078 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1080 o Type: Router and MT Capability sub-TLV type, set to 14 (VLAN- 1081 GROUP). 1083 o Length: 4 + 2*n, where n is the number of secondary VLAN ID fields 1084 beyond the first. n MAY be zero. 1086 o RESV: a 4-bit field that MUST be sent as zero and ignored on 1087 receipt. 1089 o Primary VLAN ID: This identifies the primary VLAN ID. 1091 o Secondary VLAN ID: This identifies a secondary VLAN in the VLAN 1092 Group. 1094 o more Secondary VLAN IDs: zero or more byte pairs, each with the 1095 top 4 bits as a RESV field and the low 12 bits as a VLAN ID. 1097 2.3.8 Interested Labels and Spanning Tree Roots Sub-TLV 1099 An IS that can handle fine-grained labeling [RFCfgl] announces its 1100 fine-grained label connectivity and related information in the 1101 "Interested Labels and Bridge Spanning Tree Roots sub-TLV" (INT- 1102 LABEL) which is a variation of the "Interested VLANs and Spanning 1103 Tree Roots sub-TLV" (INT-VLAN) structured as below. 1105 +-+-+-+-+-+-+-+-+ 1106 |Type= INT-LABEL| (1 byte) 1107 +-+-+-+-+-+-+-+-+ 1108 | Length | (1 byte) 1109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1110 | Nickname | (2 bytes) 1111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+-+ 1112 | Interested Labels | (7 bytes) 1113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+-+ 1114 | Appointed Forwarder Status Lost Counter | (4 bytes) 1115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+ 1116 | Root Bridges | (6*n bytes) 1117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+ 1119 o Type: Router and MT Capability sub-TLV Type, set to TBDh [15 1120 suggested] (INT-LABEL). 1122 o Length: 11 + 6*n where n is the number of root bridge IDs. 1124 o Nickname: This field may be used to associate a nickname held by 1125 the originating IS with the Labels indicated. When not used in 1126 this way, it is set to zero. 1128 o Interested Labels: The Interested Labels field is seven bytes long 1129 and formatted as shown below. 1131 0 1 2 3 4 5 6 7 1132 +--+--+--+--+--+--+--+--+ 1133 |M4|M6|BM| R| R| R| R| R| . . 1134 +--+--+--+--+--+--+--+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1135 | Label.start - 24 bits | 1136 +--+--+--+--+--+--+--+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1137 | Label.end or Bit Map - 24 bits | 1138 +--+--+--+--+--+--+--+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1139 0 1 2 1140 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 1142 - M4, M6: These bits indicate, respectively, that there is an 1143 IPv4 or IPv6 multicast router on a link to which the 1144 originating IS is appointed forwarder for the VLAN 1145 corresponding to every label in the indicated range. 1147 - BM: If the BM (Bit Map) bit is zero, the last three bytes of 1148 the Interested Labels is a Label.end label number. If the BM 1149 bit is one, those bytes are a bit map as described below. 1151 - R: These reserved bits MUST be sent as zero and are ignored on 1152 receipt. 1154 - Label.start and Label.end: If the BM bit is zero: This fine- 1155 grained label [RFCfgl] ID range is inclusive. These fields are 1156 treated as unsigned integers. Setting them both to that same 1157 label ID value indicates a range of one label ID. If Label.end 1158 is less than Label.start, the sub-TLV is ignored. 1160 - Label.start and Bit Map: If the BM bit is one: The fine-grained 1161 labels that the IS is interested in are indicated by a 24-bit 1162 bit map. The interested labels are the Label.start number plus 1163 the bit number of each one bit in the bit map. So, if bit zero 1164 of the bit map is a one, the IS in interested in the label with 1165 value Label.start and if bit 23 of the bit map is a one, the IS 1166 is interested in the label with value Label.start+23. 1168 o Appointed Forwarder Status Lost Counter: This is a count of how 1169 many times a port that was appointed forwarder for a VLAN mapping 1170 to the fine-grained label in the range or bit map given has lost 1171 the status of being an appointed forwarder as discussed in Section 1172 4.8.3 of [RFC6325]. It is initialized to zero at an IS when the 1173 zeroth LSP sequence number is initialized. No special action need 1174 be taken at rollover; the counter just wraps around. 1176 o Root Bridges: The list of zero or more spanning tree root bridge 1177 IDs is the set of root bridge IDs seen for all ports for which the 1178 IS is appointed forwarder for a VLAN mapping to the fine-grained 1179 label in the specified range or bit map. (See [RFC6325], Section 1180 4.9.3.2.) While, of course, at most one spanning tree root could 1181 be seen on any particular port, there may be multiple relevant 1182 ports connected to different bridged LANs with different spanning 1183 tree roots. 1185 An INT-LABEL sub-TLV asserts that the information provided (multicast 1186 router attachment, appointed forwarder status lost counter, and root 1187 bridges) is the same for all labels specified. If this is not the 1188 case, the sub-TLV MUST be split into subranges and/or separate bit 1189 maps meeting this criteria. It is always safe to use sub-TLVs with a 1190 "range" of one VLAN ID, but this may be too verbose. 1192 2.3.9 RBridge Channel Protocols Sub-TLV 1194 An IS announces the RBridge Channel protocols [Channel] it supports 1195 through use of this sub-TLV. 1197 +-+-+-+-+-+-+-+-+ 1198 |Type=RBCHANNELS| (1 byte) 1199 +-+-+-+-+-+-+-+-+ 1200 | Length | (1 byte) 1201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+... 1202 | Zero or more bit vectors (variable) 1203 +-+-+-+-... 1205 o Type: Router and MT Capabilities RBridge Channel Protocols sub- 1206 TLV, set to TBDi [16 suggested] (RBCHANNELS). 1208 o Length: variable. 1210 o Bit Vectors: Zero or more byte-aligned bit vectors where a one bit 1211 indicates support of a particular RBridge Channel protocol. Each 1212 byte-aligned bit vector is formatted as follows: 1214 | 0 1 2 3 4 5 6 7| 8 9 10 11 12 13 14 15| 1215 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 1216 | Bit Vector Length | Bit Vector Offset | 1217 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 1218 | bits 1219 +--+--+--... 1221 The bit vector length (BVL) is a seven bit unsigned integer field 1222 giving the number of bytes of bit vector. The bit vector offset (BVO) 1223 is a nine bit unsigned integer field. 1225 The bits in each bit vector are numbered in network order, the high 1226 order bit of the first byte of bits being bit 0 + 8*BVO, the low 1227 order bit of that byte being 7 + 8*BVO, the high order bit of the 1228 second byte being 8 + 8*BVO, and so on for BVL bytes. An RBridge 1229 Channel protocols-supported bit vector MUST NOT extend beyond the end 1230 of the value in the sub-TLV in which it occurs. If it does, it is 1231 ignored. If multiple byte-aligned bit vectors are present in one such 1232 sub-TLV, their representations are contiguous, the BVL field for the 1233 next starting immediately after the last byte of bits for the 1234 previous bit vector. The one or more bit vectors present MUST exactly 1235 fill the sub-TLV value. If there are one or two bytes of value left 1236 over, they are ignored; if more than two, an attempt is made to parse 1237 them as one or more bit vectors. 1239 If different bit vectors overlap in the protocol number space they 1240 refer to and they have inconsistent bit values for a channel 1241 protocol, support for the protocol is assumed if any of these bit 1242 vectors has a 1 for that protocol. 1244 The absence of any occurrences of this sub-TLV in the LSP for an IS 1245 implies that that IS does not support the RBridge Channel facility. 1247 To avoid wasted space, trailing bit vector zero bytes SHOULD be 1248 eliminated by reducing BVL, any null bit vectors (ones with BVL equal 1249 to zero) eliminated, and generally the most compact encoding used. 1250 For example, support for channel protocols 1 and 32 could be encoded 1251 as 1253 BVL = 5 1254 BVO = 0 1255 0b01000000 1256 0b00000000 1257 0b00000000 1258 0b00000000 1259 0b10000000 1261 or as 1263 BVL = 1 1264 BVO = 0 1265 0b01000000 1266 BLV = 1 1267 BVO = 4 1268 0b1000000 1270 The first takes 7 bytes while the second takes only 6 and thus the 1271 second would be preferred. 1273 In multi-topology aware RBridges, RBridge channel protocols for which 1274 support is announced in the base topology are assumed to be supported 1275 in all topologies for which there is no separate RBridge channel 1276 protocol support announcement. 1278 2.3.10 Affinity Sub-TLV 1280 Association of an IS to a multi-destination distribution tree through 1281 a specific path is accomplished by using the tree Affinity sub-TLV. 1282 The announcement of an Affinity sub-TLV by RB1 with the nickname of 1283 RB2 as the first part of an Affinity Record in the sub-TLV value is a 1284 request by RB1 that all ISes in the campus connect RB2 as a child of 1285 RB1 when calculating any of the trees listed in that Affinity Record. 1286 Examples of use include [Affinity] and [Resilient]. 1288 The structure of the AFFINITY sub-TLV is shown below. 1290 +-+-+-+-+-+-+-+-+ 1291 | Type=AFFINITY | (1 byte) 1292 +-+-+-+-+-+-+-+-+ 1293 | Length | (1 byte) 1294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1295 | AFFINITY RECORD 1 | 1296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1297 | AFFINITY RECORD 2 | 1298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1299 | .......... 1300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1301 | AFFINITY RECORD N | 1302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1304 Where each AFFINITY RECORD is structured as follows: 1306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1307 | Nickname | (2 bytes) 1308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1309 |Affinity Flags | (1 byte) 1310 +-+-+-+-+-+-+-+-+ 1311 |Number of trees| (1 byte) 1312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1313 | Tree-num of 1st root | (2 bytes) 1314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1315 | Tree-num of 2nd root | (2 bytes) 1316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1317 | .......... | 1318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1319 | Tree-num of Nth root | (2 bytes) 1320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1322 o Type: Router and MT Capability sub-TLV type, set to TBDj [17 1323 suggested] (AFFINITY). 1325 o Length: 1 + size of all Affinity Records included, where an 1326 Affinity Record listing n tree roots is 3+2*n bytes long. 1328 o Nickname: 16-bit nickname of the IS whose associations to the 1329 multi-destination trees listed in the Affinity Record are through 1330 the originating IS. 1332 o Affinity Flags: 8 bits reserved for future needs to provide 1333 additional information about the affinity being announced. MUST be 1334 sent as zero and ignored on receipt. 1336 o Number of trees: A one byte unsigned integer giving the number of 1337 trees for which affinity is being announced by this Affinity 1338 Record. 1340 o Tree-num of roots: The tree numbers of the distribution trees this 1341 Affinity Record is announcing. 1343 There is no need for a field giving the number of Affinity Records as 1344 this can be determined by processing those records. 1346 2.3.11 Label Group Sub-TLV 1348 The Label Group sub-TLV consists of two or more fine-grained label 1349 [RFCfgl] IDs. This sub-TLV indicates that shared Label MAC address 1350 learning is occurring at the announcing IS between the listed Labels. 1351 It is structured as follows: 1353 +-+-+-+-+-+-+-+-+ 1354 |Typ=LABEL-GROUP| (1 byte) 1355 +-+-+-+-+-+-+-+-+ 1356 | Length | (1 byte) 1357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1358 | Primary Label ID | (3 bytes) 1359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1360 | Secondary Label ID | (3 bytes) 1361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1362 | more Secondary Label IDs ... (3 bytes each) 1363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1365 o Type: Router and MT Capability sub-TLV type, set to TBDk [18 1366 suggested] (LABEL-GROUP). 1368 o Length: 6 + 3*n, where n is the number of secondary VLAN ID fields 1369 beyond the first. n MAY be zero. 1371 o Primary Label ID: This identifies the primary Label ID. 1373 o Secondary Label ID: This identifies a secondary Label in the Label 1374 Group. 1376 o more Secondary Label IDs: zero or more byte triples, each with a 1377 Label ID. 1379 2.4 MTU Sub-TLV for Ext. Reachability and MT ISN TLVs 1381 The MTU sub-TLV is used to optionally announce the MTU of a link as 1382 specified in [RFC6325] Section 4.2.4.4. It occurs within the Extended 1383 Reachability (#22) and MT (multi-topology) ISN (Intermediate System 1384 Neighbors) (#222) TLVs. 1386 +-+-+-+-+-+-+-+-+ 1387 | Type = MTU | (1 byte) 1388 +-+-+-+-+-+-+-+-+ 1389 | Length | (1 byte) 1390 +-+-+-+-+-+-+-+-+ 1391 |F| RESV | (1 byte) 1392 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1393 | MTU | (2 bytes) 1394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1396 o Type: Extended Reachability and MT IS sub-TLV type, set to MTU 1397 sub-TLV 28. 1399 o Length: 3. 1401 o F: Failed. This bit is a one if MTU testing failed on this link at 1402 the required campus-wide MTU. 1404 o RESV: 7 bits that MUST be sent as zero and ignored on receipt. 1406 o MTU: This field is set to the largest successfully tested MTU size 1407 for this link, or zero if it has not been tested, as specified in 1408 Section 4.3.2 of [RFC6325]. 1410 2.5 TRILL Neighbor TLV 1412 The TRILL Neighbor TLV is used in TRILL broadcast link IIH PDUs (see 1413 Section 4.1 below) in place of the IS Neighbor TLV, as specified in 1414 Section 4.4.2.1 of [RFC6325] and in [RFC6327]. The structure of the 1415 TRILL Neighbor TLV is as follows: 1417 +-+-+-+-+-+-+-+-+ 1418 | Type | (1 byte) 1419 +-+-+-+-+-+-+-+-+ 1420 | Length | (1 byte) 1421 +-+-+-+-+-+-+-+-+ 1422 |S|L|R| SIZE | (1 byte) 1423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1424 | Neighbor RECORDS (1) | 1425 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1426 | Neighbor RECORDS (2) | 1427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1428 | ................. | 1429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1430 | Neighbor RECORDS (N) | 1431 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1433 The information present for each neighbor is as follows: 1435 +-+-+-+-+-+-+-+-+ 1436 |F|O| RESV | (1 bytes) 1437 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1438 | MTU | (2 bytes) 1439 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+-+-+ 1440 | SNPA (MAC Address) | (SIZE bytes) 1441 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+-+-+ 1443 o Type: TLV Type, set to TRILL Neighbor TLV 145. 1445 o Length: 1 + (SIZE+3)*n, where n is the number of neighbor records, 1446 which may be zero. 1448 o S: Smallest flag. If this bit is a one, then the list of neighbors 1449 includes the neighbor with the smallest MAC address considered as 1450 an unsigned integer. 1452 o L: Largest flag. If this bit is a one, then the list of neighbors 1453 includes the neighbor with the largest MAC address considered as 1454 an unsigned integer. 1456 o R, RESV: These bits are reserved and MUST be sent as zero and 1457 ignored on receipt. 1459 o SIZE: The SNPA size as an unsigned integer in bytes except that 6 1460 is encoded as zero. An actual size of zero is meaningless and 1461 cannot be encoded. The meaning of the value 6 in this field is 1462 reserved and TRILL Neighbor TLVs received with a SIZE of 6 are 1463 ignored. The SIZE is inherent to the technology of a link and is 1464 fixed for all TRILL Neighbor TLVs on that link but may vary 1465 between different links in the campus if those links are different 1466 technologies. For example, 6 for EUI-48 SNPAs or 8 for EUI-64 1467 SNPAs [RFC7042]. (The SNPA size on the various links in a TRILL 1468 campus is independent of the System ID size.) 1470 o F: failed. This bit is a one if MTU testing to this neighbor 1471 failed at the required campus-wide MTU (see [RFC6325], Section 1472 4.3.1). 1474 o O: OOMF. This bit is a one if the IS sending the enclosing TRILL 1475 Neighbor TLV is willing to offer the Overload Originated Multi- 1476 destination Frame (OOMF) service [ClearCorrect] to the IS whose 1477 port has the SNPA in the enclosing Neighbor RECORD. 1479 o MTU: This field is set to the largest successfully tested MTU size 1480 for this neighbor or to zero if it has not been tested. 1482 o SNPA: Sub-Network Point of Attachment (MAC address) of the 1483 neighbor. 1485 As specified in [RFC6327] and Section 4.4.2.1 of [RFC6325], all MAC 1486 addresses may fit into one TLV, in which case both the S and L flags 1487 would be set to one in that TLV. If the MAC addresses don't fit into 1488 one TLV, the highest MAC address in a TRILL Neighbor TLV with the L 1489 flag zero MUST also appear as a MAC address in some other TRILL 1490 Neighbor TLV (possibly in a different TRILL IIH PDU). Also, the 1491 lowest MAC address in a TRILL Neighbor TLV with the S flag zero MUST 1492 also appear in some other TRILL Neighbor TLV (possibly in a different 1493 TRILL IIH PDU). If an IS believes it has no neighbors, it MUST send a 1494 TRILL Neighbor TLV with an empty list of neighbor RECORDS, which will 1495 have both the S and L bits on. 1497 3. MTU PDUs 1499 The IS-IS MTU-probe and MTU-ack PDUs are used to optionally determine 1500 the MTU on a link between ISs as specified in Section 4.3.2 of 1501 [RFC6325] and in [RFC6327]. 1503 The MTU PDUs have the IS-IS PDU common header (up through the Maximum 1504 Area Addresses byte) with PDU Type numbers as indicated in Section 5. 1505 They also have a common fixed MTU PDU header as shown below that is 8 1506 + 2*(ID Length) bytes long, 20 bytes in the case of the usual 6-bytes 1507 System IDs. 1509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1510 | PDU Length | (2 bytes) 1511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+.....+-+-+ 1512 | Probe ID (6 bytes) | 1513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+.....+-+-+ 1514 | Probe Source ID (ID Length bytes) | 1515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+.....+-+-+ 1516 | Ack Source ID (ID Length bytes) | 1517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+.....+-+-+ 1519 As with other IS-IS PDUs, the PDU length gives the length of the 1520 entire IS-IS packet starting with and including the IS-IS common 1521 header. 1523 The Probe ID field is an opaque 48-bit quantity set by the IS issuing 1524 an MTU-probe and copied by the responding IS into the corresponding 1525 MTU-ack. For example, an IS creating an MTU-probe could compose this 1526 quantity from a port identifier and probe sequence number relative to 1527 that port. 1529 The Probe Source ID is set by an IS issuing an MTU-probe to its 1530 System ID and copied by the responding IS into the corresponding MTU- 1531 ack. The Ack Source ID is set to zero in MTU-probe PDUs and ignored 1532 on receipt. An IS issuing an MTU-ack sets the Ack Source ID field to 1533 its System ID. The System ID length is usually 6 bytes but could be a 1534 different value as indicated by the ID Length field in the IS-IS PDU 1535 Header. 1537 The TLV area follows the MTU PDU header area. This area MAY contain 1538 an Authentication TLV and MUST be padded with the Padding TLV to the 1539 exact size being tested. Since the minimum size of the Padding TLV is 1540 2 bytes, it would be impossible to pad to exact size if the total 1541 length of the required information bearing fixed fields and TLVs 1542 added up to 1 byte less than the desired length. However, the length 1543 of the fixed fields and substantive TLVs for MTU PDUs is expected to 1544 be quite small compared with their minimum length (minimum 1470-byte 1545 MTU on an IEEE 802.3 link, for example), so this should not be a 1546 problem. 1548 4. Use of Existing PDUs and TLVs 1550 The sub-sections below provide details of TRILL use of existing PDUs 1551 and TLVs. 1553 4.1 TRILL IIH PDUs 1555 The TRILL IIH PDU is the variation of the IIH PDU used by the TRILL 1556 protocol. Section 4.4 of the TRILL standard [RFC6325] and [RFC6327] 1557 specify the contents of the TRILL IIH and how its use in TRILL 1558 differs from Layer 3 LAN IIH PDU use. The adjacency state machinery 1559 for TRILL neighbors is specified in detail in [RFC6327]. 1561 In a TRILL IIH PDU, the IS-IS common header and the fixed PDU Header 1562 are the same as a Level 1 IIH PDU. 1564 The IS-IS Neighbor TLV (6) is not used in a TRILL IIH and is ignored 1565 if it appears there. Instead, TRILL LAN IIH PDUs use the TRILL 1566 Neighbor TLV (see Section 2.5). 1568 4.2 Area Address 1570 TRILL uses a fixed zero Area Address as specified in [RFC6325], 1571 Section 4.2.3. This is encoded in a 4-byte Area Address TLV (TLV #1) 1572 as follows: 1574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1575 | 0x01, Area Address Type | (1 byte) 1576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1577 | 0x02, Length of Value | (1 byte) 1578 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1579 | 0x01, Length of Address | (1 byte) 1580 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1581 | 0x00, zero Area Address | (1 byte) 1582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1584 4.3 Protocols Supported 1586 NLPID (Network Layer Protocol ID) 0xC0 has been assigned to TRILL 1587 [RFC6328]. A Protocols Supported TLV (#129, [RFC1195]) including that 1588 value appears in TRILL IIH PDUs and LSP number zero PDUs. 1590 4.4 Link State PDUs (LSPs) 1592 A number zero LSP MUST NOT be originated larger than 1470 bytes but a 1593 larger number zero LSP successfully received MUST be processed and 1594 forwarded normally. 1596 4.5 Originating LSP Buffer Size 1598 The originatingLSPBufferSize TLV (#14) MUST be in LSP number zero; 1599 however, if found in other LSP fragments, it is processed normally. 1600 Should there be more than one originatingLSPBufferSize TLV for an IS, 1601 the minimum size, but not less than 1470, is used. 1603 5. IANA Considerations 1605 This section gives IANA Considerations for the TLVs, sub-TLVs, and 1606 PDUs specified herein. A number of new code points are assigned and 1607 those that were assigned by [RFC6326] are included here for 1608 convenience. IANA is requested to replace all [RFC6326] references 1609 in the IANA Registries with references to this document. 1611 5.1 TLVs 1613 This document specifies two IS-IS TLV types -- namely, the Group 1614 Address TLV (GADDR-TLV, type 142) and the TRILL Neighbor TLV (type 1615 145). The PDUs in which these TLVs are permitted for TRILL are shown 1616 in the table below along with the section of this document where they 1617 are discussed. The final "NUMBER" column indicates the permitted 1618 number of occurrences of the TLV in their PDU, or set of PDUs in the 1619 case of LSP, which in these two cases is "*" indicating that the TLV 1620 MAY occur 0, 1, or more times. 1622 IANA has registered these two code points in the IANA IS-IS TLV 1623 registry (ignoring the "Section" and "NUMBER" columns, which are 1624 irrelevant to that registry). 1626 Section TLV IIH LSP SNP Purge NUMBER 1627 ======= === === === === ===== ====== 1628 GADDR-TLV 2.1 142 - X - - * 1629 TRILL Neighbor TLV 2.5 145 X - - - * 1631 5.2 sub-TLVs 1633 This document specifies a number of sub-TLVs. The TLVs in which these 1634 sub-TLVs occur are shown in the second table below along with the 1635 section of this document where they are discussed. The TLVs within 1636 which these sub-TLVs can occur are determined by the presence of an 1637 "X" in the relevant column and the column header as shown in the 1638 first table below. In some cases, the column header corresponds to 1639 two different TLVs in which the sub-TLV can occur. 1641 Column Head TLV RFCref TLV Name 1642 =========== ===== ======== ============== 1643 Grp. Adr. 142 This doc Group Address 1645 MT Port 143 6165 MT-PORT-CAP 1647 MT Cap. 242 4971 Router CAPABILITY 1648 144 6329 MT-Capability 1650 Ext. Reach 22 5305 Extended IS Reachability 1651 222 5120 MT ISN 1653 The final "NUMBER" column below indicates the permitted number of 1654 occurrences of the sub-TLV cumulatively within all occurrences of 1655 their TLV(s) in those TLVs' carrying PDU (or set of PDUs in the case 1656 of LSP), as follows: 1658 0-1 = MAY occur zero or one times. 1659 1 = MUST occur exactly once. If absent, the PDU is ignored. If it 1660 occurs more than once, results are unspecified. 1661 * = MAY occur 0, 1, or more times. 1663 The values in the "Section" and "NUMBER" columns are irrelevant to 1664 the IANA sub-registries. The numbers in square brackets are suggested 1665 values. 1667 sub- Grp. MT MT Ext. 1668 Name Section TLV# Adr. Port Cap. Reach NUMBER 1669 ================================================================= 1670 GMAC-ADDR 2.1.1 1 X - - - * 1671 GIP-ADDR 2.1.2 TBDa[2] X - - - * 1672 GIPV6-ADDR 2.1.3 TBDb[3] X - - - * 1673 GLMAC-ADDR 2.1.4 TBDc[4] X - - - * 1674 GLIP-ADDR 2.1.5 TBDd[5] X - - - * 1675 GLIPV6-ADDR 2.1.6 TBDe[6] X - - - * 1676 VLAN-FLAGS 2.2.1 1 - X - - 1 1677 Enabled-VLANs 2.2.2 2 - X - - * 1678 AppointedFwrdrs 2.2.3 3 - X - - * 1679 PORT-TRILL-VER 2.2.4 TBDf[7] - X - - 0-1 1680 VLANs-Appointed 2.2.5 TBDg[8] - X - - * 1681 NICKNAME 2.3.2 6 - - X - * 1682 TREES 2.3.3 7 - - X - 0-1 1683 TREE-RT-IDs 2.3.4 8 - - X - * 1684 TREE-USE-IDs 2.3.5 9 - - X - * 1685 INT-VLAN 2.3.6 10 - - X - * 1686 TRILL-VER 2.3.1 13 - - X - 0-1 1687 VLAN-GROUP 2.3.7 14 - - X - * 1688 INT-LABEL 2.3.8 TBDh[15] - - X - * 1689 RBCHANNELS 2.3.9 TBDi[16] - - X - * 1690 AFFINITY 2.3.10 TBDj[17] - - X - * 1691 LABEL-GROUP 2.3.11 TBDk[18] - - X - * 1692 MTU 2.4 28 - - - X 0-1 1693 ================================================================= 1694 Name Section sub- Grp. MT MT Ext. NUMBER 1695 TLV# Adr. Port Cap. Reach 1697 IANA is requested to enter the newly assigned sub-TLV numbers in the 1698 above table in the one or two relevant existing sub-TLV registries, 1699 as determined by which column has an X opposite that sub-TLV. For the 1700 sub-TLVs from NICKNAME through and including VLAN-GROUP, which 1701 currently exist only in the registry of sub-TLVs under TLV 242, IANA 1702 is requested to add each sub-TLV with the same sub-TLV number to the 1703 existing registry for sub-TLVs under TLV 144. 1705 5.3 PDUs 1707 The IS-IS PDUs registry remains as established in [RFC6326] except 1708 that the references to [RFC6326] are updated to reference this 1709 document. 1711 5.4 Reserved and Capability Bits 1713 Any reserved bits (R) or bits in reserved fields (RESV) or the 1714 capabilities bits in the PORT-TRILL-VER and TRILL-VER sub-TLVs, which 1715 are specified herein as "MUST be sent as zero and ignored on receipt" 1716 or the like, are allocated based on IETF Review [RFC5226]. 1718 Two sub-registries are created within the TRILL Parameters Registry 1719 as follows: 1721 Sub-Registry Name: TRILL-VER Sub-TLV Capability Flags 1722 Registration Procedures: IETF Review 1723 Reference: (This document) 1725 Bit Description Reference 1726 ===== ============= =========== 1727 0 Affinity sub-TLV support. [Affinity] 1728 1-13 Unassigned 1729 14-31 Extended header flag support. [ExtendHeader] 1731 Sub-Registry Name: PORT-TRILL-VER Sub-TLV Capability Flags 1732 Registration Procedures: IETF Review 1733 Reference: (This document) 1735 Bit Description Reference 1736 ===== ============= =========== 1737 0 Hello reduction support. [ClearCorrect] 1738 1-2 Unassigned 1739 3-13 Hop-by-hop extended flag support. [ExtendHeader] 1740 14-31 Unassigned 1742 5.5 TRILL Neighbor Record Flags 1744 A sub-registry is created within the TRILL Parameters Registry as 1745 follows: 1747 Sub-Registry Name: TRILL Neighbor TLV NEIGHBOR RECORD Flags 1748 Registration Procedures: Standards Action 1749 Reference: (This document) 1751 Bit Short Name Description Reference 1752 ============== ============= =========== 1753 0 Fail Failed MTU test [RFC6325] 1754 1 OOMF Offering OOMF service [ClearCorrect] 1755 2-7 - Unassigned 1757 6. Security Considerations 1759 For general TRILL protocol security considerations, see the TRILL 1760 base protocol standard [RFC6325]. 1762 This document raises no new security issues for IS-IS. IS-IS security 1763 may be used to secure the IS-IS messages discussed here. See 1764 [RFC5304] and [RFC5310]. Even when IS-IS authentication is used, 1765 replays of Hello packets can create denial-of-service conditions; see 1766 [RFC6039] for details. These issues are similar in scope to those 1767 discussed in Section 6.2 of [RFC6325], and the same mitigations may 1768 apply. 1770 7. Change from RFC 6326 1772 Non-editorial changes from [RFC6326] are summarized in the list 1773 below: 1775 1. Additional of five sub-TLVs under the Group Address (GADDR) TLV 1776 covering VLAN labeled IPv4 and IPv6 addresses and fine-grained 1777 labeled MAC, IPv4, and IPv6 addresses. (Sections 2.1.2, 2.1.3, 1778 2.1.4, 2.1.5, and 2.1.6). 1780 2. Addition of the PORT-TRILL-VER sub-TLV. (Section 2.2.4) 1782 3. Addition of the VLANs-Appointed sub-TLV. (Section 2.2.5) 1784 4. Change the TRILL-VER sub-TLV as listed below. 1786 4.a Addition of 4 bytes of TRILL Header extended flags and 1787 capabilities supported information. 1789 4.b Require that the TRILL-VER sub-TLV appear in LSP number zero. 1791 The above changes to TRILL-VER are backwards compatible because 1792 the [RFC6326] conformant implementations of TRILL thus far have 1793 only supported version zero and not supported any optional 1794 capabilities or extended flags, the level of support indicated by 1795 the absence of the TRILL-VER sub-TLV. Thus, if an [RFC6326] 1796 conformant implementation of TRILL rejects this sub-TLV due to 1797 the changes specified in this document, it will, at worst, decide 1798 that support of version zero and no extended flags or 1799 capabilities is indicated, which is the best an [RFC6326] 1800 conformant implementation of TRILL can do anyway. Similarly, a 1801 TRILL implementation that supports TRILL-VER as specified herein 1802 and rejects TRILL-VER sub-TLVs in an [RFC6326] conformant TRILL 1803 implementation because they are not in LSP number zero will 1804 decide that that implementation supports only version zero with 1805 no extended flag or capabilities support, which will be correct. 1806 (Section 2.3.1) 1808 5. Clarification of the use of invalid VLAN IDs (0x000 and 0xFFF) in 1809 the Appointed Forwarders sub-TLV and the Interested VLANs and 1810 Spanning Tree Roots sub-TLV. (Sections 2.2.3 and 2.3.6) 1812 6. Addition of the Interested Labels and Spanning Tree Roots sub-TLV 1813 to indicate attachment of an IS to a fine-grained label [RFCfgl] 1814 analogous to the existing Interested VLANs and Spanning Tree 1815 Roots sub-TLV for VLANs. (Section 2.3.8) 1817 7. Addition of the RBridge Channel Protocols sub-TLV so ISs can 1818 announce the RBridge Channel protocols they support. (Section 1819 2.3.9) 1821 8. Permit specification of the length of the link SNPA field in 1822 TRILL Neighbor TLVs. This change is backwards compatible because 1823 the size of 6 bytes is specially encoded as zero, the previous 1824 value of the bits in the new SIZE field. (Section 2.5) 1826 9. Make the size of the MTU PDU Header Probe Source ID and Ack 1827 Source ID fields be the ID Length from the IS-IS PDU Header 1828 rather than the fixed value 6. (Section 3) 1830 10. For robustness, require LSP number zero PDUs be originated as no 1831 larger than 1470 bytes but processed regardless of size. (Section 1832 4.4) 1834 11. Require that the originatingLSPBufferSize TLV, if present, appear 1835 in LSP number zero. (Section 4.5) 1837 12. Create sub-registries for and specify the IANA Considerations 1838 policy for reserved and capability bits in the TRILL version sub- 1839 TLVs. (Section 5.4) 1841 13. Addition of the distribution tree Affinity sub-TLV so ISs can 1842 request distribution tree attachments. (Section 2.3.10) 1844 14. Add LABEL-GROUP sub-TLV analogous to the VLAN-GROUP sub-TLV. 1845 (Section 2.3.11) 1847 15. Add multi-topology: permit sub-TLVs previously only in Router 1848 Capabilities TLV to also appear in MT Capabilities TLV; permit 1849 MTU sub-TLV previously limited to Extended Reachability TLV to 1850 also appear in MT ISN TLV. 1852 16. Addition of a sub-registry for Neighbor TLV Neighbor RECORD flag 1853 bits. (Section 5.5) 1855 17. Explicitly state that if the number of sources in a GADDR-TLV 1856 sub-TLV is zero, it indicates a listener for (*,G), that is, a 1857 listener not restricted by source. (Section 2.1) 1859 8. Normative References 1861 [ISO-10589] - ISO/IEC 10589:2002, Second Edition, "Intermediate 1862 System to Intermediate System Intra-Domain Routing Exchange 1863 Protocol for use in Conjunction with the Protocol for Providing 1864 the Connectionless-mode Network Service (ISO 8473)", 2002. 1866 [RFC1195] - Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and 1867 Dual Environments", 1990. 1869 [RFC1982] - Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1870 1982, August 1996. 1872 [RFC2119] - Bradner, S., "Key words for use in RFCs to Indicate 1873 Requirement Levels", BCP 14, RFC 2119, March 1997. 1875 [RFC4971] - Vasseur, JP. and N. Shen, "Intermediate System to 1876 Intermediate System (IS-IS) Extensions for Advertising Router 1877 Information", 2007. 1879 [RFC5120] - Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 1880 Topology (MT) Routing in Intermediate System to Intermediate 1881 Systems (IS-ISs)", RFC 5120, February 2008. 1883 [RFC5226] - Narten, T. and H. Alvestrand, "Guidelines for Writing an 1884 IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 1885 2008. 1887 [RFC5305] - Li, T. and H. Smit, "IS-IS Extensions for Traffic 1888 Engineering", 2008. 1890 [RFC6165] - Banerjee, A. and D. Ward, "Extensions to IS-IS for 1891 Layer-2 Systems", RFC 6165, April 2011. 1893 [RFC6325] - Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A. 1894 Ghanwani, "RBridges: Base Protocol Specification", RFC 6325, 1895 June 2011. 1897 [RFC6327] - Eastlake, D., Perlman, R., Ghanwani, A., Dutt, D., and V. 1898 Manral, "RBridges: Adjacency", RFC 6327, July 2011. 1900 [RFC6328] - Eastlake, D., "IANA Considerations for Network Layer 1901 Protocol Identifiers", RFC 6328, June 2011. 1903 [RFC6329] - Fedyk, D., Ed., Ashwood-Smith, P., Ed., Allan, D., Bragg, 1904 A., and P. Unbehagen, "IS-IS Extensions Supporting IEEE 802.1aq 1905 Shortest Path Bridging", RFC 6329, April 2012. 1907 [RFC6439] - Perlman, R., Eastlake, D., Li, Y., Banerjee, A., and F. 1908 Hu, "Routing Bridges (RBridges): Appointed Forwarders", RFC 1909 6439, November 2011. 1911 [Channel] - D. Eastlake, V. Manral, L. Yizhou, S. Aldrin, D. Ward, 1912 draft-ietf-trill-rbridge-channel, in RFC Editor's queue. 1914 [ClearCorrect] - D. Eastlake, M. Zhang, A. Ghanwani, V. Manral, A. 1915 Banerjee, draft-ietf-trill-clear-correct, in RFC Editor's 1916 queue. 1918 [ExtendHeader] - D. Eastlake, A. Ghanwani, V. Manral, Y. Li, C. 1919 Bestler, draft-ietf-trill-rbridge-extension, in RFC Editor's 1920 queue. 1922 [RFCfgl] - Eastlake, D., M. Zhang, P. Agarwal, R. Perlman, D. Dutt, 1923 "TRILL (Transparent Interconnection of Lots of Links): Fine- 1924 Grained Labeling", draft-ietf-trill-fine-labeling, in RFC 1925 Ediotr's queue. 1927 9. Informative References 1929 [Err2869] - RFC Errata, Errata ID 2869, RFC 6326, http://www.rfc- 1930 editor.org. 1932 [RFC5304] - Li, T. and R. Atkinson, "IS-IS Cryptographic 1933 Authentication", RFC 5304, October 2008. 1935 [RFC5310] - Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R., 1936 and M. Fanto, "IS-IS Generic Cryptographic Authentication", RFC 1937 5310, February 2009. 1939 [RFC6039] - Manral, V., Bhatia, M., Jaeggli, J., and R. White, 1940 "Issues with Existing Cryptographic Protection Methods for 1941 Routing Protocols", RFC 6039, October 2010. 1943 [RFC6326] - Eastlake, D., Banerjee, A., Dutt, D., Perlman, R., and A. 1944 Ghanwani, "Transparent Interconnection of Lots of Links (TRILL) 1945 Use of IS-IS", RFC 6326, July 2011. 1947 [RFC7042] - Eastlake 3rd, D. and J. Abley, "IANA Considerations and 1948 IETF Protocol and Documentation Usage for IEEE 802 Parameters", 1949 BCP 141, RFC 7042, October 2013. 1951 [RFCtrillBFD] - V. Manral, D, Eastlake, D. Ward, A. Banerjee, draft- 1952 ietf-trill-rbridge-bfd-07.txt, in RFC Editor's queue. 1954 [Affinity] - draft-ietf-trill-cmt, work in progress. 1956 [MultiLevel] - draft-perlman-trill-rbridge-multilevel, work in 1957 progress. 1959 [Resilient] - draft-zhang-trill-resilient-trees, work in progress. 1961 Acknowledgements 1963 The authors gratefully acknowledge the contributions and review by 1964 the following: 1966 Ross Callon, Adrian Farrel, Alexey Melnikov, Radia Perlman, Carlos 1967 Pignataro, Joe Touch. 1969 And the contributions by the following to [RFC6326]: 1971 Mike Shand, Stewart Bryant, Dino Farinacci, Les Ginsberg, Sam 1972 Hartman, Dan Romascanu, Dave Ward, and Russ White. In particular, 1973 thanks to Mike Shand for the detailed and helpful comments. 1975 This document was produced with raw nroff. All macros used were 1976 defined in the source files. 1978 Authors' Addresses 1980 Donald Eastlake 1981 Huawei Technologies 1982 155 Beaver Street 1983 Milford, MA 01757 USA 1985 Phone: +1-508-333-2270 1986 EMail: d3e3e3@gmail.com 1988 Tissa Senevirathne 1989 Cisco Systems 1990 375 East Tasman Drive, 1991 San Jose, CA 95134 1993 Phone: +1-408-853-2291 1994 EMail: tsenevir@cisco.com 1996 Anoop Ghanwani 1997 Dell 1998 350 Holger Way 1999 San Jose, CA 95134 USA 2001 Phone: +1-408-571-3500 2002 EMail: anoop@alumni.duke.edu 2004 Dinesh Dutt 2005 Cumulus Networks 2006 1089 West Evelyn Avenue 2007 Sunnyvale, CA 94086 USA 2009 EMail: ddutt.ietf@hobbesdutt.com 2011 Ayan Banerjee 2012 Insieme Networks 2013 210 West Tasman Drive 2014 San Jose, CA 95134 USA 2016 Email: ayabaner@gmail.com 2018 Copyright, Disclaimer, and Additional IPR Provisions 2020 Copyright (c) 2014 IETF Trust and the persons identified as the 2021 document authors. All rights reserved. 2023 This document is subject to BCP 78 and the IETF Trust's Legal 2024 Provisions Relating to IETF Documents 2025 (http://trustee.ietf.org/license-info) in effect on the date of 2026 publication of this document. Please review these documents 2027 carefully, as they describe your rights and restrictions with respect 2028 to this document. Code Components extracted from this document must 2029 include Simplified BSD License text as described in Section 4.e of 2030 the Trust Legal Provisions and are provided without warranty as 2031 described in the Simplified BSD License.