idnits 2.17.1 draft-cheng-spring-ipv6-msr-design-consideration-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 : ---------------------------------------------------------------------------- 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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 12, 2021) is 1017 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC8296' is defined on line 288, but no explicit reference was found in the text == Unused Reference: 'RFC8663' is defined on line 299, but no explicit reference was found in the text == Outdated reference: A later version (-06) exists of draft-dong-6man-enhanced-vpn-vtn-id-03 == Outdated reference: A later version (-05) exists of draft-geng-spring-sr-redundancy-protection-02 == Outdated reference: A later version (-08) exists of draft-ietf-idr-sr-policy-path-mtu-02 == Outdated reference: A later version (-17) exists of draft-ietf-ippm-ioam-data-12 == Outdated reference: A later version (-07) exists of draft-ietf-spring-srv6-path-segment-00 == Outdated reference: A later version (-25) exists of draft-ietf-teas-ietf-network-slices-00 == Outdated reference: A later version (-07) exists of draft-li-apn-framework-02 == Outdated reference: A later version (-07) exists of draft-srcompdt-spring-compression-requirement-06 Summary: 0 errors (**), 0 flaws (~~), 12 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group W. Cheng 3 Internet-Draft China Mobile 4 Intended status: Informational G. Mishra 5 Expires: January 13, 2022 Verizon Inc. 6 Z. Li 7 Huawei Technologies 8 A. Wang 9 China Telecom 10 Z. Qin 11 China Unicom 12 C. Fan 13 New H3C Technologies 14 July 12, 2021 16 Design Consideration of IPv6 Multicast Source Routing (MSR6) 17 draft-cheng-spring-ipv6-msr-design-consideration-00 19 Abstract 21 This document discusses the design consideration of IPv6 source 22 routing multicast solution. 24 Requirements Language 26 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 27 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 28 document are to be interpreted as described in RFC 2119 [RFC2119]. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at https://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on January 13, 2022. 47 Copyright Notice 49 Copyright (c) 2021 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (https://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 65 2. Design Consideration . . . . . . . . . . . . . . . . . . . . 3 66 3. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 68 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 69 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 70 7. Normative References . . . . . . . . . . . . . . . . . . . . 5 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 73 1. Introduction 75 Multicast could provide efficient P2MP service without bandwidth 76 waste. The increasing amount of live video traffic in the network 77 bring new requirements for multicast solutions. The existing 78 multicast solutions request multicast tree-building on control plane 79 and maintaining end-to-end tree state per flow, which impacts router 80 state capacity and network convergence time. There has been a lot of 81 work in IETF to simplify service deployment, in which Source Routing 82 is a very important technology, including SRv6, BIER, etc. Source 83 routing is able to reduce the state of intermediate nodes and 84 indicate multicast forwarding in the ingress nodes, which could 85 simplify multicast deployment. Source routing requires sufficient 86 flexibility on the forwarding plane and IPv6 has the advantage with 87 good scalability. Therefore, it is important to simplify multicast 88 deployment and meet high quality service requirements with IPv6 89 Source Routing based multicast. 91 This document discusses the design consideration of IPv6 multicast 92 source routing (MSR6) solution. The definition of the new IPv6 93 multicast source routing solution is out of the scope of this 94 document. 96 2. Design Consideration 98 Firstly, MSR6 needs to support the basic multicast functionalities, 99 including: 101 o P2MP Forwarding: replicate and forward multicast packet to the 102 next replication nodes; 104 o Multicast Flow Overlay: multicast service, such as MVPN 106 o P2MP OAM functions: Ping/Traceroute/BFD 108 In addition to this, it is necessary for MSR6 to meet the need of 109 high quality service with high reliability, including: 111 o Traffic Engineering: explicit path specification to satisfy 112 different kinds of requirements 114 o FRR 116 o E2E Protection 118 o Advanced network measurement functions, including: performance 119 measurement and In-situ Flow Information Telemetry, which is the 120 basis for traffic engineering and high quality transport service. 122 The IPv6 multicast source routing should take use of the advantages 123 of source routing to reduce the state of the network as much as 124 possible. That is, it should satisfy the above requirements with 125 high scalability. 127 However, MSR6 is not about starting from scratch. The existing IETF 128 work should be reused as much as possible: 130 o BIER 132 Bit Index Explicit Replication (BIER) defined in [RFC8279] is an 133 architecture providing optimal multicast forwarding without requiring 134 intermediate routers to maintain any per-flow state by using a 135 multicast-specific BIER header. BIER use bitstring in the BIER 136 header to indicate leaf nodes which gives an efficient solution for 137 Best Effort multicast flow without the requirement of Traffic 138 Engineering. 140 o SRv6([RFC8986]) 142 SRv6 has advantages in indicating explicit paths, which brings 143 convenience for unicast TE and FRR. MSR6 TE should refer to the 144 experience of SRv6. In addition, SRv6 provides flexible path 145 programming capability with the definition of different type of 146 segments. MSR6 could make use the of existing segments in the design 147 of TE/FRR . For example, path segment 148 ([I-D.ietf-spring-srv6-path-segment]) could help to enhance the 149 performance measurement capability. In the meantime, SRv6 150 compression ([I-D.srcompdt-spring-compression-requirement]) is under 151 discussion to reduce encapsulation overhead, which could also be 152 reused by MSR6. 154 o The existing and ongoing IPv6 extensions 156 1) Existing functionalities including fragmentation and security 158 Multicast packets need to be fragmented and secured as they pass 159 through the IPv6 network. This can be done using IPv6 Fragmentation 160 and ESP(Encapsulating Security Payload) defined in [RFC8200]. Work 161 about Path MTU [I-D.ietf-idr-sr-policy-path-mtu] which supports 162 fragmentation, is also under discussion. All these existing work 163 should be reused in the MSR6. 165 2) New network functionalities based on the ongoing IPv6 Extensions, 166 including Network Slicing, Deterministic Networking(DetNet), 167 IOAM.etc. 169 Network slicing ([I-D.ietf-teas-ietf-network-slices]) and DetNet 170 ([RFC8655]) are being introduced to satisfy the quality service 171 requirements of critical services. IOAM ([I-D.ietf-ippm-ioam-data]) 172 is also introduced to implement in-situ network measurement. IPv6 173 data plane is being used to support network slicing 174 ([I-D.li-6man-e2e-ietf-network-slicing] and 175 [I-D.dong-6man-enhanced-vpn-vtn-id]), Detnet 176 ([I-D.geng-spring-srv6-for-detnet] and 177 [I-D.geng-spring-sr-redundancy-protection]), IOAM 178 ([I-D.ietf-ippm-ioam-data]), etc. Multicast service can also benefit 179 from these new network functionalities to improve quality of service. 180 MSR6 could reuse the ongoing work based on IPv6 extensions to 181 implement the functionalities for multicast services. 183 3) Future possible work based on IPv6 extensions, including 184 Application Aware Network (APN) 186 APN ([I-D.li-apn-framework]) is used to provide more granular 187 services, which can use IPv6 extension header to carry APN 188 information for the purpose of steering traffic, etc. MSR6 can 189 combine with APN to map the traffic to different Network-based 190 multicast services/functionalities according to the APN information 191 in the IPv6 data plane. 193 4) MSR6 is also supposed to be started at the Host based on IPv6 195 In [RFC8754], it is supposed that a host can originate the IPv6 196 source routing packet. MSR6 should take use of the native IPv6 197 design and support originating the IPv6 packet by the host. 199 3. Conclusion 201 A new IPv6 multicast source routing solution is requested based on 202 the design consideration listed above. 204 4. IANA Considerations 206 This document makes no request of IANA. 208 Note to RFC Editor: this section may be removed on publication as an 209 RFC. 211 5. Security Considerations 213 6. Acknowledgements 215 7. Normative References 217 [I-D.dong-6man-enhanced-vpn-vtn-id] 218 Dong, J., Li, Z., Xie, C., and C. Ma, "Carrying Virtual 219 Transport Network Identifier in IPv6 Extension Header", 220 draft-dong-6man-enhanced-vpn-vtn-id-03 (work in progress), 221 February 2021. 223 [I-D.geng-spring-sr-redundancy-protection] 224 Geng, X., Chen, M., and F. Yang, "Segment Routing for 225 Redundancy Protection", draft-geng-spring-sr-redundancy- 226 protection-02 (work in progress), February 2021. 228 [I-D.geng-spring-srv6-for-detnet] 229 Geng, X., Li, Z., and M. Chen, "SRv6 for Deterministic 230 Networking (DetNet)", draft-geng-spring-srv6-for-detnet-01 231 (work in progress), July 2020. 233 [I-D.ietf-idr-sr-policy-path-mtu] 234 Li, C., Zhu, Y., Sawaf, A. E., and Z. Li, "Segment Routing 235 Path MTU in BGP", draft-ietf-idr-sr-policy-path-mtu-02 236 (work in progress), November 2020. 238 [I-D.ietf-ippm-ioam-data] 239 Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields 240 for In-situ OAM", draft-ietf-ippm-ioam-data-12 (work in 241 progress), February 2021. 243 [I-D.ietf-spring-srv6-path-segment] 244 Li, C., Cheng, W., Chen, M., Dhody, D., and R. Gandhi, 245 "Path Segment for SRv6 (Segment Routing in IPv6)", draft- 246 ietf-spring-srv6-path-segment-00 (work in progress), 247 November 2020. 249 [I-D.ietf-teas-ietf-network-slices] 250 Farrel, A., Gray, E., Drake, J., Rokui, R., Homma, S., 251 Makhijani, K., Contreras, L. M., and J. Tantsura, 252 "Framework for IETF Network Slices", draft-ietf-teas-ietf- 253 network-slices-00 (work in progress), April 2021. 255 [I-D.li-6man-e2e-ietf-network-slicing] 256 Li, Z. and J. Dong, "Encapsulation of End-to-End IETF 257 Network Slice Information in IPv6", draft-li-6man-e2e- 258 ietf-network-slicing-00 (work in progress), April 2021. 260 [I-D.li-apn-framework] 261 Li, Z., Peng, S., Voyer, D., Li, C., Liu, P., Cao, C., 262 Ebisawa, K., Previdi, S., and J. N. Guichard, 263 "Application-aware Networking (APN) Framework", draft-li- 264 apn-framework-02 (work in progress), February 2021. 266 [I-D.srcompdt-spring-compression-requirement] 267 Cheng, W., Xie, C., Bonica, R., Dukes, D., Li, C., Shaofu, 268 P., and W. Henderickx, "Compressed SRv6 SID List 269 Requirements", draft-srcompdt-spring-compression- 270 requirement-06 (work in progress), March 2021. 272 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 273 Requirement Levels", BCP 14, RFC 2119, 274 DOI 10.17487/RFC2119, March 1997, 275 . 277 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 278 (IPv6) Specification", STD 86, RFC 8200, 279 DOI 10.17487/RFC8200, July 2017, 280 . 282 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 283 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 284 Explicit Replication (BIER)", RFC 8279, 285 DOI 10.17487/RFC8279, November 2017, 286 . 288 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 289 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 290 for Bit Index Explicit Replication (BIER) in MPLS and Non- 291 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 292 2018, . 294 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 295 "Deterministic Networking Architecture", RFC 8655, 296 DOI 10.17487/RFC8655, October 2019, 297 . 299 [RFC8663] Xu, X., Bryant, S., Farrel, A., Hassan, S., Henderickx, 300 W., and Z. Li, "MPLS Segment Routing over IP", RFC 8663, 301 DOI 10.17487/RFC8663, December 2019, 302 . 304 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 305 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 306 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 307 . 309 [RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer, 310 D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 311 (SRv6) Network Programming", RFC 8986, 312 DOI 10.17487/RFC8986, February 2021, 313 . 315 Authors' Addresses 317 Weiqiang Cheng 318 China Mobile 320 Email: chengweiqiang@chinamobile.com 322 Gyan Mishra 323 Verizon Inc. 325 Email: gyan.s.mishra@verizon.com 326 Zhenbin Li 327 Huawei Technologies 329 Email: lizhenbin@huawei.com 331 Aijun Wang 332 China Telecom 334 Email: wangaj3@chinatelecom.cn 336 Zhuangzhuang Qin 337 China Unicom 339 Email: qinzhuangzhuang@chinaunicom.cn 341 Chi Fan 342 New H3C Technologies 344 Email: fanchi@h3c.com