idnits 2.17.1 draft-psarkar-lsvr-bgp-spf-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-lsvr-bgp-spf]), 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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 2, 2020) is 1425 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC5331' is defined on line 234, but no explicit reference was found in the text ** Obsolete normative reference: RFC 7752 (Obsoleted by RFC 9552) == Outdated reference: A later version (-29) exists of draft-ietf-lsvr-bgp-spf-08 Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Sarkar, Ed. 3 Internet-Draft K. Patel 4 Intended status: Informational Arrcus, Inc. 5 Expires: December 4, 2020 S. Pallagatti 6 VMware 7 B. Saji 8 Arista Networks 9 June 2, 2020 11 BGP Shortest Path Routing Extension Implementation Report 12 draft-psarkar-lsvr-bgp-spf-impl-00 14 Abstract 16 This document is an implementation report for the Shortest Path 17 Routing Extensions to BGP protocol as defined in 18 [I-D.ietf-lsvr-bgp-spf]. The authors did not verify the accuracy of 19 the information provided by respondents. The respondents are experts 20 with the implementations they reported on, and their responses are 21 considered authoritative for the implementations for which their 22 responses represent. The respondents were asked to only use the 23 "YES" answer if the feature had at least been tested in the lab. 25 Requirements Language 27 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 28 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 29 document are to be interpreted as described in RFC 2119 [RFC2119]. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at https://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on December 4, 2020. 48 Copyright Notice 50 Copyright (c) 2020 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (https://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 2. Implementation Forms . . . . . . . . . . . . . . . . . . . . 3 67 3. BGP-LS-SPF Peering Models . . . . . . . . . . . . . . . . . . 3 68 4. Extensions to BGP-LS . . . . . . . . . . . . . . . . . . . . 4 69 5. Support for Simplified Decision Process . . . . . . . . . . . 4 70 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 71 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 72 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 73 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 74 9.1. Normative References . . . . . . . . . . . . . . . . . . 5 75 9.2. Informative References . . . . . . . . . . . . . . . . . 6 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 78 1. Introduction 80 [I-D.ietf-lsvr-bgp-spf] describes an alternative solution which 81 leverages BGP-LS [RFC7752] and the Shortest Path First algorithm 82 similar to Internal Gateway Protocols (IGPs) such as OSPF [RFC2328]. 83 The solution introduces an new BGP-LS-SPF AFI-SAFI and replaces the 84 Phase 1 and 2 decision functions of the Decision Process specifed by 85 [RFC4271] with the Shortest Path First (SPF) algorithm also known as 86 the Dijkstra algorithm. This solution avails the benefits of both 87 BGP and SPF-based IGPs that include TCP based flow-control, no 88 periodic link-state refresh, and completely incremental NLRI 89 advertisements. These advantages can reduce the overhead in MSDCs 90 where there is a high degree of Equal Cost Multi- Path (ECMPs) and 91 the topology is very stable. Additionally, using an SPF-based 92 computation can support fast convergence and the computation of Loop- 93 Free Alternatives (LFAs) [RFC5286] in the event of link failures. 95 This document provides an implementation report of the Shortest Path 96 Routing extensions to BGP protocol as specified in 97 [I-D.ietf-lsvr-bgp-spf]. 99 The authors did not verify the accuracy of the information provided 100 by respondents or by any alternative means. The respondents are 101 experts with the implementations they reported on, and their 102 responses are considered authoritative for the implementations for 103 which their responses represent. Respondents were asked to only use 104 the "YES" answer if the feature had at least been tested in the lab. 106 2. Implementation Forms 108 Contact and implementation information for person filling out this 109 form: 111 ArcOS 112 Name: Pushpasis Sarkar 113 Email: pushpasis@arrcus.com 114 Vendor: Arrcus, Inc. 115 Release: ArcOS 116 Protocol Role: Route Reflector and Client 118 FRR 119 Name: Basil Saji 120 Email: sajibasil@gmail.com 121 Vendor: FRR 122 Release: 123 Protocol Role: Route Reflector 125 Name: Santosh P K 126 Email: santosh.pallagatti@gmail.com 127 Vendor: FRR 128 Release: 129 Protocol Role: Route Reflector 131 Figure 1 133 3. BGP-LS-SPF Peering Models 135 Does the implementation support the following BGP-LS-SPF Peering 136 Models as specified in Section 2 of [I-D.ietf-lsvr-bgp-spf]? 138 o 2.1 -- BGP Single-Hop Peering on Network Node Connections 139 o 2.2 -- BGP Peering Between Directly Connected Network Nodes 141 o 2.3 -- BGP Peering in Route-Reflector or Controller Topology 143 +----------+-----+-----+----------------------------+ 144 | Reelease | 2.1 | 2.2 | 2.3 | 145 +----------+-----+-----+----------------------------+ 146 | ArcOS | Yes | Yes | Yes (Route Reflector only) | 147 | FRR | Yes | Yes | Yes | 148 +----------+-----+-----+----------------------------+ 150 Table 1: Peering Model Support 152 4. Extensions to BGP-LS 154 Does the implementation support the following BGP-LS-SPF TLVs as 155 described in Section 4 and sub-sections of [I-D.ietf-lsvr-bgp-spf]?? 157 o T1 -- Node NLRI Attribute SPF Capability TLV 159 o T2 -- Node/Link/Prefix NLRI Attribute SPF Status TLV 161 o T3 -- Link NLRI Attribute IPv4 Prefix-Length TLV 163 o T4 -- Link NLRI Attribute IPv6 Prefix-Length TLV 165 o T5 -- Attribute Sequence-Number TLV 167 +---------+-------------+-----+-----+-----+-----+-----+ 168 | Release | Send / Recv | T1 | T2 | T3 | T4 | T5 | 169 +---------+-------------+-----+-----+-----+-----+-----+ 170 | ArcOS | Send | Yes | Yes | Yes | Yes | Yes | 171 | | Recv | Yes | Yes | Yes | Yes | Yes | 172 | FRR | Send | Yes | Yes | Yes | Yes | Yes | 173 | | Recv | Yes | Yes | Yes | Yes | Yes | 174 +---------+-------------+-----+-----+-----+-----+-----+ 176 Table 2: BGP-LS Extension TLVs Support 178 5. Support for Simplified Decision Process 180 Does the implementation support the following Best Path Decision 181 processes as described in Section 5 and sub-sections of 182 [I-D.ietf-lsvr-bgp-spf]? 184 o P1 -- Phase-1 BGP NLRI Selection 186 o P2 -- Dual Stack Support 187 o P3 -- SPF Calculation based on BGP-LS NLRI 189 +---------+-----+-----+-----+ 190 | Release | P1 | P2 | P3 | 191 +---------+-----+-----+-----+ 192 | ArcOS | Yes | Yes | Yes | 193 | TBA | --- | --- | --- | 194 +---------+-----+-----+-----+ 196 Table 3: Decision Process Support 198 6. Acknowledgements 200 TBA 202 7. IANA Considerations 204 N/A. - No protocol changes are proposed in this document. 206 8. Security Considerations 208 This document does not introduce any change in any of the protocol 209 specifications. 211 9. References 213 9.1. Normative References 215 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 216 Requirement Levels", BCP 14, RFC 2119, 217 DOI 10.17487/RFC2119, March 1997, 218 . 220 [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, 221 DOI 10.17487/RFC2328, April 1998, 222 . 224 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 225 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 226 DOI 10.17487/RFC4271, January 2006, 227 . 229 [RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for 230 IP Fast Reroute: Loop-Free Alternates", RFC 5286, 231 DOI 10.17487/RFC5286, September 2008, 232 . 234 [RFC5331] Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream 235 Label Assignment and Context-Specific Label Space", 236 RFC 5331, DOI 10.17487/RFC5331, August 2008, 237 . 239 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 240 S. Ray, "North-Bound Distribution of Link-State and 241 Traffic Engineering (TE) Information Using BGP", RFC 7752, 242 DOI 10.17487/RFC7752, March 2016, 243 . 245 9.2. Informative References 247 [I-D.ietf-lsvr-bgp-spf] 248 Patel, K., Lindem, A., Zandi, S., and W. Henderickx, 249 "Shortest Path Routing Extensions for BGP Protocol", 250 draft-ietf-lsvr-bgp-spf-08 (work in progress), March 2020. 252 Authors' Addresses 254 Pushpasis Sarkar (editor) 255 Arrcus, Inc. 256 Bangalore, KA 562125 257 India 259 Email: pushpasis.ietf@gmail.com 261 Keyur Patel 262 Arrcus, Inc. 264 Email: keyur@arrcus.com 266 Santosh 267 VMware 269 Email: santosh.pallagatti@gmail.com 271 Basil 272 Arista Networks 274 Email: sajibasil@gmail.com