idnits 2.17.1 draft-ietf-idr-ls-distribution-impl-00.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([I-D.ietf-idr-ls-distribution]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 4, 2014) is 3556 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-05 Summary: 1 error (**), 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 Juniper Networks, Inc. 5 Expires: January 5, 2015 S. Ray, Ed. 6 M. Bhardwaj 7 Cisco Systems, Inc. 8 July 4, 2014 10 BGP Link-State Information Distribution Implementation Report 11 draft-ietf-idr-ls-distribution-impl-00 13 Abstract 15 This document is an implementation report for the BGP Link-State 16 Information Distribution protocol as defined in 17 [I-D.ietf-idr-ls-distribution]. 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 January 5, 2015. 41 Copyright Notice 43 Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Implementation Forms . . . . . . . . . . . . . . . . . . . . . 3 60 3. NLRI subtypes . . . . . . . . . . . . . . . . . . . . . . . . 4 61 4. Link NLRI TLV support . . . . . . . . . . . . . . . . . . . . 4 62 5. Node NLRI TLV support . . . . . . . . . . . . . . . . . . . . 7 63 6. Prefix NLRI TLV support . . . . . . . . . . . . . . . . . . . 9 64 7. Interoperable Implementations . . . . . . . . . . . . . . . . 11 65 7.1. Cisco Implementation . . . . . . . . . . . . . . . . . . . 11 66 7.2. Juniper Implementation . . . . . . . . . . . . . . . . . . 12 67 7.3. OpenDaylight Implementation . . . . . . . . . . . . . . . 12 68 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 69 9. Security considerations . . . . . . . . . . . . . . . . . . . 12 70 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 71 11. Informative References . . . . . . . . . . . . . . . . . . . . 12 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 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 editors did not verify the accuracy of the information provided 86 by respondents or by any alternative means. The respondents are 87 experts with the implementations they reported on, and their 88 responses are considered authoritative for the implementations for 89 which their responses represent. Respondents were asked to only use 90 the YES answer if the feature had at least been tested in the lab. 92 2. Implementation Forms 94 Contact and implementation information for person filling out this 95 form: 97 IOS-XR 98 Name: Manish Bhardwaj 99 Email:manbhard@cisco.com 100 Vendor: Cisco Systems, Inc. 101 Release: IOS-XR 102 Protocol Role: Sender, Receiver, Originator 104 JUNOS 105 Name: Balaji Rajagopalan 106 Email: balajir@juniper.net 107 Vendor: Juniper Networks, Inc. 108 Release: JUNOS 109 Protocol Role: Sender, Receiver, Originator 111 OpenDaylight 112 Name: Dana Kutenicsova 113 Email: dkutenic@cisco.com 114 Vendor: OpenDaylight Project, Inc. 115 Release: ODL Hydrogen 116 Protocol Role: Receiver 118 3. NLRI subtypes 120 Does the implementation support the Network Layer Reachability (NLRI) 121 subtypes as described in Section 3.2 of 122 [I-D.ietf-idr-ls-distribution] ? 124 N1: Node NLRI 126 N2: Link NLRI 128 N3: IPv4 Topology Prefix NLRI 130 N4: IPv6 Topology Prefix NLRI 132 +--------+--------+-------+-----+ 133 | | IOS-XR | JUNOS | ODL | 134 +--------+--------+-------+-----+ 135 | Rcv.N1 | YES | YES | YES | 136 | Snd.N1 | YES | YES | NO | 137 | Org.N1 | YES | YES | NO | 138 | Rcv.N2 | YES | YES | YES | 139 | Snd.N2 | YES | YES | NO | 140 | Org.N2 | YES | YES | NO | 141 | Rcv.N3 | YES | YES | YES | 142 | Snd.N3 | YES | YES | NO | 143 | Org.N3 | YES | NO | NO | 144 | Rcv.N4 | YES | YES | YES | 145 | Snd.N4 | YES | YES | NO | 146 | Org.N4 | YES | NO | NO | 147 +--------+--------+-------+-----+ 149 4. Link NLRI TLV support 151 Does the implementation support the TLVs described in Section 7 of 152 [I-D.ietf-idr-ls-distribution] ? 154 TLV 256: Local Node Descriptor 156 TLV 257: Remote Node Descriptor 158 TLV 258: Link Local/Remote Identifier 160 TLV 259: IPv4 Interface address 161 TLV 260: IPv4 Neighbor address 163 TLV 261: IPv6 Interface address 165 TLV 262: IPv6 Neighbor address 167 TLV 263: Multi-Topology IDs 169 TLV 512: Autonomous System 171 TLV 513: BGP-LS Identifier 173 TLV 514: Area ID 175 TLV 515: IGP Router ID 177 TLV 1028: IPv4 router-ID of Local Node 179 TLV 1029: IPv6 router-ID of Local Node 181 TLV 1030: IPv4 router-ID of Remote Node 183 TLV 1031: IPv6 router-ID of Remote Node 185 TLV 1088: Administrative group (color) 187 TLV 1089: Maximum link bandwidth 189 TLV 1090: Maximum reservable link bandwidth 191 TLV 1091: Unreserved link bandwidth 193 TLV 1092: TE default Metric 195 TLV 1093: Link Protection Type 197 TLV 1094: MPLS Protocol Mask 199 TLV 1095: IGP Metric 201 TLV 1096: Shared Risk Link Group 203 TLV 1097: Opaque Link attribute 205 TLV 1098: Link name attribute 206 +--------------+--------+-------+-----+ 207 | | IOS-XR | JUNOS | ODL | 208 +--------------+--------+-------+-----+ 209 | Rcv.TLV 256 | YES | YES | YES | 210 | Snd.TLV 256 | YES | YES | NO | 211 | Org.TLV 256 | YES | YES | NO | 212 | Rcv.TLV 257 | YES | YES | YES | 213 | Snd.TLV 257 | YES | YES | NO | 214 | Org.TLV 257 | YES | YES | NO | 215 | Rcv.TLV 258 | YES | YES | YES | 216 | Snd.TLV 258 | YES | YES | NO | 217 | Org.TLV 258 | YES | YES | NO | 218 | Rcv.TLV 259 | YES | YES | YES | 219 | Snd.TLV 259 | YES | YES | NO | 220 | Org.TLV 259 | YES | YES | NO | 221 | Rcv.TLV 260 | YES | YES | YES | 222 | Snd.TLV 260 | YES | YES | NO | 223 | Org.TLV 260 | YES | YES | NO | 224 | Rcv.TLV 261 | YES | YES | YES | 225 | Snd.TLV 261 | YES | YES | NO | 226 | Org.TLV 261 | NO | NO | NO | 227 | Rcv.TLV 262 | YES | YES | YES | 228 | Snd.TLV 262 | YES | YES | NO | 229 | Org.TLV 262 | NO | NO | NO | 230 | Rcv.TLV 263 | YES | YES | YES | 231 | Snd.TLV 263 | YES | YES | NO | 232 | Org.TLV 263 | YES | NO | NO | 233 | Rcv.TLV 512 | YES | YES | YES | 234 | Snd.TLV 512 | YES | YES | NO | 235 | Org.TLV 512 | YES | YES | NO | 236 | Rcv.TLV 513 | YES | YES | YES | 237 | Snd.TLV 513 | YES | YES | NO | 238 | Org.TLV 513 | YES | YES | NO | 239 | Rcv.TLV 514 | YES | YES | YES | 240 | Snd.TLV 514 | YES | YES | NO | 241 | Org.TLV 514 | YES | YES | NO | 242 | Rcv.TLV 515 | YES | YES | YES | 243 | Snd.TLV 515 | YES | YES | NO | 244 | Org.TLV 515 | YES | YES | NO | 245 | Rcv.TLV 1028 | YES | YES | YES | 246 | Snd.TLV 1028 | YES | YES | NO | 247 | Org.TLV 1028 | YES | YES | NO | 248 | Rcv.TLV 1029 | YES | YES | YES | 249 | Snd.TLV 1029 | YES | YES | NO | 250 | Org.TLV 1029 | YES | NO | NO | 251 | Rcv.TLV 1030 | YES | YES | YES | 252 | Snd.TLV 1030 | YES | YES | NO | 253 | Org.TLV 1030 | YES | YES | NO | 254 | Rcv.TLV 1031 | YES | YES | YES | 255 | Snd.TLV 1031 | YES | YES | NO | 256 | Org.TLV 1031 | YES | NO | NO | 257 | Rcv.TLV 1088 | YES | YES | YES | 258 | Snd.TLV 1088 | YES | YES | NO | 259 | Org.TLV 1088 | YES | YES | NO | 260 | Rcv.TLV 1089 | YES | YES | YES | 261 | Snd.TLV 1089 | YES | YES | NO | 262 | Org.TLV 1089 | YES | YES | NO | 263 | Rcv.TLV 1090 | YES | YES | YES | 264 | Snd.TLV 1090 | YES | YES | NO | 265 | Org.TLV 1090 | YES | YES | NO | 266 | Rcv.TLV 1091 | YES | YES | YES | 267 | Snd.TLV 1091 | YES | YES | NO | 268 | Org.TLV 1091 | YES | YES | NO | 269 | Rcv.TLV 1092 | YES | YES | YES | 270 | Snd.TLV 1092 | YES | YES | NO | 271 | Org.TLV 1092 | YES | YES | NO | 272 | Rcv.TLV 1093 | YES | YES | YES | 273 | Snd.TLV 1093 | YES | YES | NO | 274 | Org.TLV 1093 | NO | NO | NO | 275 | Rcv.TLV 1094 | YES | YES | YES | 276 | Snd.TLV 1094 | YES | YES | NO | 277 | Org.TLV 1094 | YES | NO | NO | 278 | Rcv.TLV 1095 | YES | YES | YES | 279 | Snd.TLV 1095 | YES | YES | NO | 280 | Org.TLV 1095 | YES | YES | NO | 281 | Rcv.TLV 1096 | YES | YES | YES | 282 | Snd.TLV 1096 | YES | YES | NO | 283 | Org.TLV 1096 | YES | YES | NO | 284 | Rcv.TLV 1097 | YES | YES | NO | 285 | Snd.TLV 1097 | YES | YES | NO | 286 | Org.TLV 1097 | YES | NO | NO | 287 | Rcv.TLV 1098 | YES | YES | YES | 288 | Snd.TLV 1098 | YES | YES | NO | 289 | Org.TLV 1098 | NO | NO | NO | 290 +--------------+--------+-------+-----+ 292 5. Node NLRI TLV support 294 Does the implementation support the TLVs described in Section 7 of 295 [I-D.ietf-idr-ls-distribution] ? 296 TLV 256: Local Node Descriptor 298 TLV 263: Multi-Topology IDs 300 TLV 512: Autonomous System 302 TLV 513: BGP-LS Identifier 304 TLV 514: Area ID 306 TLV 515: IGP Router ID 308 TLV 1024: Node flag bits 310 TLV 1025: Opaque Node properties 312 TLV 1026: Node name 314 TLV 1027: IS-IS Area Identifier 316 TLV 1028: IPv4 router-ID of Local Node 318 TLV 1029: IPv6 router-ID of Local Node 319 +--------------+--------+-------+-----+ 320 | | IOS-XR | JUNOS | ODL | 321 +--------------+--------+-------+-----+ 322 | Rcv.TLV 256 | YES | YES | YES | 323 | Snd.TLV 256 | YES | YES | NO | 324 | Org.TLV 256 | YES | YES | NO | 325 | Rcv.TLV 263 | YES | YES | YES | 326 | Snd.TLV 263 | YES | YES | NO | 327 | Org.TLV 263 | YES | NO | NO | 328 | Rcv.TLV 512 | YES | YES | YES | 329 | Snd.TLV 512 | YES | YES | NO | 330 | Org.TLV 512 | YES | YES | NO | 331 | Rcv.TLV 513 | YES | YES | YES | 332 | Snd.TLV 513 | YES | YES | NO | 333 | Org.TLV 513 | YES | YES | NO | 334 | Rcv.TLV 514 | YES | YES | YES | 335 | Snd.TLV 514 | YES | YES | NO | 336 | Org.TLV 514 | YES | YES | NO | 337 | Rcv.TLV 515 | YES | YES | YES | 338 | Snd.TLV 515 | YES | YES | NO | 339 | Org.TLV 515 | YES | YES | NO | 340 | Rcv.TLV 1024 | YES | YES | YES | 341 | Snd.TLV 1024 | YES | YES | NO | 342 | Org.TLV 1024 | YES | YES | NO | 343 | Rcv.TLV 1025 | YES | YES | NO | 344 | Snd.TLV 1025 | YES | YES | NO | 345 | Org.TLV 1025 | YES | NO | NO | 346 | Rcv.TLV 1026 | YES | YES | YES | 347 | Snd.TLV 1026 | YES | YES | NO | 348 | Org.TLV 1026 | YES | NO | NO | 349 | Rcv.TLV 1027 | YES | YES | YES | 350 | Snd.TLV 1027 | YES | YES | NO | 351 | Org.TLV 1027 | YES | NO | NO | 352 | Rcv.TLV 1028 | YES | YES | YES | 353 | Snd.TLV 1028 | YES | YES | NO | 354 | Org.TLV 1028 | YES | YES | NO | 355 | Rcv.TLV 1029 | YES | YES | YES | 356 | Snd.TLV 1029 | YES | YES | NO | 357 | Org.TLV 1029 | YES | NO | NO | 358 +--------------+--------+-------+-----+ 360 6. Prefix NLRI TLV support 362 Does the implementation support the TLVs described in Section 7 of 363 [I-D.ietf-idr-ls-distribution] ? 364 TLV 256: Local Node Descriptor 366 TLV 263: Multi-Topology IDs 368 TLV 264: OSPF route type 370 TLV 265: IP Reachability information 372 TLV 1152: IGP Flags 374 TLV 1153: Route Tag 376 TLV 1154: Extended Tag 378 TLV 1155: Prefix Metric 380 TLV 1156: OSPF Forwarding Address 382 TLV 1157: Opaque Prefix Atrribute 383 +--------------+--------+-------+-----+ 384 | | IOS-XR | JUNOS | ODL | 385 +--------------+--------+-------+-----+ 386 | Rcv.TLV 256 | YES | YES | YES | 387 | Snd.TLV 256 | YES | YES | NO | 388 | Org.TLV 256 | YES | NO | NO | 389 | Rcv.TLV 263 | YES | YES | YES | 390 | Snd.TLV 263 | YES | YES | NO | 391 | Org.TLV 263 | YES | NO | NO | 392 | Rcv.TLV 264 | YES | YES | YES | 393 | Snd.TLV 264 | YES | YES | NO | 394 | Org.TLV 264 | YES | NO | NO | 395 | Rcv.TLV 265 | YES | YES | YES | 396 | Snd.TLV 265 | YES | YES | NO | 397 | Org.TLV 265 | YES | NO | NO | 398 | Rcv.TLV 1152 | YES | YES | YES | 399 | Snd.TLV 1152 | YES | YES | NO | 400 | Org.TLV 1152 | YES | NO | NO | 401 | Rcv.TLV 1153 | YES | YES | YES | 402 | Snd.TLV 1153 | YES | YES | NO | 403 | Org.TLV 1153 | YES | NO | NO | 404 | Rcv.TLV 1154 | YES | YES | YES | 405 | Snd.TLV 1154 | YES | YES | NO | 406 | Org.TLV 1154 | NO | NO | NO | 407 | Rcv.TLV 1155 | YES | YES | YES | 408 | Snd.TLV 1155 | YES | YES | NO | 409 | Org.TLV 1155 | YES | NO | NO | 410 | Rcv.TLV 1156 | YES | YES | YES | 411 | Snd.TLV 1156 | YES | YES | NO | 412 | Org.TLV 1156 | YES | NO | NO | 413 | Rcv.TLV 1157 | YES | YES | NO | 414 | Snd.TLV 1157 | YES | YES | NO | 415 | Org.TLV 1157 | YES | NO | NO | 416 +--------------+--------+-------+-----+ 418 7. Interoperable Implementations 420 List other implementations that you have tested interoperability of 421 BGP-LS Protocol Implementation. 423 7.1. Cisco Implementation 425 Cisco: The Cisco Systems, Inc. IOS-XR implementation should be 426 interoperable with other vendor BGP-LS Protocol implementations. In 427 particular, we have tested our interoperability with Juniper's JUNOS 428 implementation. 430 7.2. Juniper Implementation 432 Juniper: The Juniper Networks, Inc. JUNOS implementation should be 433 interoperable with other vendor BGP-LS Protocol implementations. In 434 particular, we have tested our interoperability with Cisco Systems, 435 Inc. IOS-XR implementation and the Opendaylight implementation. 437 7.3. OpenDaylight Implementation 439 Opendaylight: The Opendaylight implementation should be interoperable 440 with other vendor BGP-LS Protocol implementations. In particular, we 441 have tested our interoperability with Juniper's JUNOS implementation 442 and the Cisco Systems, Inc. IOS-XR implementation. BGP receiver is 443 implemented in OpenDaylight Hydrogen release. BGP sender 444 functionality is planned in upcoming Helium release. 446 8. IANA Considerations 448 This document makes no request of IANA. 450 Note to RFC Editor: The IANA has requested that this section remain 451 in the document upon publication as an RFC. This note to the RFC 452 Editor, however, may be removed. 454 9. Security considerations 456 No new security issues are introduced to the BGP Link-State 457 Information Distribution Protocol defined in 458 [I-D.ietf-idr-ls-distribution]. 460 10. Acknowledgements 462 The authors would like to thank Stefano Previdi, Jan Medved and Chris 463 Bowers for their contributions to this document. 465 11. Informative References 467 [I-D.ietf-idr-ls-distribution] 468 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 469 Ray, "North-Bound Distribution of Link-State and TE 470 Information using BGP", draft-ietf-idr-ls-distribution-05 471 (work in progress), May 2014. 473 Authors' Addresses 475 Hannes Gredler (editor) 476 Juniper Networks, Inc. 477 1194 N. Mathilda Ave. 478 Sunnyvale, CA 94089 479 US 481 Email: hannes@juniper.net 483 Balaji Rajagopalan 484 Juniper Networks, Inc. 485 Electra, Exora Business Park, Marathahalli - Sarjapur Outer Ring Road 486 Bangalore, Karnataka 560103 487 India 489 Email: balajir@juniper.net 491 Saikat Ray (editor) 492 Cisco Systems, Inc. 493 170, West Tasman Drive 494 San Jose, CA 95134 495 US 497 Email: sairay@cisco.com 499 Manish Bhardwaj 500 Cisco Systems, Inc. 501 170, West Tasman Drive 502 San Jose, CA 95134 503 US 505 Email: manbhard@cisco.com