ForCES Implementation Experience Draft
draft-ietf-forces-implementation-experience-00
| Document | Type |
Replaced Internet-Draft
(forces WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Evangelos Haleplidis , Odysseas Koufopavlou , Spyros Denazis | ||
| Last updated | 2012-10-11 (Latest revision 2009-10-08) | ||
| Replaced by | draft-haleplidis-forces-implementation-experience | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-haleplidis-forces-implementation-experience | |
| Consensus boilerplate | Unknown | ||
| 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
The forwarding and Control Element Separation (ForCES) protocol defines a standard communication and control mechanism through which a Control Element (CE) can control the behavior of a Forwarding Element (FE). This document captures the experience of implementing the ForCES protocol and model. It's aim is to help others by providing examples and possible strategies for implementing the ForCES protocol.
Authors
Evangelos Haleplidis
Odysseas Koufopavlou
Spyros Denazis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)