idnits 2.17.1 draft-ietf-idr-ls-distribution-impl-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 : ---------------------------------------------------------------------------- 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 (January 29, 2015) is 3347 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-13) exists of draft-ietf-idr-ls-distribution-10 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing H. Gredler, Ed. 3 Internet-Draft B. Rajagopalan 4 Intended status: Informational C. Bowers 5 Expires: August 2, 2015 Juniper Networks, Inc. 6 S. Ray, Ed. 7 M. Bhardwaj 8 Cisco Systems, Inc. 9 January 29, 2015 11 BGP Link-State Information Distribution Implementation Report 12 draft-ietf-idr-ls-distribution-impl-02 14 Abstract 16 This document is an implementation report for the BGP Link-State 17 Information Distribution protocol. The editors did not verify the 18 accuracy of the information provided by respondents. The respondents 19 are experts with the implementations they reported on, and their 20 responses are considered authoritative for the implementations for 21 which their responses represent. Respondents were asked to only use 22 the YES answer if the feature had at least been tested in the lab. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on August 2, 2015. 41 Copyright Notice 43 Copyright (c) 2015 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Implementation Forms . . . . . . . . . . . . . . . . . . . . 3 60 3. NLRI subtypes . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Link NLRI TLV support . . . . . . . . . . . . . . . . . . . . 4 62 5. Node NLRI TLV support . . . . . . . . . . . . . . . . . . . . 7 63 6. Prefix NLRI TLV support . . . . . . . . . . . . . . . . . . . 8 64 7. Interoperable Implementations . . . . . . . . . . . . . . . . 10 65 7.1. Cisco Implementation . . . . . . . . . . . . . . . . . . 10 66 7.2. Juniper Implementation . . . . . . . . . . . . . . . . . 11 67 7.3. OpenDaylight Implementation . . . . . . . . . . . . . . . 11 68 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 69 9. Security considerations . . . . . . . . . . . . . . . . . . . 11 70 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 71 11. Informative References . . . . . . . . . . . . . . . . . . . 11 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 74 1. Introduction 76 In order to share network link-state and traffic engineering 77 information collected with external components using the BGP routing 78 protocol a new BGP Network Layer Reachability Information (NLRI) 79 encoding format is required. 81 This document provides an implementation report for the BGP Link- 82 State Information Distribution NLRI Format as defined in 83 [I-D.ietf-idr-ls-distribution]. 85 The scope of the interoperability test is sucessful encoding and 86 decoding of BGP-LS advertisements. No application specific logic has 87 been verified. 89 The editors did not verify the accuracy of the information provided 90 by respondents or by any alternative means. The respondents are 91 experts with the implementations they reported on, and their 92 responses are considered authoritative for the implementations for 93 which their responses represent. Respondents were asked to only use 94 the YES answer if the feature had at least been tested in the lab. 96 2. Implementation Forms 98 Contact and implementation information for person filling out this 99 form: 101 IOS-XR 102 Name: Manish Bhardwaj 103 Email:manbhard@cisco.com 104 Vendor: Cisco Systems, Inc. 105 Release: IOS-XR 106 Protocol Role: Sender, Receiver, Originator 108 JUNOS 109 Name: Balaji Rajagopalan 110 Email: balajir@juniper.net 111 Vendor: Juniper Networks, Inc. 112 Release: JUNOS 113 Protocol Role: Sender, Receiver, Originator 115 OpenDaylight 116 Name: Dana Kutenicsova 117 Email: dkutenic@cisco.com 118 Vendor: OpenDaylight Project, Inc. 119 Release: ODL Hydrogen 120 Protocol Role: Receiver 122 3. NLRI subtypes 124 Does the implementation support the Network Layer Reachability (NLRI) 125 subtypes as described in Section 3.2 of 126 [I-D.ietf-idr-ls-distribution] ? 128 N1: Node NLRI 130 N2: Link NLRI 132 N3: IPv4 Topology Prefix NLRI 134 N4: IPv6 Topology Prefix NLRI 135 +--------+--------+-------+-----+ 136 | | IOS-XR | JUNOS | ODL | 137 +--------+--------+-------+-----+ 138 | Rcv.N1 | YES | YES | YES | 139 | Snd.N1 | YES | YES | NO | 140 | Org.N1 | YES | YES | NO | 141 | Rcv.N2 | YES | YES | YES | 142 | Snd.N2 | YES | YES | NO | 143 | Org.N2 | YES | YES | NO | 144 | Rcv.N3 | YES | YES | YES | 145 | Snd.N3 | YES | YES | NO | 146 | Org.N3 | YES | NO | NO | 147 | Rcv.N4 | YES | YES | YES | 148 | Snd.N4 | YES | YES | NO | 149 | Org.N4 | YES | NO | NO | 150 +--------+--------+-------+-----+ 152 4. Link NLRI TLV support 154 Does the implementation support the TLVs described in Section 7 of 155 [I-D.ietf-idr-ls-distribution] ? 157 TLV 256: Local Node Descriptor 159 TLV 257: Remote Node Descriptor 161 TLV 258: Link Local/Remote Identifier 163 TLV 259: IPv4 Interface address 165 TLV 260: IPv4 Neighbor address 167 TLV 261: IPv6 Interface address 169 TLV 262: IPv6 Neighbor address 171 TLV 263: Multi-Topology IDs 173 TLV 512: Autonomous System 175 TLV 513: BGP-LS Identifier 177 TLV 514: Area ID 179 TLV 515: IGP Router ID 181 TLV 1028: IPv4 router-ID of Local Node 182 TLV 1029: IPv6 router-ID of Local Node 184 TLV 1030: IPv4 router-ID of Remote Node 186 TLV 1031: IPv6 router-ID of Remote Node 188 TLV 1088: Administrative group (color) 190 TLV 1089: Maximum link bandwidth 192 TLV 1090: Maximum reservable link bandwidth 194 TLV 1091: Unreserved link bandwidth 196 TLV 1092: TE default Metric 198 TLV 1093: Link Protection Type 200 TLV 1094: MPLS Protocol Mask 202 TLV 1095: IGP Metric 204 TLV 1096: Shared Risk Link Group 206 TLV 1097: Opaque Link attribute 208 TLV 1098: Link name attribute 210 +---------------+--------+-------+-----+ 211 | | IOS-XR | JUNOS | ODL | 212 +---------------+--------+-------+-----+ 213 | Rcv.TLV 256 | YES | YES | YES | 214 | Snd.TLV 256 | YES | YES | NO | 215 | Org.TLV 256 | YES | YES | NO | 216 | Rcv.TLV 257 | YES | YES | YES | 217 | Snd.TLV 257 | YES | YES | NO | 218 | Org.TLV 257 | YES | YES | NO | 219 | Rcv.TLV 258 | YES | YES | YES | 220 | Snd.TLV 258 | YES | YES | NO | 221 | Org.TLV 258 | YES | YES | NO | 222 | Rcv.TLV 259 | YES | YES | YES | 223 | Snd.TLV 259 | YES | YES | NO | 224 | Org.TLV 259 | YES | YES | NO | 225 | Rcv.TLV 260 | YES | YES | YES | 226 | Snd.TLV 260 | YES | YES | NO | 227 | Org.TLV 260 | YES | YES | NO | 228 | Rcv.TLV 261 | YES | YES | YES | 229 | Snd.TLV 261 | YES | YES | NO | 230 | Org.TLV 261 | NO | NO | NO | 231 | Rcv.TLV 262 | YES | YES | YES | 232 | Snd.TLV 262 | YES | YES | NO | 233 | Org.TLV 262 | NO | NO | NO | 234 | Rcv.TLV 263 | YES | YES | YES | 235 | Snd.TLV 263 | YES | YES | NO | 236 | Org.TLV 263 | YES | NO | NO | 237 | Rcv.TLV 512 | YES | YES | YES | 238 | Snd.TLV 512 | YES | YES | NO | 239 | Org.TLV 512 | YES | YES | NO | 240 | Rcv.TLV 513 | YES | YES | YES | 241 | Snd.TLV 513 | YES | YES | NO | 242 | Org.TLV 513 | YES | YES | NO | 243 | Rcv.TLV 514 | YES | YES | YES | 244 | Snd.TLV 514 | YES | YES | NO | 245 | Org.TLV 514 | YES | YES | NO | 246 | Rcv.TLV 515 | YES | YES | YES | 247 | Snd.TLV 515 | YES | YES | NO | 248 | Org.TLV 515 | YES | YES | NO | 249 | Rcv.TLV 1028 | YES | YES | YES | 250 | Snd.TLV 1028 | YES | YES | NO | 251 | Org.TLV 1028 | YES | YES | NO | 252 | Rcv.TLV 1029 | YES | YES | YES | 253 | Snd.TLV 1029 | YES | YES | NO | 254 | Org.TLV 1029 | YES | NO | NO | 255 | Rcv.TLV 1030 | YES | YES | YES | 256 | Snd.TLV 1030 | YES | YES | NO | 257 | Org.TLV 1030 | YES | YES | NO | 258 | Rcv.TLV 1031 | YES | YES | YES | 259 | Snd.TLV 1031 | YES | YES | NO | 260 | Org.TLV 1031 | YES | NO | NO | 261 | Rcv.TLV 1088 | YES | YES | YES | 262 | Snd.TLV 1088 | YES | YES | NO | 263 | Org.TLV 1088 | YES | YES | NO | 264 | Rcv.TLV 1089 | YES | YES | YES | 265 | Snd.TLV 1089 | YES | YES | NO | 266 | Org.TLV 1089 | YES | YES | NO | 267 | Rcv.TLV 1090 | YES | YES | YES | 268 | Snd.TLV 1090 | YES | YES | NO | 269 | Org.TLV 1090 | YES | YES | NO | 270 | Rcv.TLV 1091 | YES | YES | YES | 271 | Snd.TLV 1091 | YES | YES | NO | 272 | Org.TLV 1091 | YES | YES | NO | 273 | Rcv.TLV 1092 | YES | YES | YES | 274 | Snd.TLV 1092 | YES | YES | NO | 275 | Org.TLV 1092 | YES | YES | NO | 276 | Rcv.TLV 1093 | YES | YES | YES | 277 | Snd.TLV 1093 | YES | YES | NO | 278 | Org.TLV 1093 | NO | NO | NO | 279 | Rcv.TLV 1094 | YES | YES | YES | 280 | Snd.TLV 1094 | YES | YES | NO | 281 | Org.TLV 1094 | YES | NO | NO | 282 | Rcv.TLV 1095 | YES | YES | YES | 283 | Snd.TLV 1095 | YES | YES | NO | 284 | Org.TLV 1095 | YES | YES | NO | 285 | Rcv.TLV 1096 | YES | YES | YES | 286 | Snd.TLV 1096 | YES | YES | NO | 287 | Org.TLV 1096 | YES | YES | NO | 288 | Rcv.TLV 1097 | YES | YES | NO | 289 | Snd.TLV 1097 | YES | YES | NO | 290 | Org.TLV 1097 | YES | NO | NO | 291 | Rcv.TLV 1098 | YES | YES | YES | 292 | Snd.TLV 1098 | YES | YES | NO | 293 | Org.TLV 1098 | NO | NO | NO | 294 +---------------+--------+-------+-----+ 296 5. Node NLRI TLV support 298 Does the implementation support the TLVs described in Section 7 of 299 [I-D.ietf-idr-ls-distribution] ? 301 TLV 256: Local Node Descriptor 303 TLV 263: Multi-Topology IDs 305 TLV 512: Autonomous System 307 TLV 513: BGP-LS Identifier 309 TLV 514: Area ID 311 TLV 515: IGP Router ID 313 TLV 1024: Node flag bits 315 TLV 1025: Opaque Node properties 317 TLV 1026: Node name 319 TLV 1027: IS-IS Area Identifier 321 TLV 1028: IPv4 router-ID of Local Node 323 TLV 1029: IPv6 router-ID of Local Node 324 +---------------+--------+-------+-----+ 325 | | IOS-XR | JUNOS | ODL | 326 +---------------+--------+-------+-----+ 327 | Rcv.TLV 256 | YES | YES | YES | 328 | Snd.TLV 256 | YES | YES | NO | 329 | Org.TLV 256 | YES | YES | NO | 330 | Rcv.TLV 263 | YES | YES | YES | 331 | Snd.TLV 263 | YES | YES | NO | 332 | Org.TLV 263 | YES | NO | NO | 333 | Rcv.TLV 512 | YES | YES | YES | 334 | Snd.TLV 512 | YES | YES | NO | 335 | Org.TLV 512 | YES | YES | NO | 336 | Rcv.TLV 513 | YES | YES | YES | 337 | Snd.TLV 513 | YES | YES | NO | 338 | Org.TLV 513 | YES | YES | NO | 339 | Rcv.TLV 514 | YES | YES | YES | 340 | Snd.TLV 514 | YES | YES | NO | 341 | Org.TLV 514 | YES | YES | NO | 342 | Rcv.TLV 515 | YES | YES | YES | 343 | Snd.TLV 515 | YES | YES | NO | 344 | Org.TLV 515 | YES | YES | NO | 345 | Rcv.TLV 1024 | YES | YES | YES | 346 | Snd.TLV 1024 | YES | YES | NO | 347 | Org.TLV 1024 | YES | YES | NO | 348 | Rcv.TLV 1025 | YES | YES | NO | 349 | Snd.TLV 1025 | YES | YES | NO | 350 | Org.TLV 1025 | YES | NO | NO | 351 | Rcv.TLV 1026 | YES | YES | YES | 352 | Snd.TLV 1026 | YES | YES | NO | 353 | Org.TLV 1026 | YES | NO | NO | 354 | Rcv.TLV 1027 | YES | YES | YES | 355 | Snd.TLV 1027 | YES | YES | NO | 356 | Org.TLV 1027 | YES | NO | NO | 357 | Rcv.TLV 1028 | YES | YES | YES | 358 | Snd.TLV 1028 | YES | YES | NO | 359 | Org.TLV 1028 | YES | YES | NO | 360 | Rcv.TLV 1029 | YES | YES | YES | 361 | Snd.TLV 1029 | YES | YES | NO | 362 | Org.TLV 1029 | YES | NO | NO | 363 +---------------+--------+-------+-----+ 365 6. Prefix NLRI TLV support 367 Does the implementation support the TLVs described in Section 7 of 368 [I-D.ietf-idr-ls-distribution] ? 370 TLV 256: Local Node Descriptor 371 TLV 263: Multi-Topology IDs 373 TLV 264: OSPF route type 375 TLV 265: IP Reachability information 377 TLV 1152: IGP Flags 379 TLV 1153: Route Tag 381 TLV 1154: Extended Tag 383 TLV 1155: Prefix Metric 385 TLV 1156: OSPF Forwarding Address 387 TLV 1157: Opaque Prefix Atrribute 388 +---------------+--------+-------+-----+ 389 | | IOS-XR | JUNOS | ODL | 390 +---------------+--------+-------+-----+ 391 | Rcv.TLV 256 | YES | YES | YES | 392 | Snd.TLV 256 | YES | YES | NO | 393 | Org.TLV 256 | YES | NO | NO | 394 | Rcv.TLV 263 | YES | YES | YES | 395 | Snd.TLV 263 | YES | YES | NO | 396 | Org.TLV 263 | YES | NO | NO | 397 | Rcv.TLV 264 | YES | YES | YES | 398 | Snd.TLV 264 | YES | YES | NO | 399 | Org.TLV 264 | YES | NO | NO | 400 | Rcv.TLV 265 | YES | YES | YES | 401 | Snd.TLV 265 | YES | YES | NO | 402 | Org.TLV 265 | YES | NO | NO | 403 | Rcv.TLV 1152 | YES | YES | YES | 404 | Snd.TLV 1152 | YES | YES | NO | 405 | Org.TLV 1152 | YES | NO | NO | 406 | Rcv.TLV 1153 | YES | YES | YES | 407 | Snd.TLV 1153 | YES | YES | NO | 408 | Org.TLV 1153 | YES | NO | NO | 409 | Rcv.TLV 1154 | YES | YES | YES | 410 | Snd.TLV 1154 | YES | YES | NO | 411 | Org.TLV 1154 | NO | NO | NO | 412 | Rcv.TLV 1155 | YES | YES | YES | 413 | Snd.TLV 1155 | YES | YES | NO | 414 | Org.TLV 1155 | YES | NO | NO | 415 | Rcv.TLV 1156 | YES | YES | YES | 416 | Snd.TLV 1156 | YES | YES | NO | 417 | Org.TLV 1156 | YES | NO | NO | 418 | Rcv.TLV 1157 | YES | YES | NO | 419 | Snd.TLV 1157 | YES | YES | NO | 420 | Org.TLV 1157 | YES | NO | NO | 421 +---------------+--------+-------+-----+ 423 7. Interoperable Implementations 425 List other implementations that you have tested interoperability of 426 BGP-LS Protocol Implementation. 428 7.1. Cisco Implementation 430 Cisco: The Cisco Systems, Inc. IOS-XR implementation should be 431 interoperable with other vendor BGP-LS Protocol implementations. In 432 particular, we have tested our interoperability with Juniper's JUNOS 433 implementation. 435 7.2. Juniper Implementation 437 Juniper: The Juniper Networks, Inc. JUNOS implementation should be 438 interoperable with other vendor BGP-LS Protocol implementations. In 439 particular, we have tested our interoperability with the Cisco 440 Systems, Inc. IOS-XR implementation and the Opendaylight 441 implementation. 443 7.3. OpenDaylight Implementation 445 Opendaylight: The Opendaylight implementation should be interoperable 446 with other vendor BGP-LS Protocol implementations. In particular, we 447 have tested our interoperability with Juniper's JUNOS implementation 448 and the Cisco Systems, Inc. IOS-XR implementation. BGP receiver is 449 implemented in the OpenDaylight Hydrogen release. BGP sender 450 functionality is planned in the upcoming Helium release. 452 8. IANA Considerations 454 This document makes no request of IANA. 456 Note to RFC Editor: The IANA has requested that this section remain 457 in the document upon publication as an RFC. This note to the RFC 458 Editor, however, may be removed. 460 9. Security considerations 462 No new security issues are introduced by the BGP Link-State 463 Information Distribution Protocol defined in 464 [I-D.ietf-idr-ls-distribution]. 466 10. Acknowledgements 468 The authors would like to thank Stefano Previdi and Jan Medved for 469 their contributions to this document. 471 11. Informative References 473 [I-D.ietf-idr-ls-distribution] 474 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 475 Ray, "North-Bound Distribution of Link-State and TE 476 Information using BGP", draft-ietf-idr-ls-distribution-10 477 (work in progress), January 2015. 479 Authors' Addresses 481 Hannes Gredler (editor) 482 Juniper Networks, Inc. 483 1194 N. Mathilda Ave. 484 Sunnyvale, CA 94089 485 US 487 Email: hannes@juniper.net 489 Balaji Rajagopalan 490 Juniper Networks, Inc. 491 Electra, Exora Business Park, Marathahalli - Sarjapur Outer Ring Road 492 Bangalore, Karnataka 560103 493 India 495 Email: balajir@juniper.net 497 Chris Bowers 498 Juniper Networks, Inc. 499 1194 N. Mathilda Ave. 500 Sunnyvale, CA 94089 501 US 503 Email: cbowers@juniper.net 505 Saikat Ray (editor) 506 Cisco Systems, Inc. 507 170, West Tasman Drive 508 San Jose, CA 95134 509 US 511 Email: sairay@cisco.com 513 Manish Bhardwaj 514 Cisco Systems, Inc. 515 170, West Tasman Drive 516 San Jose, CA 95134 517 US 519 Email: manbhard@cisco.com