Flow Release Notify
draft-jing-sfc-flow-release-notify-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-30
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                                                           W. Jing
Internet-Draft                                                   C. Wang
Intended status: Standards Track                         ZTE Corporation
Expires: May 3, 2017                                         C. FONTAINE
                                                                  Qosmos
                                                        October 30, 2016

                          Flow Release Notify
                 draft-jing-sfc-flow-release-notify-01

Abstract

   Service function chain is the definition of an ordered set of service
   functions.  After instantiated, the service function path is created
   and the classified traffic is steered through the corresponding
   service function path and then forwarded to the final destination.
   SFs and SFC Proxies do not know the termination of a service flow.
   This document describes a method to notify the SFs and SFC Proxies
   the termination of a service flow.

   When one service flow goes through the SFP, there may create some
   states in some SFs or SFC Proxies.  However, when the service flow
   terminates, the SFs and SFC Proxies are unaware of that and maintain
   the states as well.This document describes a method to notify the SFs
   and SFC Proxies the termination of a service flow and release the
   resources occupied by the flow.

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 May 3, 2017.

Jing, et al.               Expires May 3, 2017                  [Page 1]
Internet-Draft             Flow Release Notify              October 2016

Copyright Notice

   Copyright (c) 2016 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Convention and Terminology  . . . . . . . . . . . . . . . . .   3
   3.  Defination of Flow Termination Message  . . . . . . . . . . .   3
     3.1.  Data Plane Approach . . . . . . . . . . . . . . . . . . .   3
     3.2.  Control Plane Approach  . . . . . . . . . . . . . . . . .   4
   4.  Controller Behavior . . . . . . . . . . . . . . . . . . . . .   5
   5.  Classifier Behavior . . . . . . . . . . . . . . . . . . . . .   5
   6.  Service Function Forwarder behavior . . . . . . . . . . . . .   6
   7.  SFC Proxy Behavior  . . . . . . . . . . . . . . . . . . . . .   6
   8.  SFC-aware Service Function Behavior . . . . . . . . . . . . .   6
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   7
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     12.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Service function chain is the definition of an ordered set of service
   functions.  After instantiated, the service function path is created
   and the classified traffic is steered through the corresponding
   service function path and then forwarded to the final destination.

   SFs and SFC Proxies allocate resources (e.g. memory) for service flow
   in order to process the packets of service flow correctly.
   Typically, in current SFC deployment, there are many SFC-unaware SFs
   which need SFC Proxies to assist them to fulfill SFC forwarding.
   When service flow goes through these SFC Proxies, there are states
Show full document text