idnits 2.17.1 draft-srcompdt-spring-compression-analysis-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 document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 144: '...ression proposal MUST reduce the size ...' RFC 2119 keyword, line 152: '...ression proposal SHOULD minimize the n...' RFC 2119 keyword, line 217: '...ression proposal SHOULD minimize the a...' RFC 2119 keyword, line 246: '...s SRv6 SID Lists SHOULD be based on th...' RFC 2119 keyword, line 248: '... MAY be based on a different data pl...' (10 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 19, 2021) is 1161 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'B5' is mentioned on line 120, but not defined == Missing Reference: 'B7' is mentioned on line 120, but not defined == Missing Reference: 'B6' is mentioned on line 122, but not defined == Missing Reference: 'B8' is mentioned on line 122, but not defined == Outdated reference: A later version (-31) exists of draft-bonica-6man-comp-rtg-hdr-24 == Outdated reference: A later version (-07) exists of draft-cl-spring-generalized-srv6-for-cmpr-02 == Outdated reference: A later version (-07) exists of draft-decraene-spring-srv6-vlsid-04 == Outdated reference: A later version (-16) exists of draft-filsfils-spring-net-pgm-extension-srv6-usid-08 == Outdated reference: A later version (-03) exists of draft-filsfilscheng-spring-srv6-srh-comp-sl-enc-02 == Outdated reference: A later version (-13) exists of draft-ietf-6man-spring-srv6-oam-08 == Outdated reference: A later version (-15) exists of draft-ietf-bess-srv6-services-05 == Outdated reference: A later version (-14) exists of draft-ietf-idr-bgpls-srv6-ext-05 == Outdated reference: A later version (-26) exists of draft-ietf-lsr-flex-algo-13 == Outdated reference: A later version (-19) exists of draft-ietf-lsr-isis-srv6-extensions-11 == Outdated reference: A later version (-13) exists of draft-ietf-rtgwg-segment-routing-ti-lfa-05 == Outdated reference: A later version (-22) exists of draft-ietf-spring-segment-routing-policy-09 == Outdated reference: A later version (-09) exists of draft-ietf-spring-sr-service-programming-03 == Outdated reference: A later version (-10) exists of draft-mirsky-6man-unified-id-sr-08 == Outdated reference: A later version (-07) exists of draft-srcompdt-spring-compression-requirement-03 Summary: 3 errors (**), 0 flaws (~~), 20 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SPRING R. Bonica 3 Internet-Draft Juniper 4 Intended status: Informational W. Cheng 5 Expires: August 23, 2021 China Mobile 6 D. Dukes 7 Cisco Systems 8 W. Henderickx 9 Nokia 10 C. Li 11 Huawei 12 P. Shaofu 13 ZTE 14 C. Xie 15 China Telecom 16 February 19, 2021 18 Compressed SRv6 SID List Analysis 19 draft-srcompdt-spring-compression-analysis-00 21 Abstract 23 Several mechanisms have been proposed to compress the SRv6 SID list. 24 This document analyzes each mechanism with regard to the requirements 25 stated in the companion requirements document. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on August 23, 2021. 44 Copyright Notice 46 Copyright (c) 2021 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. SRv6 Compression Requirements . . . . . . . . . . . . . . . . 3 63 2.1. Encapsulation Header Size . . . . . . . . . . . . . . . . 4 64 2.2. Forwarding Efficiency . . . . . . . . . . . . . . . . . . 4 65 2.2.1. Headers Parsed (PRS) . . . . . . . . . . . . . . . . 4 66 2.2.2. Lookups Performed (LKU) . . . . . . . . . . . . . . . 4 67 2.3. State Efficiency . . . . . . . . . . . . . . . . . . . . 5 68 3. SRv6 Specific Requirements . . . . . . . . . . . . . . . . . 6 69 3.1. SRv6 Based . . . . . . . . . . . . . . . . . . . . . . . 6 70 3.2. Functional Requirements . . . . . . . . . . . . . . . . . 6 71 3.2.1. SRv6 Functionality . . . . . . . . . . . . . . . . . 6 72 3.2.2. Heterogeneous SID Lists . . . . . . . . . . . . . . . 8 73 3.2.3. SID List Length . . . . . . . . . . . . . . . . . . . 8 74 3.2.4. SID Summarization . . . . . . . . . . . . . . . . . . 8 75 3.3. Operational Requirements . . . . . . . . . . . . . . . . 9 76 3.3.1. Lossless Compression . . . . . . . . . . . . . . . . 9 77 3.4. Scalability Requirements . . . . . . . . . . . . . . . . 9 78 4. Protocol Design Requirements . . . . . . . . . . . . . . . . 10 79 4.1. SRv6 Base Coexistance . . . . . . . . . . . . . . . . . . 10 80 5. Security Requirements . . . . . . . . . . . . . . . . . . . . 10 81 5.1. Security Mechanismns . . . . . . . . . . . . . . . . . . 10 82 5.2. SR Domain Protection . . . . . . . . . . . . . . . . . . 10 83 6. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 11 84 7. Normative References . . . . . . . . . . . . . . . . . . . . 12 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 87 1. Introduction 89 The following mechanisms are proposed to compress the SRv6 SID list: 91 o CSID - [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc] - Describes 92 two new SRv6 SIDs, a combination of SIDs from 93 [I-D.filsfils-spring-net-pgm-extension-srv6-usid] and 94 [I-D.cl-spring-generalized-srv6-for-cmpr] 95 o CRH - [I-D.bonica-6man-comp-rtg-hdr] - Requires two new routing 96 header types and a label mapping technique. 98 o VSID - [I-D.decraene-spring-srv6-vlsid] - Defines a set of SID 99 behaviors to access smaller SIDs within the SR header. 100 o UID - [I-D.mirsky-6man-unified-id-sr] - Extends the SRH to carry 101 MPLS labels or IPv4 addresses. 103 This document analyzes each mechanism against the requirements stated 104 in [I-D.srcompdt-spring-compression-requirement]. Each section of 105 this document corresponds to a similarly named section in 106 [I-D.srcompdt-spring-compression-requirement]. Each section 107 reiterates corresponding requirements and analyzes each proposal 108 against the those requirements. 110 2. SRv6 Compression Requirements 112 An SR domain consisting of 3 sub-domains is shown to illustrate the 113 scenarios associated with encapsulation header size, forwarding 114 efficiency and state efficiency. 116 + * * * * * * * * * * * * * * * * * * * * * * * * * * + 117 * * 118 * - - - - - - - - + - - - - - - - - + - - - - - - - - * 119 * | | * 120 * [M1_0] [B5] [C_0] [B7] [M2_0] * 121 [H1]--[E3] | | [E4]---[H2] 122 * [M1_i] [B6] [C_j] [B8] [M2_k] * 123 * | | * 124 * Metro 1 | Core | Metro 2 * 125 *- - - - - - - - - - - - - - - - - - - - - - - - - - -* 126 * * 127 * SR domain * 128 + * * * * * * * * * * * * * * * * * * * * * * * * * * + 130 Figure 1: Sample SR Domain 132 o H1 and H2 are hosts outside the SR domain 133 o E3 and E4 are SR domain edge routers 134 o Metro 1, Core and Metro 2 are sub-domains with independent IGP 135 instances 136 o B5 and B6 are border routers between the Metro 1 and Core 137 o B7 and B8 are border routers between the Metro 2 and Core 138 o M1_1..M1_i are routers in Metro 1 139 o C_1..C_j are routers in Core 140 o M2_1..M2_k are routers in Metro 2 142 2.1. Encapsulation Header Size 144 The compression proposal MUST reduce the size of the SRv6 145 encapsulation header. 147 Encapsulation header size is evaluated against multiple reference 148 scenarios. 150 2.2. Forwarding Efficiency 152 The compression proposal SHOULD minimize the number of required 153 hardware resources accessed to process a segment. 155 2.2.1. Headers Parsed (PRS) 157 This section records and summarizes differences in header parsing for 158 different SID types. 160 o Segment lists may contain transport, adjacency, service, binding 161 or VPN segments. 163 +--------+------+-----+------+-------+ 164 | 16-bit | CSID | CRH | VSID | UIDSR | 165 +--------+------+-----+------+-------+ 166 | | | | | | 167 | | | | | | 168 +--------+------+-----+------+-------+ 170 Table 1: Headers Parsed, 16-bit SIDs 172 +--------+------+-----+------+-------+ 173 | 32-bit | CSID | CRH | VSID | UIDSR | 174 +--------+------+-----+------+-------+ 175 | | | | | | 176 | | | | | | 177 +--------+------+-----+------+-------+ 179 Table 2: Headers Parsed, 32-bit SIDs 181 Conclusion: 183 2.2.2. Lookups Performed (LKU) 185 Some proposals require a different number of lookups per packet, 186 depending on the SID type and segment list. 188 A strict TE path is considered with a 1D(1..15T).V segment list, 189 where each transport segment is an adjacency segment. 191 +---------------------+------+-----+------+-------+ 192 | 16-bit and 32-bit | CSID | CRH | VSID | UIDSR | 193 +---------------------+------+-----+------+-------+ 194 | D.LKU(1D(1..15T).V) | | | | | 195 +---------------------+------+-----+------+-------+ 197 Table 3: Lookups, Strict TE Paths 199 Conclusion: 201 A loose TE path consists of a combination of prefix and adjacency 202 segments 204 +-------------------+------+-----+------+-------+ 205 | 16-bit and 32-bit | CSID | CRH | VSID | UIDSR | 206 +-------------------+------+-----+------+-------+ 207 | | | | | | 208 | | | | | | 209 +-------------------+------+-----+------+-------+ 211 Table 4: Lookups, Loose TE Paths 213 Conclusion: 215 2.3. State Efficiency 217 The compression proposal SHOULD minimize the amount of additional 218 forwarding state stored at a node. 220 State efficiency is analyzed in a single sub-domain of the SR domain, 221 where three parameters are considered: 223 o N: the number of nodes in the sub-domain 224 o I: the number of IGP algorithms [I-D.ietf-lsr-flex-algo] 225 configured 226 o A: the number of local adjacency SIDs 228 For a core sub-domain with 1000 nodes, two IGP algorithms, and 100 229 adjacencies per node: 231 o N=1000, I=2, A=100 232 +-------------------+------+-----+------+-------+ 233 | 16-bit and 32-bit | CSID | CRH | VSID | UIDSR | 234 +-------------------+------+-----+------+-------+ 235 | S(N1000,I2,A100) | | | | | 236 +-------------------+------+-----+------+-------+ 238 Table 5: Forwarding State 240 Conclusion: 242 3. SRv6 Specific Requirements 244 3.1. SRv6 Based 246 A solution to compress SRv6 SID Lists SHOULD be based on the SRv6 247 architecture, control plane and data plane. The compression solution 248 MAY be based on a different data plane and control plane, provided 249 that it derives sufficient benefit. 251 This section records the use of SRv6 standards for compression. 253 +-----------+------+-----+------+-------+ 254 | | CSID | CRH | VSID | UIDSR | 255 +-----------+------+-----+------+-------+ 256 | U.RFC8402 | | | | | 257 | U.RFC8754 | | | | | 258 | U.PGM | | | | | 259 | U.IGP | | | | | 260 | U.BGP | | | | | 261 | U.POL | | | | | 262 | U.BLS | | | | | 263 | U.SVC | | | | | 264 | U.ALG | | | | | 265 | U.OAM | | | | | 266 +-----------+------+-----+------+-------+ 268 Table 6: SRv6 Based 270 Conclusion: 272 3.2. Functional Requirements 274 3.2.1. SRv6 Functionality 276 A solution to compress an SRv6 SID list MUST support the 277 functionality of SRv6. This requirement ensures no SRv6 278 functionality is lost. It is particularly important to understand 279 how a proposal, as evaluated in section "SRv6 Based", provides this 280 functionality. 282 Functional requirements and the drafts defining how a proposal 283 provides the functionality are documented in the table below. 285 +------------------------------------------------------+ 286 | Draft reference Abbreviations | 287 +------------------------------------------------------+ 288 | IDNETPGM: [I-D.ietf-spring-srv6-network-programming] | 289 | IDSRPOL: [I-D.ietf-spring-segment-routing-policy] | 290 | IDEXT: [I-D.ietf-lsr-isis-srv6-extensions] | 291 | IDBGPSVC: [I-D.ietf-bess-srv6-services] | 292 | IDBGPLS: [I-D.ietf-idr-bgpls-srv6-ext] | 293 | IDSVCP: [I-D.ietf-spring-sr-service-programming] | 294 | IDOAM: [I-D.ietf-6man-spring-srv6-oam] | 295 | IDFLEXALG: [I-D.ietf-lsr-flex-algo] | 296 | IDTILFA: [I-D.ietf-rtgwg-segment-routing-ti-lfa] | 297 +------------------------------------------------------+ 299 +---------+------+-----+------+-------+ 300 | | CSID | CRH | VSID | UIDSR | 301 +---------+------+-----+------+-------+ 302 | F.SID | | | | | 303 | F.Scope | | | | | 304 | F.PFX | | | | | 305 | F.ADJ | | | | | 306 | F.BIND | | | | | 307 | F.PEER | | | | | 308 | F.SVC | | | | | 309 | F.ALG | | | | | 310 | F.TILFA | | | | | 311 | F.SEC | | | | | 312 | F.IGP | | | | | 313 | F.BGP | | | | | 314 | F.POL | | | | | 315 | F.BLS | | | | | 316 | F.SFC | | | | | 317 | F.PING | | | | | 318 +---------+------+-----+------+-------+ 320 Table 7: SRv6 Functionality 322 Conclusion: 324 3.2.2. Heterogeneous SID Lists 326 The compression proposal SHOULD support a combination of compressed 327 and non-compressed segments in a single path. As an example, a 328 solution may satisfy this requirement without being SRv6 based by 329 using a binding SID to impose an additional SRv6 header (IPv6 header 330 plus optional SRH) with non-compressed SID. 332 +-------------------------+------+-----+------+-------+ 333 | | CSID | CRH | VSID | UIDSR | 334 +-------------------------+------+-----+------+-------+ 335 | Heterogeneous SID Lists | | | | | 336 +-------------------------+------+-----+------+-------+ 338 Conclusion: 340 3.2.3. SID List Length 342 The compression proposal MUST be able to represent SR paths that 343 contain up to 16 segments. 345 +-------------+------+-----+------+-------+ 346 | | CSID | CRH | VSID | UIDSR | 347 +-------------+------+-----+------+-------+ 348 | 16 Segments | | | | | 349 +-------------+------+-----+------+-------+ 351 Conclusion: 353 3.2.4. SID Summarization 355 The solution MUST be compatible with segment summarization. 357 In inter sub-domain deployments with summarization: 359 o Any node can reach any other node in another sub-domain via a 360 prefix segment. 361 o Prefixes are summarized for advertisement between domains. 363 Without summarization, border router SIDs must be leaked: 365 o An additional global prefix segment is required for each domain 366 border to be traversed. 368 +-------------------+------+-----+------+-------+ 369 | | CSID | CRH | VSID | UIDSR | 370 +-------------------+------+-----+------+-------+ 371 | SID Summarization | | | | | 372 +-------------------+------+-----+------+-------+ 374 Conclusion: 376 3.3. Operational Requirements 378 3.3.1. Lossless Compression 380 A path traversed using a compressed SID list MUST always be the same 381 as the path traversed using the uncompressed SID list if no 382 compression was applied. 384 +----------------------+------+-----+------+-------+ 385 | | CSID | CRH | VSID | UIDSR | 386 +----------------------+------+-----+------+-------+ 387 | Lossless Compression | | | | | 388 +----------------------+------+-----+------+-------+ 390 Conclusion: 392 3.4. Scalability Requirements 394 The compression proposal MUST be capable of representing 65000 395 adjacency segments per node. 397 The compression proposal MUST be capable of representing 1 million 398 prefix segments per SID numbering space. 400 The compression proposal MUST be capable of representing 1 million 401 services per node. 403 +-------------------------------+------+-----+------+-------+ 404 | | CSID | CRH | VSID | UIDSR | 405 +-------------------------------+------+-----+------+-------+ 406 | Adjacency Segment Scale 65000 | | | | | 407 | Prefix Segment Scale 1000000 | | | | | 408 | Service Scale 1000000 | | | | | 409 +-------------------------------+------+-----+------+-------+ 411 Table 8: Scale Requirements 413 Conclusion: 415 4. Protocol Design Requirements 417 4.1. SRv6 Base Coexistance 419 The compression proposal MUST support deployment in existing SRv6 420 networks. 422 +-----------------------+------+-----+------+-------+ 423 | | CSID | CRH | VSID | UIDSR | 424 +-----------------------+------+-----+------+-------+ 425 | SRv6 Base Coexistence | | | | | 426 +-----------------------+------+-----+------+-------+ 428 Conclusion: 430 5. Security Requirements 432 5.1. Security Mechanismns 434 The compression solution SHOULD be able to address security issues 435 that it introduces, using existing security mechanisms. 437 +---------------------+------+-----+------+-------+ 438 | | CSID | CRH | VSID | UIDSR | 439 +---------------------+------+-----+------+-------+ 440 | Security Mechanisms | | | | | 441 +---------------------+------+-----+------+-------+ 443 Conclusion: 445 5.2. SR Domain Protection 447 A compression solution must not require nodes outside the SR domain 448 to know SID values within the SR domain, and it must provide the 449 ability to block nodes outside an SR domain from accessing SIDS. 451 +----------------------+------+-----+------+-------+ 452 | | CSID | CRH | VSID | UIDSR | 453 +----------------------+------+-----+------+-------+ 454 | SR Domain Protection | | | | | 455 +----------------------+------+-----+------+-------+ 457 Conclusion: 459 6. Conclusions 461 Encapsulation Header Size 463 - 465 Forwarding Efficiency 467 - 469 State Efficiency 471 - 473 SRv6 Based 475 - 477 SRv6 Functionality 479 - 481 Heterogeneous SID lists 483 - 485 SID List Length 487 - 489 SID Summarization 491 - 493 Operational Requirements 495 - 497 Protocol Design Requirements 499 - 501 Scalability Requirements 503 - 505 Protocol Design Requirements 506 - 508 Security Requirements 510 - 512 7. Normative References 514 [I-D.bonica-6man-comp-rtg-hdr] 515 Bonica, R., Kamite, Y., Alston, A., Henriques, D., and L. 516 Jalil, "The IPv6 Compact Routing Header (CRH)", draft- 517 bonica-6man-comp-rtg-hdr-24 (work in progress), January 518 2021. 520 [I-D.cl-spring-generalized-srv6-for-cmpr] 521 Cheng, W., Li, Z., Li, C., Clad, F., Aihua, L., Xie, C., 522 Liu, Y., and S. Zadok, "Generalized SRv6 Network 523 Programming for SRv6 Compression", draft-cl-spring- 524 generalized-srv6-for-cmpr-02 (work in progress), November 525 2020. 527 [I-D.decraene-spring-srv6-vlsid] 528 Decraene, B., Raszuk, R., Li, Z., and C. Li, "SRv6 vSID: 529 Network Programming extension for variable length SIDs", 530 draft-decraene-spring-srv6-vlsid-04 (work in progress), 531 September 2020. 533 [I-D.filsfils-spring-net-pgm-extension-srv6-usid] 534 Filsfils, C., Camarillo, P., Cai, D., Voyer, D., Meilik, 535 I., Patel, K., Henderickx, W., Jonnalagadda, P., Melman, 536 D., Liu, Y., and J. Guichard, "Network Programming 537 extension: SRv6 uSID instruction", draft-filsfils-spring- 538 net-pgm-extension-srv6-usid-08 (work in progress), 539 November 2020. 541 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc] 542 Cheng, W., Filsfils, C., Li, Z., Cai, D., Voyer, D., Clad, 543 F., Zadok, S., Guichard, J., and L. Aihua, "Compressed 544 SRv6 Segment List Encoding in SRH", draft-filsfilscheng- 545 spring-srv6-srh-comp-sl-enc-02 (work in progress), 546 November 2020. 548 [I-D.ietf-6man-spring-srv6-oam] 549 Ali, Z., Filsfils, C., Matsushima, S., Voyer, D., and M. 550 Chen, "Operations, Administration, and Maintenance (OAM) 551 in Segment Routing Networks with IPv6 Data plane (SRv6)", 552 draft-ietf-6man-spring-srv6-oam-08 (work in progress), 553 October 2020. 555 [I-D.ietf-bess-srv6-services] 556 Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R., 557 Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based 558 Overlay services", draft-ietf-bess-srv6-services-05 (work 559 in progress), November 2020. 561 [I-D.ietf-idr-bgpls-srv6-ext] 562 Dawra, G., Filsfils, C., Talaulikar, K., Chen, M., 563 daniel.bernier@bell.ca, d., and B. Decraene, "BGP Link 564 State Extensions for SRv6", draft-ietf-idr-bgpls- 565 srv6-ext-05 (work in progress), November 2020. 567 [I-D.ietf-lsr-flex-algo] 568 Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and 569 A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex- 570 algo-13 (work in progress), October 2020. 572 [I-D.ietf-lsr-isis-srv6-extensions] 573 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 574 Z. Hu, "IS-IS Extension to Support Segment Routing over 575 IPv6 Dataplane", draft-ietf-lsr-isis-srv6-extensions-11 576 (work in progress), October 2020. 578 [I-D.ietf-rtgwg-segment-routing-ti-lfa] 579 Litkowski, S., Bashandy, A., Filsfils, C., Decraene, B., 580 and D. Voyer, "Topology Independent Fast Reroute using 581 Segment Routing", draft-ietf-rtgwg-segment-routing-ti- 582 lfa-05 (work in progress), November 2020. 584 [I-D.ietf-spring-segment-routing-policy] 585 Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and 586 P. Mattes, "Segment Routing Policy Architecture", draft- 587 ietf-spring-segment-routing-policy-09 (work in progress), 588 November 2020. 590 [I-D.ietf-spring-sr-service-programming] 591 Clad, F., Xu, X., Filsfils, C., daniel.bernier@bell.ca, 592 d., Li, C., Decraene, B., Ma, S., Yadlapalli, C., 593 Henderickx, W., and S. Salsano, "Service Programming with 594 Segment Routing", draft-ietf-spring-sr-service- 595 programming-03 (work in progress), September 2020. 597 [I-D.ietf-spring-srv6-network-programming] 598 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 599 Matsushima, S., and Z. Li, "SRv6 Network Programming", 600 draft-ietf-spring-srv6-network-programming-28 (work in 601 progress), December 2020. 603 [I-D.mirsky-6man-unified-id-sr] 604 Cheng, W., Mirsky, G., Peng, S., Aihua, L., and G. Mishra, 605 "Unified Identifier in IPv6 Segment Routing Networks", 606 draft-mirsky-6man-unified-id-sr-08 (work in progress), 607 January 2021. 609 [I-D.srcompdt-spring-compression-requirement] 610 Cheng, W., "Compressed SRv6 SID List Requirements", draft- 611 srcompdt-spring-compression-requirement-03 (work in 612 progress), January 2021. 614 Authors' Addresses 616 Ron Bonica 617 Juniper 619 Email: rbonica@juniper.net 621 Weiqiang Cheng 622 China Mobile 624 Email: chengweiqiang@chinamobile.com 626 Darren Dukes 627 Cisco Systems 629 Email: ddukes@cisco.com 631 Wim Henderickx 632 Nokia 634 Email: wim.henderickx@nokia.com 636 Cheng Li 637 Huawei 639 Email: c.l@huawei.com 641 Peng Shaofu 642 ZTE 644 Email: peng.shaofu@zte.com.cn 645 Chongfeng Xie 646 China Telecom 648 Email: xiechf@chinatelecom.cn