Service Function Chaining Verification
draft-lee-sfc-verification-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Seungik Lee , Myung-Ki Shin | ||
| Last updated | 2014-08-18 (Latest revision 2014-02-14) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document addresses the possible conflicts among different service function chains. These conflicts may occur when 1) a traffic flow satisfies two or more classification rules of different service function chains; and 2) a service function cannot provide enough resource for a service function chain due to load of other service function chains. These conflicts need to be detected and resolved at deploying a new service chain.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)