idnits 2.17.1 draft-li-idr-bgp-ls-sr-policy-path-segment-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 : ---------------------------------------------------------------------------- ** There are 4 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 27, 2019) is 1759 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.ietf-mpls-bfd-directed' is defined on line 394, but no explicit reference was found in the text == Outdated reference: A later version (-26) exists of draft-ietf-idr-segment-routing-te-policy-06 == Outdated reference: A later version (-19) exists of draft-ietf-idr-te-lsp-distribution-11 == Outdated reference: A later version (-22) exists of draft-ietf-spring-mpls-path-segment-00 == Outdated reference: A later version (-22) exists of draft-ietf-spring-segment-routing-policy-03 == Outdated reference: A later version (-07) exists of draft-li-spring-srv6-path-segment-00 ** Obsolete normative reference: RFC 7752 (Obsoleted by RFC 9552) == Outdated reference: A later version (-30) exists of draft-ietf-mpls-bfd-directed-11 Summary: 2 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Interdomain Routing Working Group C. Li 3 Internet-Draft Huawei Technologies 4 Intended status: Standards Track H. Chen 5 Expires: December 29, 2019 China Telecom 6 M. Chen 7 J. Dong 8 Z. Li 9 Huawei Technologies 10 June 27, 2019 12 SR Policies Extensions for Path Segment and Bidirectional Path in BGP-LS 13 draft-li-idr-bgp-ls-sr-policy-path-segment-02 15 Abstract 17 This document specifies the way of collecting configuration and 18 states of SR policies carrying Path Segment and bidirectional path 19 information by using BPG-LS. Such information can be used by 20 external conponents for many use cases such as performance 21 measurement, path re-optimization and end-to-end protection. 23 Requirements Language 25 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 26 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 27 document are to be interpreted as described in RFC 2119 [RFC2119]. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at https://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on December 29, 2019. 46 Copyright Notice 48 Copyright (c) 2019 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (https://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 64 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 3. Carrying SR Path Sub-TLVs in BGP-LS . . . . . . . . . . . . . 3 66 3.1. SR Path Segment Sub-TLV . . . . . . . . . . . . . . . . . 5 67 3.2. Sub-TLVs for Bidirectional Path . . . . . . . . . . . . . 6 68 3.2.1. SR Bidirectional Path Sub-TLV . . . . . . . . . . . . 6 69 3.2.2. SR Reverse Path Segment List Sub-TLV . . . . . . . . 7 70 4. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 72 5.1. BGP-LS TLVs . . . . . . . . . . . . . . . . . . . . . . . 7 73 5.2. BGP-LS SR Segment Descriptors . . . . . . . . . . . . . . 8 74 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 75 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 76 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 77 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 78 8.2. Informative References . . . . . . . . . . . . . . . . . 9 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 81 1. Introduction 83 Segment routing (SR) [RFC8402] is a source routing paradigm that 84 allows the ingress node steers packets into a specific path according 85 to the Segment Routing Policy 86 [I-D.ietf-spring-segment-routing-policy]. 88 However, the SR Policies defined in 89 [I-D.ietf-spring-segment-routing-policy] only supports unidirectional 90 SR paths and there is no path ID in a Segment List to identify an SR 91 path. For identifying an SR path and supporting bidirectional path 92 [I-D.ietf-spring-mpls-path-segment], new policies carrying Path 93 Segment and bidirectional path information are defined in 95 [I-D.li-idr-sr-policy-path-segment-distribution], as well as the 96 extensions to BGP to distribute new SR policies. The Path Segment 97 can be a Path Segment in SR-MPLS [I-D.ietf-spring-mpls-path-segment] 98 , or a Path Segment in SRv6 [I-D.li-spring-srv6-path-segment], or 99 other IDs that can identify a path. 101 In many network scenarios, the configuration and state of each TE 102 Policy is required by a controller which allows the network operator 103 to optimize several functions and operations through the use of a 104 controller aware of both topology and state information 105 [I-D.ietf-idr-te-lsp-distribution]. 107 To collect the TE Policy information that is locally available in a 108 router, [I-D.ietf-idr-te-lsp-distribution] describes a new mechanism 109 by using BGP-LS update messages. 111 Based on the mechanism defined in [I-D.ietf-idr-te-lsp-distribution], 112 this document describes a mechanism to distribute configuration and 113 states of the new SR policies defined in 114 [I-D.li-idr-sr-policy-path-segment-distribution] to external 115 components using BGP-LS. 117 2. Terminology 119 This memo makes use of the terms defined in [RFC8402] and 120 [I-D.ietf-idr-te-lsp-distribution]. 122 3. Carrying SR Path Sub-TLVs in BGP-LS 124 A mechanism to collect states of SR Policies via BGP-LS is proposed 125 by [I-D.ietf-idr-te-lsp-distribution]. The characteristics of an SR 126 policy can be described by a TE Policy State TLV, which is carried in 127 the optional non-transitive BGP Attribute "LINK_STATE Attribute" 128 defined in [RFC7752]. The TE Policy State TLV contains several sub- 129 TLVs such as SR TE Policy sub-TLVs. Rather than replicating SR TE 130 Policy sub-TLVs, [I-D.ietf-idr-te-lsp-distribution] reuses the 131 equivalent sub-TLVs as defined in 132 [I-D.ietf-idr-segment-routing-te-policy]. 134 [I-D.li-idr-sr-policy-path-segment-distribution] defines the BGP 135 extensions for Path Segment. The Path Segment can appear at both 136 segment-list level and candidate path level upon the use case. The 137 encoding is shown below. 139 SR Policy SAFI NLRI: 140 Attributes: 141 Tunnel Encaps Attribute (23) 142 Tunnel Type: SR Policy 143 Binding SID 144 Preference 145 Priority 146 Policy Name 147 Explicit NULL Label Policy (ENLP) 148 Path Segment 149 Segment List 150 Weight 151 Path Segment 152 Segment 153 Segment 154 ... 155 Segment List 156 Weight 157 Path Segment 158 Segment 159 Segment 160 ... 161 ... 163 Figure 1. Path Segment in SR policy 165 Also, [I-D.li-idr-sr-policy-path-segment-distribution] defines SR 166 policy extensions for bidirectional SR path, the encoding is shown 167 below: 169 SR Policy SAFI NLRI: 170 Attributes: Tunnel Encaps Attribute (23) 171 Tunnel Type: SR Policy 172 Binding SID 173 Preference 174 Priority 175 Policy Name 176 Explicit NULL Label Policy (ENLP) 177 Bidirectioanl Path 178 Segment List 179 Weight 180 Path Segment 181 Segment 182 Segment 183 ... 184 Reverse Segment List 185 Weight 186 Path Segment 187 Segment 188 Segment 189 ... 191 Figure 2. SR policy for Bidirectional path 193 In order to collect configuration and states of unidirectional and 194 bidirectional SR policies defined in 195 [I-D.li-idr-sr-policy-path-segment-distribution], new sub-TLVs in SR 196 TE Policy sub-TLVs should be defined. Likewise, rather than 197 replicating SR Policy sub-TLVs, this document can reuse the 198 equivalent sub-TLVs as defined in 199 [I-D.li-idr-sr-policy-path-segment-distribution]. 201 3.1. SR Path Segment Sub-TLV 203 This section reuses the SR Path Segment sub-TLV defined in 204 [I-D.li-idr-sr-policy-path-segment-distribution] to describe a Path 205 Segment , and it can be included in the Segment List sub-TLV as 206 defined in [I-D.ietf-idr-te-lsp-distribution] . An SR Path Segment 207 sub-TLV can be associated with an SR path specified by a Segment List 208 sub-TLV, and it MUST appear only once within a Segment List sub-TLV. 209 Also, it can be used for identifying an SR candidate path or an SR 210 Policy defined in [I-D.ietf-spring-segment-routing-policy]. 212 The format of Path Segment TLV is included below for reference. 214 0 1 2 3 215 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | Type | Length | Flag | ST | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 | Path Segment (Variable) | 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 Figure 2. Path Segment sub-TLV 223 All fields, including type and length, are defined in 224 [I-D.li-idr-sr-policy-path-segment-distribution]. 226 3.2. Sub-TLVs for Bidirectional Path 228 In some scenarios like mobile backhaul transport network, there are 229 requirements to support bidirectional path. In SR, a bidirectional 230 path can be represented as a binding of two unidirectional SR paths 231 [I-D.ietf-spring-mpls-path-segment]. 232 [I-D.li-idr-sr-policy-path-segment-distribution] defines new sub-TLVs 233 to describe an SR bidirectional path. An SR policy carrying SR 234 bidirectional path information is expressed in Figure 1. 236 3.2.1. SR Bidirectional Path Sub-TLV 238 This section reuses the SR bidirectional path sub-TLV defined in 239 [I-D.li-idr-sr-policy-path-segment-distribution] to specify a 240 bidirectional path, which contains a Segment List sub-TLV 241 [I-D.ietf-idr-segment-routing-te-policy] and an associated Reverse 242 Path Segment List as defined in 243 [I-D.li-idr-sr-policy-path-segment-distribution]. The SR 244 bidirectional path sub-TLV has the following format: 246 0 1 2 3 247 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | Type | Length | RESERVED | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | Sub-TLVs (Variable) | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 Figure 3. SR Bidirectional path sub-TLV 255 All fields, including type and length, are defined in 256 [I-D.li-idr-sr-policy-path-segment-distribution]. 258 3.2.2. SR Reverse Path Segment List Sub-TLV 260 This section reuses the SR Reverse Path Segment List sub-TLV defined 261 in [I-D.li-idr-sr-policy-path-segment-distribution] to specify an 262 reverse SR path associated with the path specified by the Segment 263 List in the same SR Bidirectional Path Sub-TLV, and it has the 264 following format: 266 0 1 2 3 267 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 | Type | Length | RESERVED | 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | Sub-TLVs (Variable) | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 Figure 4. SR Reverse Path Segment List Sub-TLV 275 All fields, including type and length, are defined in 276 [I-D.li-idr-sr-policy-path-segment-distribution]. 278 4. Operations 280 No new operation procedures are defined in this document, the 281 operations procedures of [RFC7752] can apply to this document. 283 Typically but not limited to, the uni/bidirectional SR policies 284 carrying path identification information can be distributed by the 285 ingress node. 287 Generally, BGP-LS is used for collecting link states and 288 synchronizing with the external component. The consumer of the uni/ 289 bidirectional SR policies carrying path identification information is 290 not BGP LS process by itself, and it can be any applications such as 291 performance measurement [I-D.gandhi-spring-udp-pm] and path re- 292 coputation or re-optimization, etc. The operation of sending 293 information to other precesses is out of scope of this document. 295 5. IANA Considerations 297 5.1. BGP-LS TLVs 299 IANA maintains a registry called "Border Gateway Protocol - Link 300 State (BGP-LS) Parameters" with a sub-registry called "Node Anchor, 301 Link Descriptor and Link Attribute TLVs". The following TLV 302 codepoints are suggested (for early allocation by IANA): 304 Codepoint Description Reference 305 ------------------------------------------------------------- 306 1212 Path Segment sub-TLV This document 307 1213 SR Bidirectional Path sub-TLV This document 308 1214 Reverse Segment List sub-TLV This document 310 5.2. BGP-LS SR Segment Descriptors 312 This document defines new sub-TLVs in the registry "SR Segment 313 Descriptor Types" [I-D.ietf-idr-te-lsp-distribution] to be assigned 314 by IANA: 316 Codepoint Description Reference 317 ------------------------------------------------------------- 318 14 Path Segment sub-TLV This document 320 6. Security Considerations 322 TBA 324 7. Acknowledgements 326 Many thanks to Shraddha Hedge for her detailed review and 327 professional comments. 329 8. References 331 8.1. Normative References 333 [I-D.ietf-idr-segment-routing-te-policy] 334 Previdi, S., Filsfils, C., Jain, D., Mattes, P., Rosen, 335 E., and S. Lin, "Advertising Segment Routing Policies in 336 BGP", draft-ietf-idr-segment-routing-te-policy-06 (work in 337 progress), May 2019. 339 [I-D.ietf-idr-te-lsp-distribution] 340 Previdi, S., Talaulikar, K., Dong, J., Chen, M., Gredler, 341 H., and J. Tantsura, "Distribution of Traffic Engineering 342 (TE) Policies and State using BGP-LS", draft-ietf-idr-te- 343 lsp-distribution-11 (work in progress), May 2019. 345 [I-D.ietf-spring-mpls-path-segment] 346 Cheng, W., Li, H., Chen, M., Gandhi, R., and R. Zigler, 347 "Path Segment in MPLS Based Segment Routing Network", 348 draft-ietf-spring-mpls-path-segment-00 (work in progress), 349 March 2019. 351 [I-D.ietf-spring-segment-routing-policy] 352 Filsfils, C., Sivabalan, S., daniel.voyer@bell.ca, d., 353 bogdanov@google.com, b., and P. Mattes, "Segment Routing 354 Policy Architecture", draft-ietf-spring-segment-routing- 355 policy-03 (work in progress), May 2019. 357 [I-D.li-idr-sr-policy-path-segment-distribution] 358 Li, C., Chen, M., Dong, J., and Z. Li, "Segment Routing 359 Policies for Path Segment and Bidirectional Path", draft- 360 li-idr-sr-policy-path-segment-distribution-01 (work in 361 progress), October 2018. 363 [I-D.li-spring-srv6-path-segment] 364 Li, C., Chen, M., Dhody, D., Li, Z., Dong, J., and R. 365 Gandhi, "Path Segment for SRv6 (Segment Routing in IPv6)", 366 draft-li-spring-srv6-path-segment-00 (work in progress), 367 October 2018. 369 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 370 Requirement Levels", BCP 14, RFC 2119, 371 DOI 10.17487/RFC2119, March 1997, 372 . 374 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 375 S. Ray, "North-Bound Distribution of Link-State and 376 Traffic Engineering (TE) Information Using BGP", RFC 7752, 377 DOI 10.17487/RFC7752, March 2016, 378 . 380 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 381 Decraene, B., Litkowski, S., and R. Shakir, "Segment 382 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 383 July 2018, . 385 8.2. Informative References 387 [I-D.gandhi-spring-udp-pm] 388 Gandhi, R., Filsfils, C., daniel.voyer@bell.ca, d., 389 Salsano, S., Ventre, P., and M. Chen, "UDP Path for In- 390 band Performance Measurement for Segment Routing 391 Networks", draft-gandhi-spring-udp-pm-02 (work in 392 progress), September 2018. 394 [I-D.ietf-mpls-bfd-directed] 395 Mirsky, G., Tantsura, J., Varlashkin, I., and M. Chen, 396 "Bidirectional Forwarding Detection (BFD) Directed Return 397 Path", draft-ietf-mpls-bfd-directed-11 (work in progress), 398 April 2019. 400 Authors' Addresses 402 Cheng Li 403 Huawei Technologies 404 Huawei Campus, No. 156 Beiqing Rd. 405 Beijing 100095 406 China 408 Email: chengli13@huawei.com 410 Huanan Chen 411 China Telecom 412 109 West Zhongshan Ave 413 Guangzhou 414 China 416 Email: chenhn8.gd@chinatelecom.cn 418 Mach(Guoyi) Chen 419 Huawei Technologies 420 Huawei Campus, No. 156 Beiqing Rd. 421 Beijing 100095 422 China 424 Email: Mach.chen@huawei.com 426 Jie Dong 427 Huawei Technologies 428 Huawei Campus, No. 156 Beiqing Rd. 429 Beijing 100095 430 China 432 Email: jie.dong@huawei.com 433 Zhenbin Li 434 Huawei Technologies 435 Huawei Campus, No. 156 Beiqing Rd. 436 Beijing 100095 437 China 439 Email: lizhenbin@huawei.com