Multi-Layer OAM for Service Function Chains in Networks
draft-wang-sfc-multi-layer-oam-09

Document Type Active Internet-Draft (individual)
Last updated 2017-06-14
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                                         G. Mirsky
Internet-Draft                                                 ZTE Corp.
Intended status: Standards Track                                 W. Meng
Expires: December 16, 2017                               ZTE Corporation
                                                           B. Khasnabish
                                                            ZTE TX, Inc.
                                                                 C. Wang
                                                           June 14, 2017

        Multi-Layer OAM for Service Function Chains in Networks
                   draft-wang-sfc-multi-layer-oam-09

Abstract

   A multi-layer approach to the task of Operation, Administration and
   Maintenance (OAM) of Service Function Chains (SFCs) in networks is
   presented.  Based on the SFC OAM requirements, a multi-layer model is
   introduced.  A mechanism to detect and localize defects using the
   multi-layer model is also described.

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 December 16, 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

Mirsky, et al.          Expires December 16, 2017               [Page 1]
Internet-Draft           Multi-Layer OAM for SFC               June 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Multi-layer Model of SFC OAM  . . . . . . . . . . . . . . . .   3
   4.  Requirements for SFC OAM Multi-layer Model  . . . . . . . . .   4
   5.  SFC OAM multi-layer model . . . . . . . . . . . . . . . . . .   5
   6.  Theory of Operation . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  SFC TLV Type  . . . . . . . . . . . . . . . . . . . . . .   7
     8.2.  SFC OAM UDP Port  . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   [RFC7665] defines components necessary to implement Service Function
   Chain (SFC).  These include a classifier which performs
   classification of incoming packets.  A Service Function Forwarder
   (SFF) is responsible for forwarding traffic to one or more connected
   Service Functions (SFs) according to the information carried in the
   SFC encapsulation.  SFF also handles traffic coming back from the SF
   and transports the data packets to the next SFF.  And the SFF serves
   as termination element of the Service Function Path (SFP).  SF is
   responsible for specific treatment of received packets.

   Resulting from that SFC is constructed by a number of these
   components, there are different views from different levels of the
   SFC.  One is the SFC, fully abstract entity, that defines an ordered
   set of SFs that must be applied to packets selected as a result of
   classification.  But SFC doesn't define exact mapping between SFFs
   and SFs.  Thus there exists another semi-abstract entity referred as
Show full document text