idnits 2.17.1 draft-ietf-idr-ls-distribution-impl-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 (May 2, 2015) is 3254 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 565 == Outdated reference: A later version (-13) exists of draft-ietf-idr-ls-distribution-10 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). 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: November 3, 2015 Juniper Networks, Inc. 6 S. Ray 7 Google 8 M. Bhardwaj 9 Cisco Systems, Inc. 10 May 2, 2015 12 BGP Link-State Information Distribution Implementation Report 13 draft-ietf-idr-ls-distribution-impl-04 15 Abstract 17 This document is an implementation report for the BGP Link-State 18 Information Distribution protocol. The editors did not verify the 19 accuracy of the information provided by respondents. The respondents 20 are experts with the implementations they reported on, and their 21 responses are considered authoritative for the implementations for 22 which their responses represent. Respondents were asked to only use 23 the YES answer if the feature had at least been tested in the lab. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on November 3, 2015. 42 Copyright Notice 44 Copyright (c) 2015 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Implementation Forms . . . . . . . . . . . . . . . . . . . . 3 61 3. NLRI subtypes . . . . . . . . . . . . . . . . . . . . . . . . 4 62 4. Link NLRI TLV support . . . . . . . . . . . . . . . . . . . . 5 63 5. Node NLRI TLV support . . . . . . . . . . . . . . . . . . . . 8 64 6. Prefix NLRI TLV support . . . . . . . . . . . . . . . . . . . 9 65 7. Interoperable Implementations . . . . . . . . . . . . . . . . 11 66 7.1. Cisco Implementation . . . . . . . . . . . . . . . . . . 11 67 7.2. Juniper Implementation . . . . . . . . . . . . . . . . . 12 68 7.3. OpenDaylight Implementation . . . . . . . . . . . . . . . 12 69 7.4. Telecom Italia Implementation . . . . . . . . . . . . . . 12 70 7.5. Netphony Implementation . . . . . . . . . . . . . . . . . 12 71 7.6. CTTC Implementation . . . . . . . . . . . . . . . . . . . 12 72 7.7. CNIT Implementation . . . . . . . . . . . . . . . . . . . 13 73 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 74 9. Security considerations . . . . . . . . . . . . . . . . . . . 13 75 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 76 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 77 11.1. Normative References . . . . . . . . . . . . . . . . . . 13 78 11.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 14 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 81 1. Introduction 83 In order to share network link-state and traffic engineering 84 information collected with external components using the BGP routing 85 protocol a new BGP Network Layer Reachability Information (NLRI) 86 encoding format is required. 88 This document provides an implementation report for the BGP Link- 89 State Information Distribution NLRI Format as defined in 90 [I-D.ietf-idr-ls-distribution]. 92 The scope of the interoperability test is sucessful encoding and 93 decoding of BGP-LS advertisements. No application specific logic has 94 been verified. 96 The editors did not verify the accuracy of the information provided 97 by respondents or by any alternative means. The respondents are 98 experts with the implementations they reported on, and their 99 responses are considered authoritative for the implementations for 100 which their responses represent. Respondents were asked to only use 101 the YES answer if the feature had at least been tested in the lab. 103 2. Implementation Forms 105 Contact and implementation information for person filling out this 106 form: 108 IOS-XR 109 Name: Manish Bhardwaj 110 Email:manbhard@cisco.com 111 Vendor: Cisco Systems, Inc. 112 Release: IOS-XR 113 Protocol Role: Sender, Receiver, Originator 115 JUNOS 116 Name: Balaji Rajagopalan 117 Email: balajir@juniper.net 118 Vendor: Juniper Networks, Inc. 119 Release: JUNOS 120 Protocol Role: Sender, Receiver, Originator 122 OpenDaylight 123 Name: Dana Kutenicsova 124 Email: dkutenic@cisco.com 125 Vendor: OpenDaylight Project, Inc. 126 Release: ODL Hydrogen 127 Protocol Role: Receiver 129 Telecom Italia 130 Name: Roberto Morro 131 Email: roberto.morro@telecomitalia.it 132 Vendor: Telecom Italia, SpA 133 Release: 5.0 134 Protocol Role: Originator 136 Netphony 137 Name: Oscar Gonzalez 138 Email: oscar.gonzalezdedios@telefonica.com 139 Name: Victor Lopez 140 Email: victor.lopezalvarez@telefonica.com 141 Company: Telefonica 142 Release: 1.0.1 143 Protocol role: Sender, Receiver, Originator 145 CTTC 146 Name: Ramon Casellas 147 Email: ramon.casellas@cttc.es 148 Company: CTTC 149 Release: 4.9 (PCE) 150 Protocol role: Sender, Receiver, Originator 152 CNIT 153 Name: Francesco Paolucci 154 Email: fr.paolucci@sssup.it 155 Company: CNIT/Scuola Superiore Sant'Anna 156 Release: IdealistPCE v1.0 157 Protocol role: Originator, Sender 159 3. NLRI subtypes 161 Does the implementation support the Network Layer Reachability (NLRI) 162 subtypes as described in Section 3.2 of 163 [I-D.ietf-idr-ls-distribution] ? 165 N1: Node NLRI 167 N2: Link NLRI 169 N3: IPv4 Topology Prefix NLRI 171 N4: IPv6 Topology Prefix NLRI 172 +--------+--------+-------+-----+-----+------+------+------+ 173 | | IOS-XR | JUNOS | ODL | TI | NPHY | CTTC | CNIT | 174 +--------+--------+-------+-----+-----+------+------+------+ 175 | Rcv.N1 | YES | YES | YES | NO | YES | YES | NO | 176 | Snd.N1 | YES | YES | NO | NO | YES | YES | YES | 177 | Org.N1 | YES | YES | NO | YES | YES | YES | YES | 178 | Rcv.N2 | YES | YES | YES | NO | YES | YES | NO | 179 | Snd.N2 | YES | YES | NO | NO | YES | YES | YES | 180 | Org.N2 | YES | YES | NO | YES | YES | YES | YES | 181 | Rcv.N3 | YES | YES | YES | NO | NO | NO | NO | 182 | Snd.N3 | YES | YES | NO | NO | NO | NO | NO | 183 | Org.N3 | YES | NO | NO | NO | NO | NO | NO | 184 | Rcv.N4 | YES | YES | YES | NO | NO | NO | NO | 185 | Snd.N4 | YES | YES | NO | NO | NO | NO | NO | 186 | Org.N4 | YES | NO | NO | NO | NO | NO | NO | 187 +--------+--------+-------+-----+-----+------+------+------+ 189 4. Link NLRI TLV support 191 Does the implementation support the TLVs described in Section 7 of 192 [I-D.ietf-idr-ls-distribution] ? 194 TLV 256: Local Node Descriptor 196 TLV 257: Remote Node Descriptor 198 TLV 258: Link Local/Remote Identifier 200 TLV 259: IPv4 Interface address 202 TLV 260: IPv4 Neighbor address 204 TLV 261: IPv6 Interface address 206 TLV 262: IPv6 Neighbor address 208 TLV 263: Multi-Topology IDs 210 TLV 512: Autonomous System 212 TLV 513: BGP-LS Identifier 214 TLV 514: Area ID 216 TLV 515: IGP Router ID 218 TLV 1028: IPv4 router-ID of Local Node 219 TLV 1029: IPv6 router-ID of Local Node 221 TLV 1030: IPv4 router-ID of Remote Node 223 TLV 1031: IPv6 router-ID of Remote Node 225 TLV 1088: Administrative group (color) 227 TLV 1089: Maximum link bandwidth 229 TLV 1090: Maximum reservable link bandwidth 231 TLV 1091: Unreserved link bandwidth 233 TLV 1092: TE default Metric 235 TLV 1093: Link Protection Type 237 TLV 1094: MPLS Protocol Mask 239 TLV 1095: IGP Metric 241 TLV 1096: Shared Risk Link Group 243 TLV 1097: Opaque Link attribute 245 TLV 1098: Link name attribute 247 +---------------+--------+-------+-----+-----+------+------+------+ 248 | | IOS-XR | JUNOS | ODL | TI | NPHY | CTTC | CNIT | 249 +---------------+--------+-------+-----+-----+------+------+------+ 250 | Rcv.TLV 256 | YES | YES | YES | NO | YES | YES | NO | 251 | Snd.TLV 256 | YES | YES | NO | NO | YES | YES | YES | 252 | Org.TLV 256 | YES | YES | NO | YES | YES | YES | YES | 253 | Rcv.TLV 257 | YES | YES | YES | NO | YES | YES | NO | 254 | Snd.TLV 257 | YES | YES | NO | NO | YES | YES | YES | 255 | Org.TLV 257 | YES | YES | NO | YES | YES | YES | YES | 256 | Rcv.TLV 258 | YES | YES | YES | NO | YES | YES | NO | 257 | Snd.TLV 258 | YES | YES | NO | NO | YES | YES | YES | 258 | Org.TLV 258 | YES | YES | NO | YES | YES | YES | YES | 259 | Rcv.TLV 259 | YES | YES | YES | NO | NO | NO | NO | 260 | Snd.TLV 259 | YES | YES | NO | NO | NO | NO | NO | 261 | Org.TLV 259 | YES | YES | NO | NO | NO | NO | NO | 262 | Rcv.TLV 260 | YES | YES | YES | NO | NO | NO | NO | 263 | Snd.TLV 260 | YES | YES | NO | NO | NO | NO | NO | 264 | Org.TLV 260 | YES | YES | NO | NO | NO | NO | NO | 265 | Rcv.TLV 261 | YES | YES | YES | NO | NO | NO | NO | 266 | Snd.TLV 261 | YES | YES | NO | NO | NO | NO | NO | 267 | Org.TLV 261 | NO | NO | NO | NO | NO | NO | NO | 268 | Rcv.TLV 262 | YES | YES | YES | NO | NO | NO | NO | 269 | Snd.TLV 262 | YES | YES | NO | NO | NO | NO | NO | 270 | Org.TLV 262 | NO | NO | NO | NO | NO | NO | NO | 271 | Rcv.TLV 263 | YES | YES | YES | NO | NO | NO | NO | 272 | Snd.TLV 263 | YES | YES | NO | NO | NO | NO | NO | 273 | Org.TLV 263 | YES | NO | NO | NO | NO | NO | NO | 274 | Rcv.TLV 512 | YES | YES | YES | NO | YES | YES | NO | 275 | Snd.TLV 512 | YES | YES | NO | NO | YES | YES | YES | 276 | Org.TLV 512 | YES | YES | NO | YES | YES | YES | YES | 277 | Rcv.TLV 513 | YES | YES | YES | NO | YES | YES | NO | 278 | Snd.TLV 513 | YES | YES | NO | NO | YES | YES | YES | 279 | Org.TLV 513 | YES | YES | NO | YES | YES | YES | YES | 280 | Rcv.TLV 514 | YES | YES | YES | NO | YES | YES | NO | 281 | Snd.TLV 514 | YES | YES | NO | NO | YES | YES | YES | 282 | Org.TLV 514 | YES | YES | NO | YES | YES | YES | YES | 283 | Rcv.TLV 515 | YES | YES | YES | NO | YES | YES | NO | 284 | Snd.TLV 515 | YES | YES | NO | NO | YES | YES | YES | 285 | Org.TLV 515 | YES | YES | NO | YES | YES | YES | YES | 286 | Rcv.TLV 1028 | YES | YES | YES | NO | YES | NO | NO | 287 | Snd.TLV 1028 | YES | YES | NO | NO | YES | NO | YES | 288 | Org.TLV 1028 | YES | YES | NO | NO | NO | NO | YES | 289 | Rcv.TLV 1029 | YES | YES | YES | NO | YES | NO | NO | 290 | Snd.TLV 1029 | YES | YES | NO | NO | YES | NO | NO | 291 | Org.TLV 1029 | YES | NO | NO | NO | NO | NO | NO | 292 | Rcv.TLV 1030 | YES | YES | YES | NO | YES | NO | NO | 293 | Snd.TLV 1030 | YES | YES | NO | NO | YES | NO | YES | 294 | Org.TLV 1030 | YES | YES | NO | NO | NO | NO | YES | 295 | Rcv.TLV 1031 | YES | YES | YES | NO | YES | NO | NO | 296 | Snd.TLV 1031 | YES | YES | NO | NO | YES | NO | NO | 297 | Org.TLV 1031 | YES | NO | NO | NO | NO | NO | NO | 298 | Rcv.TLV 1088 | YES | YES | YES | NO | YES | YES | NO | 299 | Snd.TLV 1088 | YES | YES | NO | NO | YES | YES | NO | 300 | Org.TLV 1088 | YES | YES | NO | YES | NO | YES | NO | 301 | Rcv.TLV 1089 | YES | YES | YES | NO | YES | YES | NO | 302 | Snd.TLV 1089 | YES | YES | NO | NO | YES | YES | NO | 303 | Org.TLV 1089 | YES | YES | NO | NO | YES | YES | NO | 304 | Rcv.TLV 1090 | YES | YES | YES | NO | YES | YES | NO | 305 | Snd.TLV 1090 | YES | YES | NO | NO | YES | YES | NO | 306 | Org.TLV 1090 | YES | YES | NO | YES | YES | YES | NO | 307 | Rcv.TLV 1091 | YES | YES | YES | NO | YES | YES | NO | 308 | Snd.TLV 1091 | YES | YES | NO | NO | YES | YES | NO | 309 | Org.TLV 1091 | YES | YES | NO | YES | YES | YES | NO | 310 | Rcv.TLV 1092 | YES | YES | YES | NO | YES | YES | NO | 311 | Snd.TLV 1092 | YES | YES | NO | NO | YES | YES | YES | 312 | Org.TLV 1092 | YES | YES | NO | YES | YES | YES | YES | 313 | Rcv.TLV 1093 | YES | YES | YES | NO | YES | NO | NO | 314 | Snd.TLV 1093 | YES | YES | NO | NO | NO | NO | NO | 315 | Org.TLV 1093 | NO | NO | NO | NO | NO | NO | NO | 316 | Rcv.TLV 1094 | YES | YES | YES | NO | NO | NO | NO | 317 | Snd.TLV 1094 | YES | YES | NO | NO | NO | NO | NO | 318 | Org.TLV 1094 | YES | NO | NO | NO | NO | NO | NO | 319 | Rcv.TLV 1095 | YES | YES | YES | NO | NO | NO | NO | 320 | Snd.TLV 1095 | YES | YES | NO | NO | NO | NO | NO | 321 | Org.TLV 1095 | YES | YES | NO | NO | NO | NO | NO | 322 | Rcv.TLV 1096 | YES | YES | YES | NO | NO | NO | NO | 323 | Snd.TLV 1096 | YES | YES | NO | NO | NO | NO | NO | 324 | Org.TLV 1096 | YES | YES | NO | NO | NO | NO | NO | 325 | Rcv.TLV 1097 | YES | YES | NO | NO | NO | NO | NO | 326 | Snd.TLV 1097 | YES | YES | NO | NO | NO | NO | NO | 327 | Org.TLV 1097 | YES | NO | NO | NO | NO | NO | NO | 328 | Rcv.TLV 1098 | YES | YES | YES | NO | NO | NO | NO | 329 | Snd.TLV 1098 | YES | YES | NO | NO | NO | NO | NO | 330 | Org.TLV 1098 | NO | NO | NO | NO | NO | NO | NO | 331 +---------------+--------+-------+-----+-----+------+------+------+ 333 5. Node NLRI TLV support 335 Does the implementation support the TLVs described in Section 7 of 336 [I-D.ietf-idr-ls-distribution] ? 338 TLV 256: Local Node Descriptor 340 TLV 263: Multi-Topology IDs 342 TLV 512: Autonomous System 344 TLV 513: BGP-LS Identifier 346 TLV 514: Area ID 348 TLV 515: IGP Router ID 350 TLV 1024: Node flag bits 352 TLV 1025: Opaque Node properties 354 TLV 1026: Node name 356 TLV 1027: IS-IS Area Identifier 358 TLV 1028: IPv4 router-ID of Local Node 360 TLV 1029: IPv6 router-ID of Local Node 361 +--------------+--------+-------+-----+-----+------+------+------+ 362 | | IOS-XR | JUNOS | ODL | TI | NPHY | CTTC | CNIT | 363 +--------------+--------+-------+-----+-----+------+------+------+ 364 | Rcv.TLV 256 | YES | YES | YES | NO | YES | YES | NO | 365 | Snd.TLV 256 | YES | YES | NO | NO | YES | YES | YES | 366 | Org.TLV 256 | YES | YES | NO | NO | YES | YES | YES | 367 | Rcv.TLV 263 | YES | YES | YES | NO | NO | NO | NO | 368 | Snd.TLV 263 | YES | YES | NO | NO | NO | NO | NO | 369 | Org.TLV 263 | YES | NO | NO | NO | NO | NO | NO | 370 | Rcv.TLV 512 | YES | YES | YES | NO | YES | YES | NO | 371 | Snd.TLV 512 | YES | YES | NO | NO | YES | YES | YES | 372 | Org.TLV 512 | YES | YES | NO | YES | YES | YES | YES | 373 | Rcv.TLV 513 | YES | YES | YES | NO | YES | YES | NO | 374 | Snd.TLV 513 | YES | YES | NO | NO | YES | YES | YES | 375 | Org.TLV 513 | YES | YES | NO | YES | YES | YES | YES | 376 | Rcv.TLV 514 | YES | YES | YES | NO | YES | YES | NO | 377 | Snd.TLV 514 | YES | YES | NO | NO | YES | YES | YES | 378 | Org.TLV 514 | YES | YES | NO | YES | YES | YES | YES | 379 | Rcv.TLV 515 | YES | YES | YES | NO | YES | YES | NO | 380 | Snd.TLV 515 | YES | YES | NO | NO | YES | YES | YES | 381 | Org.TLV 515 | YES | YES | NO | YES | YES | YES | YES | 382 | Rcv.TLV 1024 | YES | YES | YES | NO | NO | NO | NO | 383 | Snd.TLV 1024 | YES | YES | NO | NO | NO | NO | NO | 384 | Org.TLV 1024 | YES | YES | NO | NO | NO | NO | NO | 385 | Rcv.TLV 1025 | YES | YES | NO | NO | NO | NO | NO | 386 | Snd.TLV 1025 | YES | YES | NO | NO | NO | NO | NO | 387 | Org.TLV 1025 | YES | NO | NO | NO | NO | NO | NO | 388 | Rcv.TLV 1026 | YES | YES | YES | NO | NO | NO | NO | 389 | Snd.TLV 1026 | YES | YES | NO | NO | NO | NO | NO | 390 | Org.TLV 1026 | YES | NO | NO | NO | NO | NO | NO | 391 | Rcv.TLV 1027 | YES | YES | YES | NO | NO | NO | NO | 392 | Snd.TLV 1027 | YES | YES | NO | NO | NO | NO | NO | 393 | Org.TLV 1027 | YES | NO | NO | NO | NO | NO | NO | 394 | Rcv.TLV 1028 | YES | YES | YES | NO | NO | YES | NO | 395 | Snd.TLV 1028 | YES | YES | NO | NO | YES | YES | YES | 396 | Org.TLV 1028 | YES | YES | NO | YES | YES | YES | YES | 397 | Rcv.TLV 1029 | YES | YES | YES | NO | NO | NO | NO | 398 | Snd.TLV 1029 | YES | YES | NO | NO | NO | NO | NO | 399 | Org.TLV 1029 | YES | NO | NO | NO | NO | NO | NO | 400 +--------------+--------+-------+-----+-----+------+------+------+ 402 6. Prefix NLRI TLV support 404 Does the implementation support the TLVs described in Section 7 of 405 [I-D.ietf-idr-ls-distribution] ? 407 TLV 256: Local Node Descriptor 408 TLV 263: Multi-Topology IDs 410 TLV 264: OSPF route type 412 TLV 265: IP Reachability information 414 TLV 1152: IGP Flags 416 TLV 1153: Route Tag 418 TLV 1154: Extended Tag 420 TLV 1155: Prefix Metric 422 TLV 1156: OSPF Forwarding Address 424 TLV 1157: Opaque Prefix Attribute 425 +--------------+--------+-------+-----+----+------+------+------+ 426 | | IOS-XR | JUNOS | ODL | TI | NPHY | CTTC | CNIT | 427 +--------------+--------+-------+-----+----+------+------+------+ 428 | Rcv.TLV 256 | YES | YES | YES | NO | NO | NO | NO | 429 | Snd.TLV 256 | YES | YES | NO | NO | NO | NO | NO | 430 | Org.TLV 256 | YES | NO | NO | NO | NO | NO | NO | 431 | Rcv.TLV 263 | YES | YES | YES | NO | NO | NO | NO | 432 | Snd.TLV 263 | YES | YES | NO | NO | NO | NO | NO | 433 | Org.TLV 263 | YES | NO | NO | NO | NO | NO | NO | 434 | Rcv.TLV 264 | YES | YES | YES | NO | NO | NO | NO | 435 | Snd.TLV 264 | YES | YES | NO | NO | NO | NO | NO | 436 | Org.TLV 264 | YES | NO | NO | NO | NO | NO | NO | 437 | Rcv.TLV 265 | YES | YES | YES | NO | NO | NO | NO | 438 | Snd.TLV 265 | YES | YES | NO | NO | NO | NO | NO | 439 | Org.TLV 265 | YES | NO | NO | NO | NO | NO | NO | 440 | Rcv.TLV 1152 | YES | YES | YES | NO | NO | NO | NO | 441 | Snd.TLV 1152 | YES | YES | NO | NO | NO | NO | NO | 442 | Org.TLV 1152 | YES | NO | NO | NO | NO | NO | NO | 443 | Rcv.TLV 1153 | YES | YES | YES | NO | NO | NO | NO | 444 | Snd.TLV 1153 | YES | YES | NO | NO | NO | NO | NO | 445 | Org.TLV 1153 | YES | NO | NO | NO | NO | NO | NO | 446 | Rcv.TLV 1154 | YES | YES | YES | NO | NO | NO | NO | 447 | Snd.TLV 1154 | YES | YES | NO | NO | NO | NO | NO | 448 | Org.TLV 1154 | NO | NO | NO | NO | NO | NO | NO | 449 | Rcv.TLV 1155 | YES | YES | YES | NO | NO | NO | NO | 450 | Snd.TLV 1155 | YES | YES | NO | NO | NO | NO | NO | 451 | Org.TLV 1155 | YES | NO | NO | NO | NO | NO | NO | 452 | Rcv.TLV 1156 | YES | YES | YES | NO | NO | NO | NO | 453 | Snd.TLV 1156 | YES | YES | NO | NO | NO | NO | NO | 454 | Org.TLV 1156 | YES | NO | NO | NO | NO | NO | NO | 455 | Rcv.TLV 1157 | YES | YES | NO | NO | NO | NO | NO | 456 | Snd.TLV 1157 | YES | YES | NO | NO | NO | NO | NO | 457 | Org.TLV 1157 | YES | NO | NO | NO | NO | NO | NO | 458 +--------------+--------+-------+-----+----+------+------+------+ 460 7. Interoperable Implementations 462 List other implementations that you have tested interoperability of 463 BGP-LS Protocol Implementation. 465 7.1. Cisco Implementation 467 Cisco: The Cisco Systems, Inc. IOS-XR implementation should be 468 interoperable with other vendor BGP-LS Protocol implementations. In 469 particular, we have tested our interoperability with Juniper's JUNOS 470 implementation. 472 7.2. Juniper Implementation 474 Juniper: The Juniper Networks, Inc. JUNOS implementation should be 475 interoperable with other vendor BGP-LS Protocol implementations. In 476 particular, we have tested our interoperability with the Cisco 477 Systems, Inc. IOS-XR implementation and the Opendaylight 478 implementation. 480 7.3. OpenDaylight Implementation 482 Opendaylight: The Opendaylight implementation should be interoperable 483 with other vendor BGP-LS Protocol implementations. In particular, we 484 have tested our interoperability with Juniper's JUNOS implementation 485 and the Cisco Systems, Inc. IOS-XR implementation. BGP receiver is 486 implemented in the OpenDaylight Hydrogen release. BGP sender 487 functionality is planned in the upcoming Helium release. 489 7.4. Telecom Italia Implementation 491 The Telecom Italia implementation has been developed in the context 492 of the EU-funded project IDEALIST, aiming at studying flexible grid 493 optical networks. In this context, some extension have been defined 494 to advertise Nominal Center Frequency (NCF) status. It has been 495 tested against the Telefonica Netphony implementation (only receiver 496 role). Telecom Italia implementation has been successfully tested 497 also against OpenDayLight Hydrogen and Helium releases. 499 7.5. Netphony Implementation 501 Netphony is an open-source implementation of networking protocols. 502 The encoding of BGP-LS is available at Github [1]. Netphony BGP-LS 503 implementation is known to interoperate with Telecom Italia 504 Implementation, CTTC Implementation and CNIT Implementation. 506 7.6. CTTC Implementation 508 The CTTC implementation is part of the CTTC-PCE software, which uses 509 BGP-LS as a north bound interface to export the TED used to other 510 entities, or as an interface to provide the TED on which the PCE 511 operates on. It has been developed in the context of the IDEALIST 512 FP7 project. It has been tested with Telefonica implementation, in a 513 multi-partner control plane testbed that uses a hierarchical PCE to 514 perform multi-domain path computation. BGP-LS is used to export 515 (abstracted or physical) domain TE information from the child PCE to 516 the parent PCE. 518 7.7. CNIT Implementation 520 The CNIT implementation is part of the GMPLS-PCE control plane 521 software suitably extended to handle Flexgrid and advanced bandwidth- 522 variable transponders. The PCE includes a BGP-LS speaker module, 523 developed in C++ and running on Linux, able to export TED topology, 524 both in a static and dynamic fashion, triggered by PCEP 525 notifications, update/report messages on LSP setup/teardown/modify/ 526 adaptation events. Implementation includes updates of TE links, 527 nodes and per-link nominal central frequencies utilization 528 information. The BGP-LS speaker has been evaluated and tested with 529 Telefonica implementation in a child PCE configuration controlling a 530 real Flexgrid data plane domain and exporting link state information 531 to a parent PCE performing inter-domain end to end path computation. 532 Development has been done in the context of the FP7 IDEALIST project. 534 8. IANA Considerations 536 This document makes no request of IANA. 538 Note to RFC Editor: The IANA has requested that this section remain 539 in the document upon publication as an RFC. This note to the RFC 540 Editor, however, may be removed. 542 9. Security considerations 544 No new security issues are introduced by the BGP Link-State 545 Information Distribution Protocol defined in 546 [I-D.ietf-idr-ls-distribution]. 548 10. Acknowledgements 550 The authors would like to thank Stefano Previdi and Jan Medved for 551 their contributions to this document. 553 11. References 555 11.1. Normative References 557 [I-D.ietf-idr-ls-distribution] 558 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 559 Ray, "North-Bound Distribution of Link-State and TE 560 Information using BGP", draft-ietf-idr-ls-distribution-10 561 (work in progress), January 2015. 563 11.2. URIs 565 [1] https://github.com/telefonicaid/netphony-network-protocols 567 Authors' Addresses 569 Hannes Gredler (editor) 570 Juniper Networks, Inc. 571 1194 N. Mathilda Ave. 572 Sunnyvale, CA 94089 573 US 575 Email: hannes@juniper.net 577 Balaji Rajagopalan 578 Juniper Networks, Inc. 579 Electra, Exora Business Park, Marathahalli - Sarjapur Outer Ring Road 580 Bangalore, Karnataka 560103 581 India 583 Email: balajir@juniper.net 585 Chris Bowers 586 Juniper Networks, Inc. 587 1194 N. Mathilda Ave. 588 Sunnyvale, CA 94089 589 US 591 Email: cbowers@juniper.net 593 Saikat Ray 594 Google 595 1600 Amphitheatre Parkway 596 Mountain View, CA 94043 597 US 599 Email: raysaikat@gmail.com 600 Manish Bhardwaj 601 Cisco Systems, Inc. 602 170, West Tasman Drive 603 San Jose, CA 95134 604 US 606 Email: manbhard@cisco.com