ForCES LFB Instance State
draft-djjhs-forces-lfbstate-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Damascane M. Joachimpillai , Jamal Hadi Salim | ||
| Last updated | 2013-04-16 (Latest revision 2012-10-13) | ||
| 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
The ForCES LFB Topology currently defines that once an instance of an LFB class is created it becomes immediately active in the datatapath. This document makes a slight extension to add state to an instantiated LFB class allowing the CE to decide when an LFB instance becomes operational on the datapath.
Authors
Damascane M. Joachimpillai
Jamal Hadi Salim
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)