idnits 2.17.1 draft-filsfils-spring-net-pgm-srv6-usid-illus-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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 2 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 25, 2020) is 1522 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-16) exists of draft-filsfils-spring-net-pgm-extension-srv6-usid-03 == Outdated reference: A later version (-04) exists of draft-filsfils-spring-srv6-net-pgm-illustration-01 == Outdated reference: A later version (-28) exists of draft-ietf-spring-srv6-network-programming-10 Summary: 3 errors (**), 0 flaws (~~), 5 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 P. Camarillo, Ed. 4 Intended status: Informational Cisco Systems, Inc. 5 Expires: August 28, 2020 D. Cai 6 Alibaba 7 D. Voyer 8 Bell Canada 9 I. Meilik 10 Broadcom 11 K. Patel 12 Arrcus, Inc. 13 W. Henderickx 14 Nokia 15 P. Jonnalagadda 16 Barefoot Networks 17 D. Melman 18 Marvell 19 February 25, 2020 21 NET-PGM extension: SRv6 uSID illustration 22 draft-filsfils-spring-net-pgm-srv6-usid-illus-00 24 Abstract 26 This document illustrates the SRv6 "micro segment" (SRv6 uSID or uSID 27 for short) instruction. 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 August 28, 2020. 46 Copyright Notice 48 Copyright (c) 2020 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. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 2 65 2.1. Reference diagram . . . . . . . . . . . . . . . . . . . . 3 66 2.2. SRv6 overlay with underlay optimization . . . . . . . . . 3 67 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 68 4. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 69 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 72 1. Introduction 74 SRv6 Network Programming [I-D.ietf-spring-srv6-network-programming] 75 defines a mechanism to build a network program with topological and 76 service segments. It leverages the SRH 77 [I-D.ietf-6man-segment-routing-header] to encode a network program 78 together with optional metadata shared among the different SIDs. 80 [I-D.filsfils-spring-net-pgm-extension-srv6-usid] draft extends SRv6 81 Network Programming with a new type of SRv6 SID behavior: SRv6 uN. 82 This document illustrates it. 84 2. Illustration 86 This section extends the illustrations for SRv6 Network Programming 87 [I-D.filsfils-spring-srv6-net-pgm-illustration] to cover uSID. The 88 reference topology is the same with the addition of link 6-8. 90 2.1. Reference diagram 92 Nodes 1 to 8 are considered within the network domain. 94 Nodes X and Y are outside the domain. 96 Nodes 1 and 8 act as PE respectively to nodes X and Y. 98 All the links within the domain have the same IGP metric. The IGP- 99 metric shortest-path from 1 to 8 is 1-2-7-8 while the latency-metric 100 shortest-path from 1 to 8 is 1-2-3-4-5-6-7-8. 102 3------4---5 103 | \ / 104 | 6 105 | / \ 106 1--- 2------7---8 107 / \ 108 X Y 109 Tenant100 Tenant100 with 110 IPv4 20/8 112 Figure 1: Reference topology 114 2.2. SRv6 overlay with underlay optimization 116 Let us illustrate a low-latency SR-L3VPN service delivered to a 117 packet (X,Y). 119 PE 1 encapsulates (X, Y) in an outer IPv6 header with DA = 120 2001:db8:0300:0500:0700:: and SRH (B:8:D0::; SL=1; NH=4). Leveraging 121 the illustration conventions from SRv6 network programming, the 122 following resulting packet leaves node 1 in the direction of node 3: 124 (A1::, 2001:db8:0300:0500:0700::)(B:8:D0::; SL=1; NH=4)(X, Y) 126 2001:db8:0300:0500:0700:: is a uSID carrier encoding a source routed 127 stateless path via node 3 then 5 then 7. 129 B:8:D0:: is an End.DT4 SID instantiated at node 8. 131 1 sends this packet to 2, as 2 is on the shortest-path to 132 2001:db8:0300::/48 advertised by 3. 134 When 2 receives the packet, 2 performs a regular IPv6 FIB lookup. It 135 finds a FIB entry for 2001:db8:0300::/48 and forwards along the 136 shortest path to 3. 138 When 3 receives the packet, 3 matches 2001:db8:0300::/48 in its "My 139 SID Table" and executes the uN behavior. The updated DA becomes 140 2001:db8:0500:0700::. Node 3 then performs a lookup on the updated DA 141 and forwards the packet to 5 along the shortest path to 142 2001:db8:0500::/48. 144 The following packet leaves node 3: 146 (A1::, 2001:db8:0500:0700::)(B:8:D0::; SL=1; NH=4)(X, Y) 148 4 forwards along the shortest path to 2001:db8:0500::/48. 150 When 5 receives the packet, 5 matches 2001:db8:0500::/48 in its "My 151 SID Table" and executes the uN behavior. The updated DA becomes 152 2001:db8:0700::. 5 performs a lookup on the updated DA and forwards 153 the packet to 7 along the shortest path to 2001:db8:0700::/48. 155 The following packet leaves node 5: 157 (A1::, 2001:db8:0700::)(B:8:D0::; SL=1; NH=4)(X, Y) 159 6 forwards along the shortest path to 2001:db8:0700::/48. 161 When 7 receives the packet, 7 matches 2001:db8:0700::/48 in its "My 162 SID Table" and finds the bound function uN. As a result, Node 7 163 executes the "End with PSP and USD support" pseudocode, decrementing 164 the SL value in the SRH, and updating the DA with the next SID 165 B:8:D0::. Since the SL value is zero the SRH is removed. Node 7 166 performs a lookup on the updated DA and forwards along the shortest 167 path. 169 The following packet leaves node 7: 171 (A1::, B:8:D0::)(X, Y) 173 8 receives it, performs the End.DT4 function and sends the IP packet 174 (X, Y) towards its VPN destination. 176 This example illustrates the benefits highlighted in the next 177 section. 179 3. Acknowledgements 181 The authors would like to acknowledge Francois Clad, Peter Psenak, 182 Ketan Talaulikar, Jakub Horn, Swadesh Agrawal, Zafar Ali, Darren 183 Dukes, Kiran Sadshiran, Junaid Israr, Lakshmanan Srikanth, Asif 184 Islam, Saleem Hafeez, Michael MacKenzie, Sushek Shekar, YuanChao Su, 185 Alexander Preusche, Alberto Donzelli, Miya Kohno, David Smith, Ianik 186 Semco, Bertrand Duvivier, Frederic Trate, Kris Michielsen, Eyal 187 Dagan, Eli Stein, Ofer Iny, Elad Naor, Aviad Behar, Joseph Chin. 189 4. Contributors 191 Jisu Bhattacharyaa 192 Cisco Systems, Inc. 193 United States of America 195 Email: jisu@cisco.com 197 Kamran Raza 198 Cisco Systems, Inc. 199 Canada 201 Email: skraza@cisco.com 203 John Bettink 204 Cisco Systems, Inc. 205 United States of America 207 Email: jbettink@cisco.com 209 Tomonobu Niwa 210 KDDI 211 Japan 213 Email: to-niwa@kddi.com 215 Luay Jalil 216 Verizon 217 United States of America 219 Email: luay.jalil@one.verizon.com 221 Zhichun Jiang 222 Tencent 223 China 224 Email: zcjiang@tencent.com 226 Ahmed Shawky 227 Saudi Telecom Company 228 Saudi Arabia 230 Email: ashawky@stc.com.sa 232 Nic Leymann 233 Deutsche Telekom 234 Germany 236 Email: N.Leymann@telekom.de 238 Dirk Steinberg 239 Lapishills Consulting Limited 240 Cyprus 242 Email: dirk@lapishills.com 244 Shawn Zandi 245 LinkedIn 246 United States of America 248 Email: szandi@linkedin.com 250 Gaurav Dawra 251 LinkedIn 252 United States of America 254 Email: gdawra@linkedin.com 256 Jim Uttaro 257 AT&T 258 United States of America 259 Email: ju1738@att.com 261 Ning So 262 Reliance 263 United States of America 265 Email: Ning.So@ril.com 267 Michael Fiumano 268 Sprint 269 United States of America 271 Email: michael.f.fiumano@sprint.com 273 Mazen Khaddam 274 Cox 275 United States of America 277 Email: Mazen.Khaddam@cox.com 279 Jichun Ma 280 China Unicom 281 China 283 Email: majc16@chinaunicom.cn 285 Satoru Matsushima 286 Softbank 287 Japan 289 Email: satoru.matsushima@g.softbank.co.jp 291 Francis Ferguson 292 CenturyLink 293 United States of America 294 Email: Francis.Ferguson@centurylink.com 296 Takuya Miyasaka 297 KDDI 298 Japan 300 Email: ta-miyasaka@kddi.com 302 Kentaro Ebisawa 303 Toyota Motor Corporation 304 Japan 306 Email: ebisawa@toyota-tokyo.tech 308 Yukito Ueno 309 NTT Communications Corporation 310 Japan 312 Email: yukito.ueno@ntt.com 314 5. References 316 [I-D.filsfils-spring-net-pgm-extension-srv6-usid] 317 Filsfils, C., Camarillo, P., Cai, D., Voyer, D., Meilik, 318 I., Patel, K., Henderickx, W., Jonnalagadda, P., and D. 319 Melman, "Network Programming extension: SRv6 uSID 320 instruction", draft-filsfils-spring-net-pgm-extension- 321 srv6-usid-03 (work in progress), February 2020. 323 [I-D.filsfils-spring-srv6-net-pgm-illustration] 324 Filsfils, C., Camarillo, P., Li, Z., Matsushima, S., 325 Decraene, B., Steinberg, D., Lebrun, D., Raszuk, R., and 326 J. Leddy, "Illustrations for SRv6 Network Programming", 327 draft-filsfils-spring-srv6-net-pgm-illustration-01 (work 328 in progress), August 2019. 330 [I-D.ietf-6man-segment-routing-header] 331 Filsfils, C., Dukes, D., Previdi, S., Leddy, J., 332 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 333 (SRH)", draft-ietf-6man-segment-routing-header-26 (work in 334 progress), October 2019. 336 [I-D.ietf-spring-srv6-network-programming] 337 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 338 Matsushima, S., and Z. Li, "SRv6 Network Programming", 339 draft-ietf-spring-srv6-network-programming-10 (work in 340 progress), February 2020. 342 Authors' Addresses 344 Clarence Filsfils (editor) 345 Cisco Systems, Inc. 346 Belgium 348 Email: cf@cisco.com 350 Pablo Camarillo Garvia (editor) 351 Cisco Systems, Inc. 352 Spain 354 Email: pcamaril@cisco.com 356 Dennis Cai 357 Alibaba 358 China 360 Email: d.cai@alibaba-inc.com 362 Daniel Voyer 363 Bell Canada 364 Canada 366 Email: daniel.voyer@bell.ca 368 Israel Meilik 369 Broadcom 370 Israel 372 Email: israel.meilik@broadcom.com 373 Keyur Patel 374 Arrcus, Inc. 375 United States of America 377 Email: keyur@arrcus.com 379 Wim Henderickx 380 Nokia 381 Belgium 383 Email: wim.henderickx@nokia.com 385 Prem Jonnalagadda 386 Barefoot Networks 387 United States of America 389 Email: prem@barefootnetworks.com 391 David Melman 392 Marvell 393 Israel 395 Email: davidme@marvell.com