ForCES FE Functional Model Elements
draft-haraszti-forces-model-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zsolt Haraszti , Steven L. Blake | ||
| Last updated | 2003-07-28 | ||
| 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 memo identifies requirements and issues associated with the ForCES Forwarding Element Functional Model. It attempts to: o Build on the concepts introduced in [MODEL]. o Serve as a collection/list of requirements for the FE functional model o State some open issues that must be resolved before the actual formal model can be designed. o Address some of the issues raised here and in [MODEL].
Authors
Zsolt Haraszti
Steven L. Blake
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)