<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.blake-forces-attrib'>
<front>
<title>Some Possible Extensions of the Current LFB Model</title>

<author initials='S' surname='Blake' fullname='Steven Blake'>
    <organization />
</author>

<author initials='Z' surname='Haraszti' fullname='Zsolt  Haraszti'>
    <organization />
</author>

<date month='July' day='13' year='2004' />

<abstract><t>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.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-blake-forces-attrib-00' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-blake-forces-attrib-00.txt' />
</reference>

