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

Document Type Expired Internet-Draft (individual)
Last updated 2017-05-03 (latest revision 2016-10-30)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-jing-sfc-flow-release-notify-01.txt

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.

Authors

WeiDong Jing (jing.weidong1@zte.com.cn)
Cui Wang (wang.cui1@zte.com.cn)
Christophe Fontaine (christophe.fontaine@qosmos.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)