Some Possible Extensions of the Current LFB Model
draft-blake-forces-attrib-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Steven L. Blake , Zsolt Haraszti | ||
| Last updated | 2004-07-13 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-blake-forces-attrib-00.txt
Abstract
The ForCES Forwarding Element Model [Model] defines a model and schema for representing Logical Functional Block (LFB) classes and their operational and capability attributes. The operational attributes of LFB instances within a Forwarding Element (FE) are manipulated by the ForCES protocol [ForCES] to configure the operation of the FE. The model assumes that any particular LFB attribute is owned and accessed exclusively by a single LFB instance. While this is a simple and clean restriction, we observe that it imposes some complications when defining LFBs. This memo addresses these complications and proposes that the restriction be re-examined.
Authors
Steven L. Blake
Zsolt Haraszti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)