idnits 2.17.1 draft-ietf-dmm-deployment-models-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 16, 2018) is 2171 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-14) exists of draft-ietf-dmm-fpc-cpdp-10 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DMM WG S. Gundavelli 3 Internet-Draft Cisco 4 Intended status: Informational S. Jeon 5 Expires: November 17, 2018 Sungkyunkwan University 6 May 16, 2018 8 DMM Deployment Models and Architectural Considerations 9 draft-ietf-dmm-deployment-models-04.txt 11 Abstract 13 This document identifies the deployment models for Distributed 14 Mobility Management architecture. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on November 17, 2018. 33 Copyright Notice 35 Copyright (c) 2018 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 52 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 53 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. DMM Architectural Overview . . . . . . . . . . . . . . . . . 4 55 3.1. DMM Service Primitives . . . . . . . . . . . . . . . . . 4 56 3.2. DMM Functions and Interfaces . . . . . . . . . . . . . . 5 57 3.2.1. Home Control-Plane Anchor (Home-CPA): . . . . . . . . 5 58 3.2.2. Home Data-Plane Anchor (Home-DPA): . . . . . . . . . 6 59 3.2.3. Access Control Plane Node (Access-CPN) . . . . . . . 6 60 3.2.4. Access Data Plane Node (Access-DPN) . . . . . . . . . 6 61 3.2.5. DMM Functions Mapping to Other Architectures . . . . 6 62 4. Deployment Models . . . . . . . . . . . . . . . . . . . . . . 8 63 4.1. Model-1: Split Home Anchor Mode . . . . . . . . . . . . . 8 64 4.2. Model-2: Separated Control and User Plane Mode . . . . . 9 65 4.3. Model-3: Centralized Control Plane Mode . . . . . . . . . 10 66 4.4. Model-4: Data Plane Abstraction Mode . . . . . . . . . . 10 67 4.5. Model-5: On-Demand Control Plane Orchestration Mode . . . 11 68 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 69 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 70 7. Work Team . . . . . . . . . . . . . . . . . . . . . . . . . . 13 71 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 72 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 73 9.1. Normative References . . . . . . . . . . . . . . . . . . 14 74 9.2. Informative References . . . . . . . . . . . . . . . . . 14 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 77 1. Overview 79 One of the key aspects of the Distributed Mobility Management (DMM) 80 architecture is the separation of control plane (CP) and data plane 81 (DP) functions of a network element. While data plane elements 82 continue to reside on customized networking hardware, the control 83 plane resides as a software element in the cloud. This is usually 84 referred to as CP-DP separation and is the basis for the IETF's DMM 85 Architecture. This approach of centralized control plane and 86 distributed data plane allows elastic scaling of control plane and 87 efficient use of common data plane that is agnostic to access 88 architectures. 90 This document identifies the functions in the DMM architecture and 91 the supported deployment models. 93 2. Conventions and Terminology 95 2.1. Conventions 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in RFC 2119 [RFC2119]. 101 2.2. Terminology 103 All the mobility related terms are to interpreted as defined in 104 [RFC6275], [RFC5213], [RFC5844], [RFC7333], [RFC7665], [RFC7429], 105 [RFC8300] and [I-D.ietf-dmm-fpc-cpdp]. Additionally, this document 106 uses the following terms: 108 Home Control-Plane Anchor (Home-CPA or H-CPA) 110 The Home-CPA function hosts the mobile node (MN)'s mobility 111 session. There can be more than one mobility session for a mobile 112 node and those sessions may be anchored on the same or different 113 Home-CPA's. The home-CPA will interface with the home-DPA for 114 managing the forwarding state. 116 Home Data Plane Anchor (Home-DPA or H-DPA) 118 The Home-DPA is the topological anchor for the MN's IP address/ 119 prefix(es). The Home-DPA is chosen by the Home-CPA on a session- 120 basis. The Home-DPA is in the forwarding path for all the mobile 121 node's IP traffic. 123 Access Control Plane Node (Access-CPN or A-CPN) 125 The Access-CPN is responsible for interfacing with the mobile 126 node's Home-CPA and with the Access-DPN. The Access-CPN has a 127 protocol interface to the Home-CPA. 129 Access Data Plane Node (Access-DPN or A-DPN) 131 The Access-DPN function is hosted on the first-hop router where 132 the mobile node is attached. This function is not hosted on a 133 layer-2 bridging device such as a eNode(B) or Access Point. 135 Routing Controller (RC) 137 The Routing Controller is a centralized control entity, which is 138 able to instruct the forwarding behavior for mobility management 139 in Home-DPA and Access-DPN. 141 Mobility Controller (MC) 143 The Mobility Controller is a function entity, which is able to 144 manage the orchestration of Home-CPA and Access-CPN functions. 146 3. DMM Architectural Overview 148 Following are the key goals of the Distributed Mobility Management 149 architecture. 151 1. Separation of control and data Plane 153 2. Aggregation of control plane for elastic scaling 155 3. Distribution of the data plane for efficient network usage 157 4. Elimination of mobility state from the data plane 159 5. Dynamic selection of control and data plane nodes 161 6. Enabling the mobile node with network properties 163 7. Relocation of anchor functions for efficient network usage 165 3.1. DMM Service Primitives 167 The functions in the DMM architecture support a set of service 168 primitives. Each of these service primitives identifies a specific 169 service capability with the exact service definition. The functions 170 in the DMM architecture are required to support a specific set of 171 service primitives that are mandatory for that service function. Not 172 all service primitives are applicable to all DMM functions. The 173 below table as shown in Fig. 1 identifies the service primitives that 174 each of the DMM function SHOULD support. The marking "X" indicates 175 the service primitive on that row needs to be supported by the 176 identified DMM function on the corresponding column; for example, the 177 IP address management MUST be supported by Home-CPA function. The 178 NSH Classifier denotes the SFC entity that performs the 179 classification of a service flow, defined in [RFC7665]. 181 +=================+=======+=======+=======+=======+=======+=======+ 182 | Service | H-CPA | H-DPA | A-CPN | A-DPN | MC | RC | 183 | Primitive | | | | | | | 184 +=================+=======+=======+=======+=======+=======+=======+ 185 | IP Management | X | | | | X | | 186 +-----------------+-------+-------+-------+-------+-------+-------+ 187 | IP Anchoring | | X | | | | | 188 +-----------------+-------+-------+-------+-------+-------+-------+ 189 | MN Detection | | | X | X | | | 190 +-----------------+-------+-------+-------+-------+-------+-------+ 191 | Routing | | X | | X | | | 192 +-----------------+-------+-------+-------+-------+-------+-------+ 193 | Tunneling | | X | | X | | | 194 +-----------------+-------+-------+-------+-------+-------+-------+ 195 | QoS Enforcement | | X | | X | | | 196 +-----------------+-------+-------+-------+-------+-------+-------+ 197 | FPC Client | X | | X | | X | | 198 +-----------------+-------+-------+-------+-------+-------+-------+ 199 | FPC Agent | | X | | X | | X | 200 +-----------------+-------+-------+-------+-------+-------+-------+ 201 | NSH Classifier | | X | | X | | | 202 +-----------------+-------+-------+-------+-------+-------+-------+ 204 Figure 1: Role or capability of DMM functions 206 3.2. DMM Functions and Interfaces 208 3.2.1. Home Control-Plane Anchor (Home-CPA): 210 The Home-CPA function hosts the mobile node's mobility session. 211 There can be more than one mobility session for a mobile node and 212 those sessions may be anchored on the same or different Home-CPA's. 213 The home-CPA will interface with the home-dpa for managing the 214 forwarding state. 216 There can be more than one Home-CPA serving the same mobile node at a 217 given point of time, each hosting a different control plane session. 219 The Home-CPA is responsible for life cycle management of the session, 220 interfacing with the policy infrastructure, policy control and 221 interfacing with the Home-DPA functions. 223 The Home-CPA function typically stays on the same node. In some 224 special use-cases (Ex: Geo-Redundancy), the session may be migrated 225 to a different node and with the new node assuming the Home-CPA role 226 for that session. 228 3.2.2. Home Data-Plane Anchor (Home-DPA): 230 The Home-DPA is the topological anchor for the mobile node's IP 231 address/prefix(es). The Home-DPA is chosen by the Home-CPA/MC on a 232 session-basis. The Home-DPA is in the forwarding path for all the 233 mobile node's IP traffic. 235 As the mobile node roams in the mobile network, the mobile node's 236 access-DPN may change, however, the Home-DPA does not change, unless 237 the session is migrated to a new node. 239 The Home-DPA interfaces with the Home-CPA/MC for all IP forwarding 240 and QoS rules enforcement. 242 The Home-DPA and the Access-DPN functions may be collocated on the 243 same node. 245 3.2.3. Access Control Plane Node (Access-CPN) 247 The Access-CPN is responsible for interfacing with the mobile node's 248 Home-CPA and with the Access-DPN. The Access-CPN has a protocol 249 interface to the Home-CPA. 251 The Access-CPN is responsible for the mobile node's Home-CPA 252 selection based on: Mobile Node's Attach Preferences, Access and 253 Subscription Policy, Topological Proximity and Other Considerations. 255 The Access-CPN function is responsible for MN's service 256 authorization. It will interface with the access network 257 authorization functions. 259 3.2.4. Access Data Plane Node (Access-DPN) 261 The Access-DPN function is hosted on the first-hop router where the 262 mobile node is attached. This function is not hosted on a layer-2 263 bridging device such as a eNode(B) or Access Point. 265 The Access-DPA will have a protocol interface to the Access-CPA. 267 The Access-DPN and the Home-DPA functions may be collocated on the 268 same node. 270 3.2.5. DMM Functions Mapping to Other Architectures 272 Following table identifies the potential mapping of DMM functions to 273 protocol functions in other system architectures. 275 +=======+=========+========+=========+=============+==========+=======+ 276 | Func. | PMIPv6 | MIPv6 | IPsec | 3GPP-SAE | BBF | 5GC | 277 +=======+=========+========+=========+=============+==========+=======+ 278 | H-CPA | LMA-CPA | HA-CPA | IKE-CPA | PGW-CPA/MME | BNG-CPA |AMF/SMF| 279 +-------+---------+--------+---------+-------------+----------+-------+ 280 | H-DPA | LMA-DPA | HA-DPA | IKE-DPA | PGW-DPA | BNG-DPA | UPF | 281 +-------+---------+--------+---------+-------------+----------+-------+ 282 | A-CPN | MAG-CPN | - | - | SGW-CPN | RG-CPN | SMF | 283 +-------+---------+--------+---------+-------------+----------+-------+ 284 | A-DPN | MAG-DPN | - | - | SGW-DPN | RG-DPN | UPF | 285 +-------+---------+--------+---------+-------------+----------+-------+ 287 Figure 2: Mapping of DMM functions in other system architectures 289 Mapping from the DMM functions to network components in PMIPv6, 290 MIPv6, IPsec, Broadband Forum (BBF) can be given straight-forward. 291 In the 3GPP System Architecture Evolution (SAE), H-CPA functionality 292 is charged by PGW-CPA and Mobility Management Entity (MME), as MME is 293 the key control-plane node involving in such as location management, 294 handoff management, selection of SGW/PGW as well as authorization of 295 UEs. But PGW-CPA is in charge of tunnel control based on UE's 296 subscription and policy between SGW and PGW. The rest of the 3GPP 297 SAE network components are as given in Fig. 2. 299 The 3GPP Release 15 introduces the Service-Based Architecture (SBA) 300 for 5G networks. The 3GPP 5G architecture can be represented by 301 reference point or service-based interfaces [_3GPP.23.501]. Allowing 302 the service-based interface provides greater flexibility for updates 303 and extensions of the 5G control plane system by operator's need or 304 request. The architecture introduces various kinds of network 305 functions granularized in the CP/DP separation concept. In Fig. 2, 306 Access and Mobility Management Function (AMF), Session Management 307 Function (SMF), and User Plane Function (UPF) are picked up among all 308 the network functions introduced in the 5G SBA for mapping to the DMM 309 functions. 311 AMF and SMF take major roles for mobility management in control 312 plane. AMF manages access control and mobility and includes network 313 slice selection functionality. SMF manages sessions based on UE's 314 subscription and network policy and is in charge of IP address 315 allocation management. UPF is the data plane node, which works for 316 data packet handling based on forwarding policy regulated by control 317 plane nodes such as AMF and SMF, etc. 319 4. Deployment Models 321 This section identifies the key deployment models for the DMM 322 architecture. 324 4.1. Model-1: Split Home Anchor Mode 326 In this model, the control and the data plane functions of the home 327 anchor are separated and deployed on different nodes. The control 328 plane function of the Home anchor is handled by the Home-CPA and 329 where as the data plane function is handled by the Home-DPA. In this 330 model, the access node operates in the legacy mode with the 331 integrated control and user plane functions. 333 The FPC interface defined in [I-D.ietf-dmm-fpc-cpdp] allows the 334 control plane functions to interact with the data plane for the 335 subscriber's forwarding state management. 337 +============+ 338 | Policy | 339 . . . . . . .| Function |. . . . . . . 340 . +============+ . 341 . . 342 . . 343 +============+ {PMIPv6/GTP} +============+ 344 | |- - - - - - - - - - - - -| Home-CPA | 345 | | +============+ 346 | | . 347 | | . FPC 348 | Access Node| . 349 | | . 350 | (CPN + DPN)| . 351 | | +============+ 352 | Legacy |. . . . . . . . . . . . .| Home-DPA | 353 +============+ UP {Tunnel/Route} +============+ 354 . 355 . 356 +--+ 357 |MN| 358 +--+ 360 Figure 3: Split Home Anchor Mode 362 4.2. Model-2: Separated Control and User Plane Mode 364 In this model, the control and the data plane functions on both the 365 home anchor and the access node are seperated and deployed on 366 different nodes. The control plane function of the Home anchor is 367 handled by the Home-CPA whereas the data plane function is handled by 368 the Home-DPA. The control plane function of the access node is 369 handled by the Access-CPN and where as the data plane function is 370 handled by the Access-DPN. 372 The FPC interface defined in [I-D.ietf-dmm-fpc-cpdp] allows the 373 control plane functions of the home and access nodes to interact with 374 the respective data plane functions for the subscriber's forwarding 375 state management. 377 +============+ 378 | Policy | 379 . . . . . . .| Function |. . . . . . . 380 . +============+ . 381 . . 382 . . 383 . . 384 . . 385 +============+ {PMIPv6/GTP} +============+ 386 | Access-CPN |- - - - - - - - - - - - | Home-CPA | 387 +============+ +============+ 388 . . 389 . FPC . FPC 390 . . 391 . . 392 . . 393 +============+ +============+ 394 | Access-DPN |. . . . . . . . . . . | Home-DPA | 395 +============+ UP {Tunnel/Route} +============+ 396 . 397 . 398 +--+ 399 |MN| 400 +--+ 402 Figure 4: Seperated Control and User Plane Mode 404 4.3. Model-3: Centralized Control Plane Mode 406 In this model, the control-plane functions of the home and the access 407 nodes are collapsed. This is a flat architecture with no signaling 408 protocol between the access node and home anchors. The interface 409 between the Home-CPA and the Access-DPN is internal to the system. 411 The FPC interface defined in [I-D.ietf-dmm-fpc-cpdp] allows the 412 mobility controller to interact with the respective data plane 413 functions for the subscriber's forwarding state management. 415 +=======================+ +============+ 416 | Home-CPA + Access-CPN | | Policy | 417 | |-----| Function | 418 +=======================+ +============+ 419 . 420 . . 421 . . 422 FPC . . FPC 423 . . 424 . . 425 +============+ +============+ 426 | Access-DPN |. . . . . . . . . .| Home-DPA | 427 +============+ UP {Tunnel/Route} +============+ 428 . 429 . 430 +--+ 431 |MN| 432 +--+ 434 Figure 5: Centralized Control Plane Mode 436 4.4. Model-4: Data Plane Abstraction Mode 438 In this model, the data plane network is completely abstracted from 439 the control plane. There is a new network element, Routing 440 Controller which abstracts the entire data plane network and offers 441 data plane services to the control plane functions. The control 442 plane functions, Home-CPA and the Access-CPN interface with the 443 Routing Controller for the forwarding state management. 445 The FPC interface defined in [I-D.ietf-dmm-fpc-cpdp] allows the Home- 446 CPA and Access-CPN functions to interface with the Routing Controller 447 for subscriber's forwarding state management. 449 +============+ 450 | Policy | 451 . . . . . . .| Function |. . . . . . . 452 . +============+ . 453 . . 454 . . 455 . . 456 +============+ {PMIPv6/GTP} +============+ 457 | Access-CPN |- - - - - - - - - - - - | Home-CPA | 458 +============+ +============+ 459 . . 460 . . 461 . . 462 . +============+ . 463 . . . . . . | Routing | . . . . . . . 464 | Controller | 465 +============+ 466 . 467 . . 468 . . BGP/Others 469 . . 470 . . 471 . . 472 +============+ +============+ 473 | Access-DPN |. . . . . . . . . .| Home-DPA | 474 +============+ UP {Tunnel/Route} +============+ 475 . 476 . 477 +--+ 478 |MN| 479 +--+ 481 Figure 6: Data Plane Abstraction Mode 483 4.5. Model-5: On-Demand Control Plane Orchestration Mode 485 In this model, there is a new function Mobility Controller which 486 manages the orchestration of Access-CPN and Home-CPA functions. The 487 Mobility Controller allocates the Home-CPA and Access-DPN 488 + - - - - - - - - - - - - - - - - - - - - - - - - - - -+ 489 | +----------+ +----------+ +----------+ | 490 |Access-CPN| |Access-CPN| |Access-CPN| 491 | +----------+ +----------+ +----------+ | 493 | +----------+ +----------+ +----------+ | 494 | Home-CPA | | Home-CPA | | Home-CPA | 495 | +----------+ +----------+ +----------+ | 496 + - - - - - - - - - - - - - - - - - - - - - - - - - - -+ 497 . . 498 . . 499 . . 500 . +============+ +============+ 501 . | Mobility | | Policy | 502 . | Controller |-----| Function | 503 . +============+ +============+ 504 . 505 . 506 . 507 . +============+ 508 . . . . . .| Routing | 509 | Controller | 510 +============+ 511 . 512 . 513 . 514 + - - - - - - - - - - - - - - - - - - - - - - - - - - -+ 515 | +----------+ +----------+ +----------+ | 516 |Access-DPN| |Access-DPN| |Access-DPN| 517 | +----------+ +----------+ +----------+ | 519 | +----------+ +----------+ +----------+ | 520 | Home-DPA | | Home-DPA | | Home-DPA | 521 | +----------+ +----------+ +----------+ | 522 + - - - - - - - - - - - - - - - - - - - - - - - - - - -+ 524 Figure 7: On-Demand CP Orchestration Mode 526 5. IANA Considerations 528 This document does not require any IANA actions. 530 6. Security Considerations 532 The control-plane messages exchanged between a Home-CPA and the Home- 533 DPA must be protected using end-to-end security associations with 534 data-integrity and data-origination capabilities. 536 IPsec ESP in transport mode with mandatory integrity protection 537 should be used for protecting the signaling messages. IKEv2 should 538 be used to set up security associations between the Home-CPA and 539 Home-DPA. 541 There are no additional security considerations other than what is 542 presented in the document. 544 7. Work Team 546 This document reflects contributions from the following work team 547 members: 549 Younghan Kim 551 younghak@ssu.ac.kr 553 Vic Liu 555 liuzhiheng@chinamobile.com 557 Danny S Moses 559 danny.moses@intel.com 561 Marco Liebsch 563 liebsch@neclab.eu 565 Carlos Jesus Bernardos Cano 567 cjbc@it.uc3m.es 569 8. Acknowledgements 571 This document is a result of DMM WT#4 team discussions and ideas 572 taken from several DMM WG presentations and documents including, 573 draft-sijeon-dmm-deployment-models, draft-liu-dmm-deployment-scenario 574 and others. The work teams would like to thank the authors of these 575 documents and additionally the discussions in DMM Working group that 576 helped shape this document. 578 9. References 580 9.1. Normative References 582 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 583 Requirement Levels", BCP 14, RFC 2119, 584 DOI 10.17487/RFC2119, March 1997, 585 . 587 9.2. Informative References 589 [_3GPP.23.501] 590 3GPP, "System Architecture for the 5G System", 3GPP 591 TS 23.501 15.0.0, December 2018, 592 . 594 [I-D.ietf-dmm-fpc-cpdp] 595 Matsushima, S., Bertz, L., Liebsch, M., Gundavelli, S., 596 Moses, D., and C. Perkins, "Protocol for Forwarding Policy 597 Configuration (FPC) in DMM", draft-ietf-dmm-fpc-cpdp-10 598 (work in progress), March 2018. 600 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 601 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 602 RFC 5213, DOI 10.17487/RFC5213, August 2008, 603 . 605 [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy 606 Mobile IPv6", RFC 5844, DOI 10.17487/RFC5844, May 2010, 607 . 609 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 610 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 611 2011, . 613 [RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J. 614 Korhonen, "Requirements for Distributed Mobility 615 Management", RFC 7333, DOI 10.17487/RFC7333, August 2014, 616 . 618 [RFC7429] Liu, D., Ed., Zuniga, JC., Ed., Seite, P., Chan, H., and 619 CJ. Bernardos, "Distributed Mobility Management: Current 620 Practices and Gap Analysis", RFC 7429, 621 DOI 10.17487/RFC7429, January 2015, 622 . 624 [RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function 625 Chaining (SFC) Architecture", RFC 7665, 626 DOI 10.17487/RFC7665, October 2015, 627 . 629 [RFC8300] Quinn, P., Ed., Elzur, U., Ed., and C. Pignataro, Ed., 630 "Network Service Header (NSH)", RFC 8300, 631 DOI 10.17487/RFC8300, January 2018, 632 . 634 Authors' Addresses 636 Sri Gundavelli 637 Cisco 638 170 West Tasman Drive 639 San Jose, CA 95134 640 USA 642 Email: sgundave@cisco.com 644 Seil Jeon 645 Sungkyunkwan University 646 2066 Seobu-ro, Jangan-gu 647 Suwon, Gyeonggi-do 648 Korea 650 Email: seiljeon@skku.edu