idnits 2.17.1 draft-filsfils-spring-sr-mpls-ipv6-control-plane-04.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 date (May 24, 2021) is 1066 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-22) exists of draft-ietf-spring-segment-routing-policy-11 == Outdated reference: A later version (-09) exists of draft-ietf-spring-sr-service-programming-04 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SPRING C. Filsfils, Ed. 3 Internet-Draft F. Clad, Ed. 4 Intended status: Informational K. Talaulikar 5 Expires: November 25, 2021 Cisco Systems 6 May 24, 2021 8 SR-MPLS Data Plane with IPv6 Control Plane 9 draft-filsfils-spring-sr-mpls-ipv6-control-plane-04 11 Abstract 13 This document reminds the existence of the "Segment Routing (SR) MPLS 14 data-plane with IPv6 control-plane" solution that is mature from a 15 standardization, productization and commercial deployment viewpoint. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on November 25, 2021. 34 Copyright Notice 36 Copyright (c) 2021 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (https://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Context . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 3. Reference diagram . . . . . . . . . . . . . . . . . . . . . . 3 54 4. Packet processing . . . . . . . . . . . . . . . . . . . . . . 4 55 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 56 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 57 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 58 8. Informative References . . . . . . . . . . . . . . . . . . . 5 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 61 1. Introduction 63 This document reminds the existence of the "Segment Routing (SR) MPLS 64 dataplane with IPv6 control-plane". This solution is mature from a 65 standardization, productization and commercial deployment viewpoint. 66 Other proposed source routing solutions with MPLS-like label lookup 67 or mapping ids should list all their data-plane and control-plane 68 differences with respect to this mature solution and should justify 69 these differences with genuine benefits not available in the mature 70 solution described in this document and others referenced here that 71 are published by the SPRING and MPLS WGs. 73 2. Context 75 This is an existing solution. 77 o Mature IETF standardization 79 o Mature productization 81 o Commercially deployed 83 The IETF standardization references are: 85 o Architecture: 87 * Segment Routing [RFC8402] 89 o Data-plane: 91 * Homogenous MPLS deployment: [RFC8660] 93 * Hopping over IP-only parts of network: [RFC8663] 95 o Control-plane: 97 * IS-IS: [RFC8667] 99 * OSPFv3: [RFC8666] 101 * BGP: [RFC4364] 103 * BGP-LS: [I-D.ietf-idr-bgp-ls-segment-routing-ext] 105 * SR Policy headend: [I-D.ietf-spring-segment-routing-policy] 107 o Service programming: [I-D.ietf-spring-sr-service-programming] 109 o OAM: [RFC8287] 111 3. Reference diagram 113 +--------------------------------------------------------------+ 114 | +-------------------+ +-------------------+ | 115 | | | | | | 116 | | +-+-+ +-+-+ | | 117 | | |121| |231| | | 118 | | +-+-+ +-+-+ | | 119 | | +---+ | | +---+ | | 120 | | |PE1| | | |PE2| | | 121 | | +---+ +-+-+ +-+-+ +---+ | | 122 | | |122| |232| | | 123 | | +-+-+ +-+-+ | | 124 | | (MPLS island 1) | | (MPLS island 2) | | 125 | +-------------------+ (IPv6 network) +-------------------+ | 126 +--------------------------------------------------------------+ 128 Figure 1: IPv6 network with SR-MPLS islands 130 o Single IGP domain, IPv6 only 132 * PE1 is configured with a loopback IP address 2001:db8::1 134 * PE2 is configured with a loopback IP address 2001:db8::2 136 * Each other node k is configured with a loopback IP address 137 2001:db8::k 139 o 2 SR-MPLS islands running with an IPv6 control plane 141 * PE1 is configured with a Prefix-SID 16001 associated with 142 2001:db8::1 144 * PE2 is configured with a Prefix-SID 16002 associated with 145 2001:db8::2 147 4. Packet processing 149 +------------------------------------------------------------+ 150 | +-------------------+ +-------------------+ | 151 | | | | | | 152 | | +-+-+ +-+-+ | | 153 | | +---->+121+----->------+231+-----+ | | 154 | | | +-+-+ +-+-+ | | | 155 | | +---+ | | | | +---+ | | 156 A +-----+PE1+-----+ | | +---->+PE2+-----> B 157 | | +---+ +-+-+ +-+-+ +---+ | | 158 | | |122| |232| | | 159 | | +-+-+ +-+-+ | | 160 | | (MPLS island 1) | | (MPLS island 2) | | 161 | +-------------------+ (IPv6 network) +-------------------+ | 162 +------------------------------------------------------------+ 164 +----------+ +----------+ +--------------+ +----------+ +----------+ 165 | IP4(A,B) | | 16002 | |IP6( | | 16002 | | IP4(A,B) | 166 +----------+ +----------+ |2001:db8::121,| +----------+ +----------+ 167 | 12345 | |2001:db8::231)| | 12345 | 168 +----------+ +--------------+ +----------+ 169 | IP4(A,B) | | 16002 | | IP4(A,B) | 170 +----------+ +--------------+ +----------+ 171 | 12345 | 172 +--------------+ 173 | IP4(A,B) | 174 +--------------+ 176 Figure 2: Packet processing in IPv6 network with SR-MPLS islands 178 o PE1 receives IPv4 traffic from A and headed to B 180 o PE1 PUSHes the VPN label 12345 and the prefix-SID 16002 of PE2 182 o Traffic is steered in MPLS island 1 according to the top label 183 16002 185 o Traffic reaches node 121, whose next-hop towards 16002 is not 186 MPLS-enabled 188 * Node 121 has determined(*) that traffic to 16002 should be sent 189 over an IPv6 encapsulation to node 231 191 * Node 121 encapsulates the traffic with IPv6 header (Next Header 192 137 [RFC4023]) to 2001:db8::231 194 o Node 231 removes the IPv6 encapsulation, exposes the MPLS label 195 16002 and forwards the traffic accordingly 197 o Traffic is steered in MPLS island 2 according to the top label 198 16002 200 o (PHP: Penultimate node POPs label 16002 and sends the traffic to 201 PE2) 203 o PE2 looks up the exposed VPN label 12345 and forwards the traffic 204 accordingly. 206 (*) Node 121 determines that node 231 is the closest MPLS- and IPv6- 207 pop-capable node on the shortest path to PE2 using a technique 208 outside the scope of the document. 210 5. Security Considerations 212 None 214 6. IANA Considerations 216 None 218 7. Acknowledgements 220 TBD 222 8. Informative References 224 [I-D.ietf-idr-bgp-ls-segment-routing-ext] 225 Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H., 226 and M. Chen, "BGP Link-State extensions for Segment 227 Routing", draft-ietf-idr-bgp-ls-segment-routing-ext-18 228 (work in progress), April 2021. 230 [I-D.ietf-spring-segment-routing-policy] 231 Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and 232 P. Mattes, "Segment Routing Policy Architecture", draft- 233 ietf-spring-segment-routing-policy-11 (work in progress), 234 April 2021. 236 [I-D.ietf-spring-sr-service-programming] 237 Clad, F., Xu, X., Filsfils, C., Bernier, D., Li, C., 238 Decraene, B., Ma, S., Yadlapalli, C., Henderickx, W., and 239 S. Salsano, "Service Programming with Segment Routing", 240 draft-ietf-spring-sr-service-programming-04 (work in 241 progress), March 2021. 243 [RFC4023] Worster, T., Rekhter, Y., and E. Rosen, Ed., 244 "Encapsulating MPLS in IP or Generic Routing Encapsulation 245 (GRE)", RFC 4023, DOI 10.17487/RFC4023, March 2005, 246 . 248 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 249 Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 250 2006, . 252 [RFC8287] Kumar, N., Ed., Pignataro, C., Ed., Swallow, G., Akiya, 253 N., Kini, S., and M. Chen, "Label Switched Path (LSP) 254 Ping/Traceroute for Segment Routing (SR) IGP-Prefix and 255 IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data 256 Planes", RFC 8287, DOI 10.17487/RFC8287, December 2017, 257 . 259 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 260 Decraene, B., Litkowski, S., and R. Shakir, "Segment 261 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 262 July 2018, . 264 [RFC8660] Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S., 265 Decraene, B., Litkowski, S., and R. Shakir, "Segment 266 Routing with the MPLS Data Plane", RFC 8660, 267 DOI 10.17487/RFC8660, December 2019, 268 . 270 [RFC8663] Xu, X., Bryant, S., Farrel, A., Hassan, S., Henderickx, 271 W., and Z. Li, "MPLS Segment Routing over IP", RFC 8663, 272 DOI 10.17487/RFC8663, December 2019, 273 . 275 [RFC8666] Psenak, P., Ed. and S. Previdi, Ed., "OSPFv3 Extensions 276 for Segment Routing", RFC 8666, DOI 10.17487/RFC8666, 277 December 2019, . 279 [RFC8667] Previdi, S., Ed., Ginsberg, L., Ed., Filsfils, C., 280 Bashandy, A., Gredler, H., and B. Decraene, "IS-IS 281 Extensions for Segment Routing", RFC 8667, 282 DOI 10.17487/RFC8667, December 2019, 283 . 285 Authors' Addresses 287 Clarence Filsfils (editor) 288 Cisco Systems 290 Email: cfilsfil@cisco.com 292 Francois Clad (editor) 293 Cisco Systems 295 Email: fclad@cisco.com 297 Ketan Talaulikar 298 Cisco Systems 300 Email: ketant@cisco.com