Geneve applicability for service function chaining
draft-boutros-nvo3-geneve-applicability-for-sfc-02

Document Type Active Internet-Draft (individual)
Last updated 2018-09-14
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)
INTERNET-DRAFT                                         Sami Boutros, Ed.
Intended Status: Standard Track                                   VMware
                                                            Dharma Rajan
                                                           Philip Kippen
                                                       Pierluigi Rolando
                                                                  VMware

Expires: March 18, 2019                               September 14, 2018

          Geneve applicability for service function chaining  
           draft-boutros-nvo3-geneve-applicability-for-sfc-02

Abstract

   This document describes the applicability of using Generic Network
   Virtualization Encapsulation (Geneve), to carry the service function
   path (SFP) information, and the network service header (NSH)
   encapsulation. The SFP information will be carried in Geneve option
   TLV(s).

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 and License Notice

 

Boutros                  Expires March 18, 2019                 [Page 1]
INTERNET DRAFT     NVO3 Geneve applicability for SFC  September 14, 2018

   Copyright (c) 2018 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1 Requirement for SFC in NVO3 domain . . . . . . . . . . . . .  3
     1.2 Proposed solution for SFC in NVO3 domain . . . . . . . . . .  3
   2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4. Geneve Option TLV(s)  . . . . . . . . . . . . . . . . . . . . .  5
     4.1 Geneve Service Function List (SFL) Option TLV  . . . . . . .  5
   5.. Operation  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     5.1 Operation at Ingress . . . . . . . . . . . . . . . . . . . .  7
     5.2 Operation at each NVE along the service function path  . . .  8
     5.3 Operation at Egress  . . . . . . . . . . . . . . . . . . . .  9
   6. Security Considerations . . . . . . . . . . . . . . . . . . . .  9
   7. Management Considerations . . . . . . . . . . . . . . . . . . . 10
   8. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 11
   9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 11
   10.  References  . . . . . . . . . . . . . . . . . . . . . . . . . 11
     10.1  Normative References . . . . . . . . . . . . . . . . . . . 11
     10.2  Informative References . . . . . . . . . . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12

 

Boutros                  Expires March 18, 2019                 [Page 2]
INTERNET DRAFT     NVO3 Geneve applicability for SFC  September 14, 2018

1. Introduction

   The Service Function Chaining (SFC) Architecture [rfc7665] defines a
   service function chain (SFC) as (1) the instantiation of an ordered
   set of service functions and (2) the subsequent "steering" of traffic
   through them.

   SFC defines a Service Function Path (SFP) as the exact set of service
   function forwarders (SFF)/service functions (SF)s the packet will
   visit when it actually traverses the network.

   An optimized SFP helps to build an efficient Service function chain
   (SFC) that can be used to steer traffic based on classification
   rules, and metadata information to provide services for Network
   Function Virtualization (NFV).  Metadata are typically passed between
Show full document text