Architecture and application scenario for fused service function chain
draft-dai-sfc-fused-architecture-and-scenario-00

Document Type Active Internet-Draft (individual)
Authors Jinyou Dai  , Xueshun Wang  , Jun Gao 
Last updated 2020-12-28
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             J. Dai
INTERNET-DRAFT                                                   X. Wang
Intended Status: Informational                                    J. Gao
Expires:  June 28, 2021                                  Fiberhome/CICT                  
                                                        December 28, 2020

 Architecture and application scenario for fused service function chain 
            draft-dai-sfc-fused-architecture-and-scenario-00

    
Abstract

   This document discusses the architecture and application scenarios 
   of fused service function chain. Fused service function chain means  
   that two or more service function chains are fused to become a single
   service function chain from the view of data plane and control plane.
   Anyhow, some mechanism or methods need to be used when two or more   
   service function chains are fused to be a single service function     
   chain. 

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors. All rights reserved.

  
Dai, et al.              Expires June 28, 2021                 [Page 1]
INTERNET DRAFT     Architecture for fused SFC   December 28, 2020

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with 
   respect to this document. Code Components extracted from this 
   document must include Simplified BSD License text as described in 
   Section 4.e of the Trust Legal Provisions and are provided without 
   warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   2. Architecture of Fused Service Function Chain  . . . . . . . . .  4
     2.1. General Architecture for Fused Service Functional Chain . .  4
     2.2.  Interface in the Fused Service Function Chain  . . . . . .  6
     2.3.  OAM Architecture for Fused Service Function Chain  . . . .  6
   3  Application Scenarios of Fused Service Function Chain   . . . .  7
     3.1. F-SFC for Wide-area Enterprise Network  . . . . . . . . . .  7
     3.2. F-SFC in Cross-domain Scenario. . . . . . . . . . . . . . .  8
     3.3. SFC as a Service in Cloud. . . . . . . .  . . . . . . . . .  9
     3.4. F-SFC in Mobile Edge Computing. . . . . . . . . . . . . . . 10
     3.5. F-SFC in Distributed Active/Active Data Center. . . . . . . 11
     3.6. F-SFC in Network Function Virtualization Context. . . . . . 12
   4  Additional Requirements for Fused Service Function Chain. . . . 13
     4.1 Function Aspect. . . . . . . . . . . .  . . .  . . .  . . .  13
     4.2 Performance Aspect  . . . . . . . . .  . . . . . . .  . . .  13
     4.3 Control Aspect   . . . . . . .  . . .  . . . . . . . . . . . 13
     4.4 Management Aspect . . . . . . .  . . .  . . .  . . . . . . . 14
     4.5 Other Aspect  . . . . . . .  . . .  . . .  . . . . . . . . . 14
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 14
   6  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14
   7  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 14
   8  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     8.1  Normative References  . . . . . . . . . . . . . . . . . . . 15
     8.2  Informative References  . . . . . . . . . . . . . . . . . . 15
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15

1.  Introduction

   The delivery of end-to-end services often requires various service
   functions.  These include traditional network service functions such
   as firewalls and traditional IP Network Address Translators (NATs),

Dai, et al.              Expires June 28, 2021                 [Page 2]
INTERNET DRAFT     Architecture for fused SFC   December 28, 2020
Show full document text