idnits 2.17.1 draft-gredler-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 (February 14, 2014) is 3723 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-04 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: August 18, 2014 S. Ray, Ed. 6 M. Bhardwaj 7 Cisco Systems, Inc. 8 February 14, 2014 10 BGP Link-State Information Distribution Implementation Report 11 draft-gredler-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 August 18, 2014. 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 . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . 9 65 7.1. Cisco Implementation . . . . . . . . . . . . . . . . . . . 9 66 7.2. Juniper Implementation . . . . . . . . . . . . . . . . . . 10 67 7.3. TBD Implementation . . . . . . . . . . . . . . . . . . . . 10 68 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 69 9. Security considerations . . . . . . . . . . . . . . . . . . . 10 70 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 71 11. Informative References . . . . . . . . . . . . . . . . . . . . 10 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 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 104 JUNOS 105 Name: Balaji Rajagopalan 106 Email: balajir@juniper.net 107 Vendor: Juniper Networks, Inc. 108 Release: JUNOS 109 Protocol Role: Sender, Receiver 111 3. NLRI subtypes 113 Does the implementation support the Network Layer Reachability (NLRI) 114 subtypes as described in Section 3.2 of 115 [I-D.ietf-idr-ls-distribution] ? 116 N1: Node NLRI 118 N2: Link NLRI 120 N3: IPv4 Topology Prefix NLRI 122 N4: IPv6 Topology Prefix NLRI 124 +--------+--------+-------+-----+ 125 | | IOS-XR | JUNOS | TBD | 126 +--------+--------+-------+-----+ 127 | Rcv.N1 | YES | YES | --- | 128 | Snd.N1 | YES | YES | --- | 129 | Rcv.N2 | YES | YES | --- | 130 | Snd.N2 | YES | YES | --- | 131 | Rcv.N3 | YES | NO(1) | --- | 132 | Snd.N3 | YES | NO(1) | --- | 133 | Rcv.N4 | YES | NO(1) | --- | 134 | Snd.N4 | YES | NO(1) | --- | 135 +--------+--------+-------+-----+ 137 Note 1: Topology Prefix NLRIs get transparently relayed. 139 4. Link NLRI TLV support 141 Does the implementation support the TLVs described in Section 7 of 142 [I-D.ietf-idr-ls-distribution] ? 144 TLV 256: Local Node Descriptor 146 TLV 257: Remote Node Descriptor 148 TLV 258: Link Local/Remote Identifier 150 TLV 259: IPv4 Interface address 152 TLV 260: IPv4 Neighbor address 154 TLV 261: IPv6 Interface address 156 TLV 262: IPv6 Neighbor address 158 TLV 263: Multi-Topology IDs 159 TLV 512: Autonomous System 161 TLV 513: BGP-LS Identifier 163 TLV 514: Area ID 165 TLV 515: IGP Router ID 167 TLV 1028: IPv4 router-ID of Local Node 169 TLV 1029: IPv6 router-ID of Local Node 171 TLV 1030: IPv4 router-ID of Remote Node 173 TLV 1031: IPv6 router-ID of Remote Node 175 TLV 1088: Administrative group (color) 177 TLV 1089: Maximum link bandwidth 179 TLV 1090: Maximum reservable link bandwidth 181 TLV 1091: Unreserved link bandwidth 183 TLV 1092: TE default Metric 185 TLV 1093: Link Protection Type 187 TLV 1094: MPLS Protocol Mask 189 TLV 1095: IGP Metric 191 TLV 1096: Shared Risk Link Group 193 TLV 1097: Opaque Link attribute 195 TLV 1098: Link name attribute 197 +--------------+--------+-------+-----+ 198 | | IOS-XR | JUNOS | TBD | 199 +--------------+--------+-------+-----+ 200 | Rcv.TLV 256 | YES | YES | --- | 201 | Snd.TLV 256 | YES | YES | --- | 202 | Rcv.TLV 257 | YES | YES | --- | 203 | Snd.TLV 257 | YES | YES | --- | 204 | Rcv.TLV 258 | YES | YES | --- | 205 | Snd.TLV 258 | YES | YES | --- | 206 | Rcv.TLV 259 | YES | YES | --- | 207 | Snd.TLV 259 | YES | YES | --- | 208 | Rcv.TLV 260 | YES | YES | --- | 209 | Snd.TLV 260 | YES | YES | --- | 210 | Rcv.TLV 261 | YES | YES | --- | 211 | Snd.TLV 261 | YES | YES | --- | 212 | Rcv.TLV 262 | YES | YES | --- | 213 | Snd.TLV 262 | YES | YES | --- | 214 | Rcv.TLV 263 | --- | NO | --- | 215 | Snd.TLV 263 | --- | NO | --- | 216 | Rcv.TLV 512 | YES | YES | --- | 217 | Snd.TLV 512 | YES | YES | --- | 218 | Rcv.TLV 513 | --- | YES | --- | 219 | Snd.TLV 513 | --- | NO | --- | 220 | Rcv.TLV 514 | --- | YES | --- | 221 | Snd.TLV 514 | --- | NO | --- | 222 | Rcv.TLV 515 | YES | YES | --- | 223 | Snd.TLV 515 | YES | YES | --- | 224 | Rcv.TLV 1028 | YES | YES | --- | 225 | Snd.TLV 1028 | YES | YES | --- | 226 | Rcv.TLV 1029 | YES | YES | --- | 227 | Snd.TLV 1029 | YES | YES | --- | 228 | Rcv.TLV 1030 | YES | YES | --- | 229 | Snd.TLV 1030 | YES | YES | --- | 230 | Rcv.TLV 1031 | YES | YES | --- | 231 | Snd.TLV 1031 | YES | YES | --- | 232 | Rcv.TLV 1088 | YES | YES | --- | 233 | Snd.TLV 1088 | YES | YES | --- | 234 | Rcv.TLV 1089 | YES | YES | --- | 235 | Snd.TLV 1089 | YES | YES | --- | 236 | Rcv.TLV 1090 | --- | YES | --- | 237 | Snd.TLV 1090 | --- | YES | --- | 238 | Rcv.TLV 1091 | --- | YES | --- | 239 | Snd.TLV 1091 | --- | YES | --- | 240 | Rcv.TLV 1092 | --- | YES | --- | 241 | Snd.TLV 1092 | --- | YES | --- | 242 | Rcv.TLV 1093 | --- | NO | --- | 243 | Snd.TLV 1093 | --- | NO | --- | 244 | Rcv.TLV 1094 | NO | NO | --- | 245 | Snd.TLV 1094 | NO | NO | --- | 246 | Rcv.TLV 1095 | --- | NO | --- | 247 | Snd.TLV 1095 | --- | NO | --- | 248 | Rcv.TLV 1096 | YES | YES | --- | 249 | Snd.TLV 1096 | --- | YES | --- | 250 | Rcv.TLV 1097 | --- | YES | --- | 251 | Snd.TLV 1097 | --- | NO | --- | 252 | Rcv.TLV 1098 | NO | NO | --- | 253 | Snd.TLV 1098 | NO | NO | --- | 254 +--------------+--------+-------+-----+ 256 5. Node NLRI TLV support 258 Does the implementation support the TLVs described in Section 7 of 259 [I-D.ietf-idr-ls-distribution] ? 261 TLV 256: Local Node Descriptor 263 TLV 263: Multi-Topology IDs 265 TLV 512: Autonomous System 267 TLV 513: BGP-LS Identifier 269 TLV 514: Area ID 271 TLV 515: IGP Router ID 273 TLV 1024: Node flag bits 275 TLV 1025: Opaque Node properties 277 TLV 1026: Node name 279 TLV 1027: IS-IS Area Identifier 281 TLV 1028: IPv4 router-ID of Local Node 283 TLV 1029: IPv6 router-ID of Local Node 284 +--------------+--------+-------+-----+ 285 | | IOS-XR | JUNOS | TBD | 286 +--------------+--------+-------+-----+ 287 | Rcv.TLV 256 | YES | YES | --- | 288 | Snd.TLV 256 | YES | YES | --- | 289 | Rcv.TLV 263 | --- | NO | --- | 290 | Snd.TLV 263 | --- | NO | --- | 291 | Rcv.TLV 512 | YES | YES | --- | 292 | Snd.TLV 512 | YES | YES | --- | 293 | Rcv.TLV 513 | --- | YES | --- | 294 | Snd.TLV 513 | --- | NO | --- | 295 | Rcv.TLV 514 | --- | YES | --- | 296 | Snd.TLV 514 | --- | NO | --- | 297 | Rcv.TLV 515 | YES | YES | --- | 298 | Snd.TLV 515 | YES | YES | --- | 299 | Rcv.TLV 1024 | YES | NO | --- | 300 | Snd.TLV 1024 | YES | NO | --- | 301 | Rcv.TLV 1025 | --- | NO | --- | 302 | Snd.TLV 1025 | --- | NO | --- | 303 | Rcv.TLV 1026 | --- | NO | --- | 304 | Snd.TLV 1026 | --- | NO | --- | 305 | Rcv.TLV 1027 | --- | NO | --- | 306 | Snd.TLV 1027 | --- | NO | --- | 307 | Rcv.TLV 1028 | YES | YES | --- | 308 | Snd.TLV 1028 | YES | YES | --- | 309 | Rcv.TLV 1029 | YES | YES | --- | 310 | Snd.TLV 1029 | YES | YES | --- | 311 +--------------+--------+-------+-----+ 313 6. Prefix NLRI TLV support 315 Does the implementation support the TLVs described in Section 7 of 316 [I-D.ietf-idr-ls-distribution] ? 318 TLV 256: Local Node Descriptor 320 TLV 263: Multi-Topology IDs 322 TLV 264: OSPF route type 324 TLV 265: IP Reachability information 326 TLV 1152: IGP Flags 327 TLV 1153: Route Tag 329 TLV 1154: Extended Tag 331 TLV 1155: Prefix Metric 333 TLV 1156: OSPF Forwarding Address 335 TLV 1157: Opaque Prefix Atrribute 337 +--------------+--------+-------+-----+ 338 | | IOS-XR | JUNOS | TBD | 339 +--------------+--------+-------+-----+ 340 | Rcv.TLV 256 | YES | NO | --- | 341 | Snd.TLV 256 | YES | NO | --- | 342 | Rcv.TLV 263 | YES | NO | --- | 343 | Snd.TLV 263 | YES | NO | --- | 344 | Rcv.TLV 264 | YES | NO | --- | 345 | Snd.TLV 264 | YES | NO | --- | 346 | Rcv.TLV 265 | YES | NO | --- | 347 | Snd.TLV 265 | YES | NO | --- | 348 | Rcv.TLV 1152 | YES | NO | --- | 349 | Snd.TLV 1152 | YES | NO | --- | 350 | Rcv.TLV 1153 | YES | NO | --- | 351 | Snd.TLV 1153 | YES | NO | --- | 352 | Rcv.TLV 1154 | YES | NO | --- | 353 | Snd.TLV 1154 | YES | NO | --- | 354 | Rcv.TLV 1155 | YES | NO | --- | 355 | Snd.TLV 1155 | YES | NO | --- | 356 | Rcv.TLV 1156 | YES | NO | --- | 357 | Snd.TLV 1156 | YES | NO | --- | 358 | Rcv.TLV 1157 | --- | NO | --- | 359 | Snd.TLV 1157 | --- | NO | --- | 360 +--------------+--------+-------+-----+ 362 7. Interoperable Implementations 364 List other implementations that you have tested interoperability of 365 BGP-LS Protocol Implementation. 367 7.1. Cisco Implementation 369 Cisco: The Cisco Systems, Inc. IOS-XR implementation should be 370 interoperable with other vendor BGP-LS Protocol implementations. In 371 particular we have tested our interoperability with Juniper's JUNOS 372 and Telefonica's XXX implementation. 374 7.2. Juniper Implementation 376 Juniper: The Juniper Networks, Inc. JUNOS implementation should be 377 interoperable with other vendor BGP-LS Protocol implementations. In 378 particular we have tested our interoperability with Cisco Systems, 379 Inc. IOS-XR implementation. 381 7.3. TBD Implementation 383 TBD: The TBD implementation has been tested by us with other 384 implementations. It was so buggy that we were rolling on the floor 385 laughing. We think this was either due to bad star alignment or 386 perhaps increased solar flare activity. 388 8. IANA Considerations 390 This document makes no request of IANA. 392 Note to RFC Editor: The IANA has requested that this section remain 393 in the document upon publication as an RFC. This note to the RFC 394 Editor, however, may be removed. 396 9. Security considerations 398 No new security issues are introduced to the BGP Link-State 399 Information Distribution Protocol defined in 400 [I-D.ietf-idr-ls-distribution]. 402 10. Acknowledgements 404 The authors would like to thank Stefano Previdi, Jan Medved for their 405 contributions to this document. 407 11. Informative References 409 [I-D.ietf-idr-ls-distribution] 410 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 411 Ray, "North-Bound Distribution of Link-State and TE 412 Information using BGP", draft-ietf-idr-ls-distribution-04 413 (work in progress), November 2013. 415 Authors' Addresses 417 Hannes Gredler (editor) 418 Juniper Networks, Inc. 419 1194 N. Mathilda Ave. 420 Sunnyvale, CA 94089 421 US 423 Email: hannes@juniper.net 425 Balaji Rajagopalan 426 Juniper Networks, Inc. 427 1194 N. Mathilda Ave. 428 Sunnyvale, CA 94089 429 US 431 Email: balajir@juniper.net 433 Saikat Ray (editor) 434 Cisco Systems, Inc. 435 170, West Tasman Drive 436 San Jose, CA 95134 437 US 439 Email: sairay@cisco.com 441 Manish Bhardwaj 442 Cisco Systems, Inc. 443 170, West Tasman Drive 444 San Jose, CA 95134 445 US 447 Email: manbhard@cisco.com