Interworking SFC network and Overlay network
draft-ao-sfc-overlay-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-12
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
SFC WG                                                             T. Ao
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                               G. Mirsky
Expires: September 13, 2017                                    ZTE Corp.
                                                          March 12, 2017

              Interworking SFC network and Overlay network
                        draft-ao-sfc-overlay-01

Abstract

   For SFC, it's generally transmitted over an overlay network.A Service
   Function Chain is an overlay carried over by an underlay network.This
   document defines necessary interworking stand-alone Network Virtual
   Edge and Service Forwarding Function entities to ensure proper
   handling of SFC traffic by the underlay network.

Status of This Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on September 13, 2017.

Copyright Notice

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

   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

Ao & Mirsky            Expires September 13, 2017               [Page 1]
Internet-Draft                 SFC overlay                    March 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   4.  Interworking action . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Co-located NVE-SFF  . . . . . . . . . . . . . . . . . . .   4
     4.2.  NVE-SFF split . . . . . . . . . . . . . . . . . . . . . .   4
       4.2.1.  Classifier action . . . . . . . . . . . . . . . . . .   4
       4.2.2.  SFF action  . . . . . . . . . . . . . . . . . . . . .   5
       4.2.3.  NVE action  . . . . . . . . . . . . . . . . . . . . .   5
   5.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Service Function Chaining (SFC) is a technique for prescribing
   differentiated traffic forwarding policies within the SFC domain.
   SFC is described in detail in the SFC architecture document.
   [RFC7665] .

   SFC traffic is transferred in overlay network, which is described in
   SFC architecture document [RFC7665].  In an underlay network, Network
   Virtualization Edge (NVE) maps the traffic to a tunnel according to
   the inner destination address of the traffic, then encapsulates the
   packet into outer.  In this document, we assume that the NVEs in
   overlay network have already obtained the mapping information between
   NVE and Service Functions(SFs) which is described in NVO3 network
   framework [RFC7365].

   But the destination address of SFC traffic is the final destination
   of the traffic, not the next hop of the SFC, so that NVE will not
   tunnel the traffic to the next SF, but encapsulate the SFC traffic
   with the NVE address connected to the destination station.  So it's
   important to coordinate SFC domain and corresponding underlay
   network.  Underlay network edge device NVE needs to know how to
   forward SFC traffic, that is NVE should only encapsulate the SFC
Show full document text