idnits 2.17.1 draft-ietf-isis-l2bundles-04.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 11, 2017) is 2571 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.1AX' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO10589' == Outdated reference: A later version (-25) exists of draft-ietf-isis-segment-routing-extensions-11 == Outdated reference: A later version (-15) exists of draft-ietf-spring-segment-routing-11 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Networking Working Group L. Ginsberg 3 Internet-Draft A. Bashandy 4 Intended status: Standards Track C. Filsfils 5 Expires: October 13, 2017 Cisco Systems 6 M. Nanduri 7 Microsoft 8 E. Aries 9 Private Contributer 10 April 11, 2017 12 Advertising L2 Bundle Member Link Attributes in IS-IS 13 draft-ietf-isis-l2bundles-04.txt 15 Abstract 17 There are deployments where the Layer 3 interface on which IS-IS 18 operates is a Layer 2 interface bundle. Existing IS-IS 19 advertisements only support advertising link attributes of the Layer 20 3 interface. If entities external to IS-IS wish to control traffic 21 flows on the individual physical links which comprise the Layer 2 22 interface bundle link attribute information about the bundle members 23 is required. 25 This document introduces the ability for IS-IS to advertise the link 26 attributes of layer 2 (L2) bundle members. 28 Requirements Language 30 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 31 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 32 document are to be interpreted as described in RFC 2119 [RFC2119]. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on October 13, 2017. 50 Copyright Notice 52 Copyright (c) 2017 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 68 2. L2 Bundle Member Attributes TLV . . . . . . . . . . . . . . . 3 69 2.1. Parallel L3 Adjacencies . . . . . . . . . . . . . . . . . 5 70 2.2. Shared Attribute sub-TLVs . . . . . . . . . . . . . . . . 5 71 3. Advertising L2 Bundle Member Adj-SIDs . . . . . . . . . . . . 5 72 3.1. L2 Bundle Member Adjacency Segment Identifier sub-TLV . . 6 73 3.2. L2 Bundle Member LAN Adjacency Segment Identifier sub-TLV 7 74 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 75 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 76 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 77 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 78 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 79 8.1. Normative References . . . . . . . . . . . . . . . . . . 11 80 8.2. Informational References . . . . . . . . . . . . . . . . 12 81 Appendix A. Example Encoding . . . . . . . . . . . . . . . . . . 12 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 84 1. Introduction 86 There are deployments where the Layer 3 interface on which an IS-IS 87 adjacency is established is a Layer 2 interface bundle, for instance 88 a Link Aggregation Group (LAG) [IEEE802.1AX]. This reduces the 89 number of adjacencies which need to be maintained by the routing 90 protocol in cases where there are parallel links between the 91 neighbors. Entities external to IS-IS such as Path Computation 92 Elements (PCE) [RFC4655] may wish to control traffic flows on 93 individual members of the underlying Layer 2 bundle. In order to do 94 so link attribute information about individual bundle members is 95 required. The protocol extensions defined in this document provide 96 the means to advertise this information. 98 This document introduces a new TLV to advertise link attribute 99 information for each of the L2 bundle members which comprise the 100 Layer 3 interface on which IS-IS operates. 102 [SR-ISIS] introduces a new link attribute - adjacency segment 103 identifier (Adj-SID) - which can be used as an instruction to 104 forwarding to send traffic over a specific link. This document 105 introduces additional sub-TLVs to advertise Adj-SIDs for L2 Bundle 106 members. 108 Note that the new advertisements defined in this document are 109 intended to be provided to external entities. 111 2. L2 Bundle Member Attributes TLV 113 A new TLV is introduced to advertise L2 Bundle member attributes. 114 Although much of the information is identical to and uses the same 115 sub-TLVs included in Extended IS-Neighbor advertisements (TLVs 22 and 116 222), a new TLV is used so that changes to the advertisement of the 117 L2 Bundle member link attributes does not trigger unnecessary action 118 by the [ISO10589] Decision process. 120 This new TLV utilizes the sub-TLV space defined for TLVs 22, 23, 141, 121 222, and 223. 123 The following new TLV is introduced: 125 L2 Bundle Member Attributes 126 Type: 25 (suggested - to be assigned by IANA) 127 Length: Number of octets to follow 129 Parent L3 Neighbor Descriptor 130 L3 Neighbor System ID + pseudonode ID (7 octets) 131 Flags: 1 octet field of following flags: 133 0 1 2 3 4 5 6 7 134 +-+-+-+-+-+-+-+-+ 135 |P| | 136 +-+-+-+-+-+-+-+-+ 138 where: 140 P-flag: When set to 1 one of the sub-TLVs described 141 in Section 2.1 immediately follows the flags field. 142 If the P-flag is set to 0, then none of the sub-TLVs 143 described in Section 2.1 are present. 145 Other bits: MUST be zero when originated and ignored when 146 received. 148 One or more of the following: 149 L2 Bundle Attribute Descriptors 150 Length of L2 Bundle Attribute Descriptor (1 octet) 151 NOTE: This includes all fields described below. 153 Number of L2 Bundle Member Descriptors (1 octet) 154 L2 Bundle Member Link Local Identifiers 155 (4 * Number of L2 Bundle Member Descriptors octets) 157 NOTE: An L2 Bundle Member Descriptor is a Link Local 158 Identifier as defined in [RFC4202]. 160 sub-TLV(s) 162 A sub-TLV may define an attribute common to all of 163 the bundle members listed or a sub-TLV may define an 164 attribute unique to each bundle member. Use of these 165 two classes of sub-TLVs is described in the following 166 sections. 168 NOTE: Only one Parent L3 Neighbor Descriptor is present in a given 169 TLV. Multiple L2 Bundle Attribute Descriptors may be present in a 170 single TLV. 172 2.1. Parallel L3 Adjacencies 174 When there exist multiple L3 adjacencies to the same neighbor 175 additional information is required to uniquely identify the L3 176 Neighbor. One and only one of the following three sub-TLVs is used 177 to uniquely identify the L3 adjacency: 179 o IPv4 Interface Address (sub-TLV 6 defined in [RFC5305]) 181 o IPv6 Interface Address (sub-TLV 12 defined in [RFC6119]) 183 o Link Local/Remote Identifiers (sub-TLV 4 defined in [RFC5307]) 185 When the P-bit is set in the flags field in the Parent L3 Neighbor 186 Descriptor one and only one of the above sub-TLVs MUST be present. 187 The chosen sub-TLV MUST immediately follow the flags field described 188 in Section 2. 190 These sub-TLVs MAY be omitted if no parallel adjacencies to the 191 neighbor exist. 193 2.2. Shared Attribute sub-TLVs 195 These sub-TLVs advertise a single copy of an attribute (e.g. link 196 bandwidth). The attribute applies to all of the L2 Bundle Members in 197 the set advertised under the preceding L2 Bundle Member Attribute 198 Descriptor. No more than one copy of a given sub-TLV in this 199 category may appear in the set of sub-TLVs under the preceding L2 200 Bundle Member Attribute Descriptor. If multiple copies of a given 201 sub-TLV are present all copies MUST be ignored. 203 The set of L2 Bundle Member Descriptors which may be advertised under 204 a single L2 Bundle Member Attribute Descriptor is therefore limited 205 to bundle members which share the set of attributes advertised in the 206 shared attribute sub-TLVs. 208 All existing sub-TLVs defined in the IANA Sub-TLVs for TLVs 22, 23, 209 141, 222, and 223 registry are in the category of shared attribute 210 sub-TLVs unless otherwise specified in this document. 212 3. Advertising L2 Bundle Member Adj-SIDs 214 [SR-ISIS] defines sub-TLVs to advertise Adj-SIDs for L3 adjacencies. 215 However these sub-TLVs only support a advertisement of a single Adj- 216 SID. As it is expected that each L2 Bundle member will have unique 217 Adj-SIDs in many deployments it is desirable to define a new sub-TLV 218 which allows more efficient encoding of a set of Adj-SIDs in a single 219 sub-TLV. Two new sub-TLVs are therefore introduced to support 220 advertising Adj-SIDs for L2 Bundle members. The format of the new 221 sub-TLVs is similar to that used for L3 adjacencies, but is optimized 222 to allow advertisement of a set of Adj-SIDs (one per L2 Bundle 223 Member) in a single sub-TLV. 225 The two new sub-TLVs defined in the following sections do not fall 226 into the category of shared attribute sub-TLVs. 228 3.1. L2 Bundle Member Adjacency Segment Identifier sub-TLV 230 This sub-TLV is used to advertise Adj-SIDs for L2 Bundle Members 231 associated with a parent L3 adjacency which is Point-to-Point. The 232 following format is defined for this sub-TLV: 234 Type: 41 (suggested value to be assigned by IANA) (1 octet) 235 Length: variable (1 octet) 237 Flags: 1 octet field of following flags: 239 0 1 2 3 4 5 6 7 240 +-+-+-+-+-+-+-+-+ 241 |F|*|V|L|S|P| | 242 +-+-+-+-+-+-+-+-+ 244 where: 246 NOTE: The flags are deliberately kept congruent to the flags 247 in the L3 ADJ-SID defined in [SR-ISIS]. 248 * indicates a flag used in the L3 Adj-SID sub-TLV but which is 249 NOT used in this sub-TLV. These bits SHOULD be sent as 0 and 250 MUST be ignored on receipt. 252 F-Flag: Address-Family flag. If unset, then the Adj-SID refers 253 to an L2 Bundle Member with outgoing IPv4 encapsulation. If set 254 then the Adj-SID refers to an L2 Bundle Member with outgoing 255 IPv6 encapsulation. 257 V-Flag: Value flag. If set, then the Adj-SID carries a value. 258 By default the flag is SET. 260 L-Flag: Local Flag. If set, then the value/index carried by 261 the Adj-SID has local significance. By default the flag is 262 SET. 264 S-Flag. Set Flag. When set, the S-Flag indicates that the 265 Adj-SID refers to a set of L2 Bundle Members (and therefore 266 MAY be assigned to other L2 Bundle Members as well). 268 P-Flag. Persistent flag. When set, the P-Flag indicates that 269 the Adj-SID is persistently allocated, i.e., the Adj-SID value 270 remains consistent across router restart and/or interface flap. 272 Other bits: MUST be zero when originated and ignored when 273 received. 275 Weight: 1 octet. The value represents the weight of the Adj-SID 276 for the purpose of load balancing. The use of the weight is 277 defined in [SR-ARCH]. 279 NOTE: Flags and weight are shared by all L2 Bundle Members 280 listed in the L2 Bundle Attribute Descriptor. 282 L2 Bundle Member Adj-SID Descriptors. There MUST be one descriptor 283 for each of the L2 Bundle Members advertised under the preceding 284 L2 Bundle Member Attribute Descriptor. Each descriptor consists 285 of one of the following fields: 287 SID/Index/Label: according to the V and L flags, it contains 288 either: 290 * A 3 octet local label where the 20 rightmost bits are used 291 for encoding the label value. In this case the V and L 292 flags MUST be set. 294 * A 4 octet index defining the offset in the SID/Label space 295 advertised by this router. See [SR-ISIS]. 296 In this case V and L flags MUST be unset. 298 3.2. L2 Bundle Member LAN Adjacency Segment Identifier sub-TLV 300 This sub-TLV is used to advertise Adj-SIDs for L2 Bundle Members 301 associated with a parent L3 adjacency which is a LAN adjacency. In 302 LAN subnetworks, the Designated Intermediate System (DIS) is elected 303 and originates the Pseudonode-LSP (PN-LSP) including all neighbors of 304 the DIS. When Segment Routing is used, each router in the LAN MAY 305 advertise the Adj-SID of each of its neighbors on the LAN. 306 Similarly, for each L2 Bundle Member a router MAY advertise an Adj- 307 SID to each neighbor on the LAN. 309 The following format is defined for this sub-TLV: 311 Type: 42 (suggested value to be assigned by IANA) (1 octet) 312 Length: variable (1 octet) 313 Neighbor System ID: 6 octets 314 Flags: 1 octet field of following flags: 316 0 1 2 3 4 5 6 7 317 +-+-+-+-+-+-+-+-+ 318 |F|*|V|L|S|P| | 319 +-+-+-+-+-+-+-+-+ 321 where: 323 NOTE: The flags are deliberately kept congruent to the flags 324 in the L3 LAN_ADJ-SID defined in [SR-ISIS]. 325 * indicates a flag used in the L3 Adj-SID sub-TLV but which is 326 NOT used in this sub-TLV. These bits SHOULD be sent as 0 and 327 MUST be ignored on receipt. 329 F-Flag: Address-Family flag. If unset, then the Adj-SID refers 330 to an L2 Bundle Member with outgoing IPv4 encapsulation. If set 331 then the Adj-SID refers to an L2 Bundle Member with outgoing 332 IPv6 encapsulation. 334 V-Flag: Value flag. If set, then the Adj-SID carries a value. 335 By default the flag is SET. 337 L-Flag: Local Flag. If set, then the value/index carried by 338 the Adj-SID has local significance. By default the flag is 339 SET. 341 S-Flag. Set Flag. When set, the S-Flag indicates that the 342 Adj-SID refers to a set of L2 Bundle Members (and therefore 343 MAY be assigned to other L2 Bundle Members as well). 345 P-Flag. Persistent flag. When set, the P-Flag indicates that 346 the Adj-SID is persistently allocated, i.e., the Adj-SID value 347 remains consistent across router restart and/or interface flap. 349 Other bits: MUST be zero when originated and ignored when 350 received. 352 Weight: 1 octet. The value represents the weight of the Adj-SID 353 for the purpose of load balancing. The use of the weight is 354 defined in [SR-ARCH]. 356 NOTE: Flags and weight are shared by all L2 Bundle Members 357 listed in the L2 Bundle Attribute Descriptor. 359 L2 Bundle Member LAN Adj-SID Descriptors. There MUST be one 360 descriptor for each of the L2 Bundle Members advertised 361 under the preceding L2 Bundle Member Attribute Descriptor. 363 Each descriptor consists of one of the following fields: 365 SID/Index/Label: according to the V and L flags, it contains 366 either: 368 * A 3 octet local label where the 20 rightmost bits are used 369 for encoding the label value. In this case the V and L 370 flags MUST be set. 372 * A 4 octet index defining the offset in the SID/Label space 373 advertised by this router. See [SR-ISIS]. 374 In this case V and L flags MUST be unset. 376 4. IANA Considerations 378 This document adds the following new TLV to the IS-IS TLV Codepoints 379 registry. 381 Value: 25 (suggested - to be assigned by IANA) 383 Name: L2 Bundle Member Attributes 385 The name of the Sub-TLVs for TLVs 22, 23, 141, 222, and 223 registry 386 needs to be changed to Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 387 223 registry. An additional column needs to be added to the registry 388 to indicate which sub-TLVs may appear in the new L2 Bundle Member 389 Attributes TLV. The column for TLV 25 has one of the following three 390 values: 392 y - sub-TLV may appear in TLV 25 but MUST NOT be shared by multiple 393 L2 Bundle Members 394 y(s) - sub-TLV may appear in TLV 25 and MAY be shared by multiple 395 L2 Bundle Members 396 n - sub-TLV MUST NOT appear in TLV 25 398 The following table indicates the appropriate settings for all 399 currently defined sub-TLVs as regards their use in the new L2 Bundle 400 Member Attributes TLV. 402 3 Administrative group (color) y(s) 403 4 Link Local/Remote Identifiers y(s) 404 6 IPv4 interface address y(s) 405 8 IPv4 neighbor address y(s) 406 9 Maximum link bandwidth y(s) 407 10 Maximum reservable link bandwidth y(s) 408 11 Unreserved bandwidth y(s) 409 12 IPv6 Interface Address y(s) 410 13 IPv6 Neighbor Address y(s) 411 14 Extended Administrative Group y(s) 412 18 TE Default metric y(s) 413 19 Link-attributes y(s) 414 20 Link Protection Type y(s) 415 21 Interface Switching Capability Descriptor y(s) 416 22 Bandwidth Constraints y(s) 417 23 Unconstrained TE LSP Count y(s) 418 24 Remote AS number n 419 25 IPv4 remote ASBR Identifier n 420 26 IPv6 remote ASBR Identifier n 421 27 Interface Adjustment Capability Descriptor (IACD) y(s) 422 28 MTU n 423 29 SPB-Metric y(s) 424 30 SPB-A-OALG y(s) 426 This document adds the following new sub-TLVs to the sub-TLVs for 427 TLVs 22, 23, 25, 141, 222, and 223 registry. 429 Value: 41 (suggested - to be assigned by IANA) 431 Name: L2 Bundle Member Adj-SID 433 This sub-TLV is allowed in the following TLVs: 435 22 23 25 141 222 223 436 n n y n n n 438 Value: 42 (suggested to be assigned by IANA) 440 Name: L2 Bundle Member LAN Adj-SID 442 This sub-TLV is allowed in the following TLVs: 444 22 23 25 141 222 223 445 n n y n n n 447 5. Security Considerations 449 None. 451 6. Contributors 453 The following people gave a substantial contribution to the content 454 of this document and should be considered as co-authors: 456 Stefano Previdi 457 Cisco Systems 458 Via Del Serafico 200 459 Rome 0144 460 Italy 462 Email: sprevidi@cisco.com 464 7. Acknowledgements 466 The authors would like to thank Jon MItchell for his careful review. 468 8. References 470 8.1. Normative References 472 [IEEE802.1AX] 473 Institute of Electrical and Electronics Engineers, "IEEE 474 Standard for Local and Metropolitan Area Networks - Link 475 Aggregation.", Nov 2008. 477 [ISO10589] 478 International Organization for Standardization, 479 "Intermediate system to Intermediate system intra-domain 480 routeing information exchange protocol for use in 481 conjunction with the protocol for providing the 482 connectionless-mode Network Service (ISO 8473)", ISO/ 483 IEC 10589:2002, Second Edition, Nov 2002. 485 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 486 Requirement Levels", BCP 14, RFC 2119, 487 DOI 10.17487/RFC2119, March 1997, 488 . 490 [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions 491 in Support of Generalized Multi-Protocol Label Switching 492 (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, 493 . 495 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 496 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 497 2008, . 499 [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions 500 in Support of Generalized Multi-Protocol Label Switching 501 (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, 502 . 504 [RFC6119] Harrison, J., Berger, J., and M. Bartlett, "IPv6 Traffic 505 Engineering in IS-IS", RFC 6119, DOI 10.17487/RFC6119, 506 February 2011, . 508 [SR-ISIS] "IS-IS Extensions for Segment Routing, draft-ietf-isis- 509 segment-routing-extensions-11(work in progress)", April 510 2017. 512 8.2. Informational References 514 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 515 Element (PCE)-Based Architecture", RFC 4655, 516 DOI 10.17487/RFC4655, August 2006, 517 . 519 [SR-ARCH] "Segment Routing Architecture, draft-ietf-spring-segment- 520 routing-11(work in progress)", February 2017. 522 Appendix A. Example Encoding 524 Below is an example encoding of L2 Bundle advertisements in a case 525 where we have two parallel adjacencies to the same neighbor whose 526 system-id is 1234.1234.1234.00. The two L2 bundles have the 527 following sets of attributes: 529 L3 Adjacency #1 530 L3 IPv4 local link address: 1.1.1.1 531 Four bundle members with the following attributes: 533 -------------------------------------------------- 534 Num | Link Local ID | Bandwidth | Adj-SID/Weight | 535 -------------------------------------------------- 536 1 | 0x11111111 | 1G | 0x11111/1 | 537 -------------------------------------------------- 538 2 | 0x11112222 | 1G | 0x11112/1 | 539 -------------------------------------------------- 540 3 | 0x11113333 | 10G | 0x11113/1 | 541 -------------------------------------------------- 542 4 | 0x11114444 | 10G | 0x11114/1 | 543 -------------------------------------------------- 545 L3 Adjacency #2 546 L3 IPv4 local link address: 2.2.2.2 547 Three bundle members with the following attributes: 549 -------------------------------------------------- 550 Num | Link Local ID | Bandwidth | Adj-SID/Weight | 551 -------------------------------------------------- 552 1 | 0x22221111 | 10G | 22221/1 | 553 -------------------------------------------------- 554 2 | 0x22222222 | 10G | 22222/1 | 555 -------------------------------------------------- 556 3 | 0x22223333 | 10G | 22223/1 | 557 -------------------------------------------------- 559 This requires two TLVs, one for each L3 adjacency. 561 TLV for Adjacency #1: 563 0 1 564 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 565 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 566 | Type(25) |Len: 64 | 567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 569 Parent L3 Neighbor Descriptor 570 0 1 2 3 571 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 572 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 573 | Neighbor System-ID octets 1-4: 1234.1234 | 574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 575 | System-ID octets 5-6: 1.2.3.4 | P-node: 00 |1|0|0|0|0|0|0|0| 576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 578 IPv4 Interface Address sub-TLV 579 0 1 580 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 581 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 582 | Type(6)) | Length(4) | 583 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 584 | IPv4 address:1.1.1.1 | 585 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 587 L2 Bundle Attribute Descriptors 588 0 1 2 3 589 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 590 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 591 |Len:9+6+10 = 25| # Desc: 2 | 592 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 593 | Link Local Identifier Bundle Member #1: 0x11111111 | 594 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 595 | Link Local Identifier Bundle Member #2: 0x11112222 | 596 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 Maximum Link Bandwidth sub-TLV 599 0 1 2 3 600 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 601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 602 | Type(9) | Length(4) | 603 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 604 | Bandwidth Value: 1G/8 | 605 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 607 L2 Bundle Member Adjacency Segment Identifier sub-TLV 608 0 1 2 3 609 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 610 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 611 | Type(41) | Length(8) |0|0|1|1|0|0|0|0| Weight: 1 | 612 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 613 | Local Label Bundle Member #1: 0x11111 | 614 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 615 | Local Label Bundle Member #2: 0x11112 | 616 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 618 L2 Bundle Attribute Descriptors 619 0 1 2 3 620 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 621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 622 |Len:9+6+10 = 25| # Desc: 2 | 623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 624 | Link Local Identifier Bundle Member #3: 0x11113333 | 625 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 626 | Link Local Identifier Bundle Member #4: 0x11114444 | 627 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 629 Maximum Link Bandwidth sub-TLV 630 0 1 2 3 631 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 632 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 633 | Type(9) | Length(4) | 634 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 635 | Bandwidth Value: 10G/8 | 636 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 638 L2 Bundle Member Adjacency Segment Identifier sub-TLV 639 0 1 2 3 640 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 641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 642 | Type(41) | Length(8) |0|0|1|1|0|0|0|0| Weight: 1 | 643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 644 | Local Label Bundle Member #3: 0x11113 | 645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 646 | Local Label Bundle Member #4: 0x11114 | 647 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 649 TLV for Adjacency #2 651 0 1 652 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 653 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 654 | Type(25) | Len: 43 | 655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 657 Parent L3 Neighbor Descriptor 658 0 1 2 3 659 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 660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 661 | Neighbor System-ID octets 1-4: 1234.1234 | 662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 663 | System-ID octets 5-6: 1.2.3.4 | P-node: 00 |1|0|0|0|0|0|0|0| 664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 666 IPv4 Interface Address sub-TLV 667 0 1 668 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 669 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 670 | Type(6)) | Length(4) | 671 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 672 | IPv4 address: 2.2.2.2 | 673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 675 L2 Bundle Attribute Descriptors 676 0 1 2 3 677 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 678 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 679 |Len:13+6+13=29 | # Desc: 3 | 680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 681 | Link Local Identifier Bundle Member #1: 0x22221111 | 682 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 683 | Link Local Identifier Bundle Member #2: 0x22222222 | 684 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 685 | Link Local Identifier Bundle Member #3: 0x22223333 | 686 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 688 Maximum Link Bandwidth sub-TLV 689 0 1 2 3 690 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 691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 692 | Type(9) | Length(4) | 693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 694 | Bandwidth Value: 10G/8 | 695 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 697 L2 Bundle Member Adjacency Segment Identifier sub-TLV 698 0 1 2 3 699 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 700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 701 | Type(41) | Length(11) |0|0|1|1|0|0|0|0| Weight: 1 | 702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 703 | Local Label Bundle Member #1: 0x22221 | 704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 705 | Local Label Bundle Member #2: 0x22222 | 706 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 707 | Local Label Bundle Member #2: 0x22223 | 708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 710 Authors' Addresses 712 Les Ginsberg 713 Cisco Systems 714 510 McCarthy Blvd. 715 Milpitas, CA 95035 716 USA 718 Email: ginsberg@cisco.com 720 Ahmed Bashandy 721 Cisco Systems 722 170 West Tasman Drive 723 San Jose, Ca 95134 724 US 726 Clarence Filsfils 727 Cisco Systems 729 Email: cf@cisco.com 731 Mohan Nanduri 732 Microsoft 734 Email: mnanduri@microsft.com 736 Ebben Aries 737 Private Contributer 739 Email: exa@dscp.org