draft-ietf-forces-model-extension-01.txt   draft-ietf-forces-model-extension-02.txt 
Internet Engineering Task Force E. Haleplidis Internet Engineering Task Force E. Haleplidis
Internet-Draft University of Patras Internet-Draft University of Patras
Intended status: Standards Track November 16, 2013 Intended status: Standards Track May 20, 2014
Expires: May 20, 2014 Expires: November 21, 2014
ForCES Model Extension ForCES Model Extension
draft-ietf-forces-model-extension-01 draft-ietf-forces-model-extension-02
Abstract Abstract
Forwarding and Control Element Separation (ForCES) defines an Forwarding and Control Element Separation (ForCES) defines an
architectural framework and associated protocols to standardize architectural framework and associated protocols to standardize
information exchange between the control plane and the forwarding information exchange between the control plane and the forwarding
plane in a ForCES Network Element (ForCES NE). RFC5812 has defined plane in a ForCES Network Element (ForCES NE). RFC5812 has defined
the ForCES Model provides a formal way to represent the capabilities, the ForCES Model provides a formal way to represent the capabilities,
state, and configuration of forwarding elements within the context of state, and configuration of forwarding elements within the context of
the ForCES protocol, so that control elements (CEs) can control the the ForCES protocol, so that control elements (CEs) can control the
FEs accordingly. More specifically, the model describes the logical FEs accordingly. More specifically, the model describes the logical
functions that are present in an FE, what capabilities these functions that are present in an FE, what capabilities these
functions support, and how these functions are or can be functions support, and how these functions are or can be
interconnected. interconnected.
RFC5812 has been around for two years and experience in its use has RFC5812 has been around for two years and experience in its use has
shown room for small extensions without a need to alter the protocol shown room for small extensions without a need to alter the protocol
while retaining backward compatibility with older xml libraries. while retaining backward compatibility with older xml libraries.
This document extends the model to allow complex datatypes for This document extends the model to allow complex datatypes for
metadata, optional default values for datatypes and optional access metadata, optional default values for datatypes, optional access
types for structures. The document also introduces two new features types for structures and fixes an issue with LFB inheritance. The
a new event condition BecomesEqualTo and LFB properties. document also introduces two new features a new event condition
BecomesEqualTo and LFB properties.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 20, 2014. This Internet-Draft will expire on November 21, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Terminology and Conventions . . . . . . . . . . . . . . . . . 2 1. Terminology and Conventions . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
1.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 2 1.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
3. ForCES Model Extension proposal . . . . . . . . . . . . . . . 4 3. ForCES Model Extension proposal . . . . . . . . . . . . . . . 4
3.1. Complex datatypes for Metadata . . . . . . . . . . . . . 4 3.1. Complex datatypes for Metadata . . . . . . . . . . . . . 4
3.2. Optional Default Value for Datatypes . . . . . . . . . . 6 3.2. Optional Default Value for Datatypes . . . . . . . . . . 6
3.3. Optional Access Type for Structs . . . . . . . . . . . . 7 3.3. Optional Access Type for Structs . . . . . . . . . . . . 8
3.4. New Event Condition: BecomesEqualTo . . . . . . . . . . . 8 3.4. New Event Condition: BecomesEqualTo . . . . . . . . . . . 10
3.5. LFB Properties . . . . . . . . . . . . . . . . . . . . . 9 3.5. LFB Properties . . . . . . . . . . . . . . . . . . . . . 11
3.6. Enhancing XML Validation . . . . . . . . . . . . . . . . 11 3.6. LFB class inheritance . . . . . . . . . . . . . . . . . . 12
4. XML Extension Schema for LFB Class Library Documents . . . . 12 3.7. Enhancing XML Validation . . . . . . . . . . . . . . . . 13
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 4. XML Extension Schema for LFB Class Library Documents . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27
7. Security Considerations . . . . . . . . . . . . . . . . . . . 25 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 7. Security Considerations . . . . . . . . . . . . . . . . . . . 27
8.1. Normative References . . . . . . . . . . . . . . . . . . 25 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 27
8.2. Informative References . . . . . . . . . . . . . . . . . 25 8.1. Normative References . . . . . . . . . . . . . . . . . . 27
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 25 8.2. Informative References . . . . . . . . . . . . . . . . . 27
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 27
1. Terminology and Conventions 1. Terminology and Conventions
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
1.2. Definitions 1.2. Definitions
skipping to change at page 4, line 30 skipping to change at page 4, line 34
2. Introduction 2. Introduction
The ForCES Model [RFC5812] presents a formal way to define FEs The ForCES Model [RFC5812] presents a formal way to define FEs
Logical Function Blocks (LFBs) using XML. [RFC5812] has been Logical Function Blocks (LFBs) using XML. [RFC5812] has been
published a more than two years and current experience in its use has published a more than two years and current experience in its use has
demonstrated need for adding new and changing existing modeling demonstrated need for adding new and changing existing modeling
concepts. concepts.
Specifically this document extends the ForCES Model to allow complex Specifically this document extends the ForCES Model to allow complex
datatypes for metadata, optional default values for datatypes and datatypes for metadata, optional default values for datatypes,
optional access types for structures. Additionally the document optional access types for structures and fixes an issue with the LFB
introduces two new features a new event condition BecomesEqualTo and inheritance. Additionally the document introduces two new features a
LFB properties. new event condition BecomesEqualTo and LFB properties.
These extensions are an addendum to the ForCES model [RFC5812] and do These extensions are an addendum to the ForCES model [RFC5812] and do
not require any changes on the ForCES protocol [RFC5810] as they are not require any changes on the ForCES protocol [RFC5810] as they are
simply changes of the schema definition. Additionally backward simply changes of the schema definition. Additionally backward
compatibility is ensured as xml libraries produced with the earlier compatibility is ensured as xml libraries produced with the earlier
schema are still valid with the new one. schema are still valid with the new one.
3. ForCES Model Extension proposal 3. ForCES Model Extension proposal
3.1. Complex datatypes for Metadata 3.1. Complex datatypes for Metadata
skipping to change at page 5, line 22 skipping to change at page 5, line 22
2. When a packet is received from a controller it may be accompanied 2. When a packet is received from a controller it may be accompanied
by a list of actions to be performed on it prior to be sent on by a list of actions to be performed on it prior to be sent on
the flow table pipeline which is also an array. the flow table pipeline which is also an array.
With this extension (Figure 2), complex data types are also allowed, With this extension (Figure 2), complex data types are also allowed,
specifically structs and arrays as metadata. The key declarations specifically structs and arrays as metadata. The key declarations
are required to check for validity of content keys in arrays and are required to check for validity of content keys in arrays and
componentIDs in structs. componentIDs in structs.
<xsd:complexType name="metadataDefsType"> <xsd:complexType name="metadataDefsType">
<xsd:sequence> <xsd:sequence>
<xsd:element name="metadataDef" maxOccurs="unbounded"> <xsd:element name="metadataDef" maxOccurs="unbounded">
<xsd:complexType> <xsd:complexType>
<xsd:sequence> <xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/> <xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/> <xsd:element ref="synopsis"/>
<xsd:element name="metadataID" type="xsd:integer"/> <xsd:element name="metadataID" type="xsd:integer"/>
<xsd:element ref="description" minOccurs="0"/> <xsd:element ref="description" minOccurs="0"/>
<xsd:choice> <xsd:choice>
<xsd:element name="typeRef" type="typeRefNMTOKEN"/> <xsd:element name="typeRef" type="typeRefNMTOKEN"/>
<xsd:element name="atomic" type="atomicType"/> <xsd:element name="atomic" type="atomicType"/>
</xsd:choice> </xsd:choice>
</xsd:sequence> </xsd:sequence>
</xsd:complexType> </xsd:complexType>
</xsd:element> </xsd:element>
</xsd:sequence> </xsd:sequence>
</xsd:complexType> </xsd:complexType>
Figure 1: Initial MetadataDefType Definition in the schema Figure 1: Initial MetadataDefType Definition in the schema
<xsd:complexType name="metadataDefsType">
<xsd:complexType name="metadataDefsType"> <xsd:sequence>
<xsd:sequence> <xsd:element name="metadataDef" maxOccurs="unbounded">
<xsd:element name="metadataDef" maxOccurs="unbounded"> <xsd:complexType>
<xsd:complexType> <xsd:sequence>
<xsd:sequence> <xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element name="name" type="xsd:NMTOKEN"/> <xsd:element ref="synopsis"/>
<xsd:element ref="synopsis"/> <xsd:element name="metadataID" type="xsd:integer"/>
<xsd:element name="metadataID" type="xsd:integer"/> <xsd:element ref="description" minOccurs="0"/>
<xsd:element ref="description" minOccurs="0"/> <xsd:choice>
<xsd:choice> <xsd:element name="typeRef" type="typeRefNMTOKEN"/>
<xsd:element name="typeRef" type="typeRefNMTOKEN"/> <xsd:element name="atomic" type="atomicType"/>
<xsd:element name="atomic" type="atomicType"/> <xsd:element name="array" type="arrayType">
<xsd:element name="array" type="arrayType"> <xsd:key name="contentKeyID1">
<xsd:key name="contentKeyID1"> <xsd:selector xpath="lfb:contentKey"/>
<xsd:selector xpath="lfb:contentKey"/> <xsd:field xpath="@contentKeyID"/>
<xsd:field xpath="@contentKeyID"/> </xsd:key>
</xsd:key> </xsd:element>
</xsd:element> <xsd:element name="struct" type="structType">
<xsd:element name="struct" type="structType"> <xsd:key name="structComponentID1">
<xsd:key name="structComponentID1"> <xsd:selector xpath="lfb:component"/>
<xsd:selector xpath="lfb:component"/> <xsd:field xpath="@componentID"/>
<xsd:field xpath="@componentID"/> </xsd:key>
</xsd:key> </xsd:element>
</xsd:element> </xsd:choice>
</xsd:choice> </xsd:sequence>
</xsd:sequence> </xsd:complexType>
</xsd:complexType> </xsd:element>
</xsd:element> </xsd:sequence>
</xsd:sequence> </xsd:complexType>
</xsd:complexType>
Figure 2: New MetadataDefType Definition for the schema Figure 2: New MetadataDefType Definition for the schema
3.2. Optional Default Value for Datatypes 3.2. Optional Default Value for Datatypes
In the original schema, default values can only be defined for In the original schema, default values can only be defined for
datatypes defined inside LFB components and not inside structures or datatypes defined inside LFB components and not inside structures or
arrays. Therefore default values of datatypes that are constantly arrays. Therefore default values of datatypes that are constantly
being reused, e.g. counters with default value of 0, have to be being reused, e.g. counters with default value of 0, have to be
constantly respecified. Additionally, datatypes inside complex constantly respecified. Additionally, datatypes inside complex
skipping to change at page 6, line 46 skipping to change at page 7, line 9
This extension allows optionally to add default values to atomic and This extension allows optionally to add default values to atomic and
typeref types, whether they are as simple or complex datatypes. A typeref types, whether they are as simple or complex datatypes. A
simple use case would be to have a struct component where one of the simple use case would be to have a struct component where one of the
components is a counter which the default value would be zero. components is a counter which the default value would be zero.
This extension alters the definition of the typeDeclarationGroup in This extension alters the definition of the typeDeclarationGroup in
the xml schema from Figure 3 to Figure 4 to allow default values to the xml schema from Figure 3 to Figure 4 to allow default values to
TypeRef. TypeRef.
<xsd:element name="typeRef" type="typeRefNMTOKEN"/> <xsd:element name="typeRef" type="typeRefNMTOKEN"/>
Figure 3: Initial Excerpt of typeDeclarationGroup Defintion in the Figure 3: Initial Excerpt of typeDeclarationGroup Defintion in the
schema schema
<xsd:sequence> <xsd:sequence>
<xsd:element name="typeRef" type="typeRefNMTOKEN"/> <xsd:element name="typeRef" type="typeRefNMTOKEN"/>
<xsd:element name="DefaultValue" type="xsd:token" <xsd:element name="DefaultValue" type="xsd:token"
minOccurs="0"/> minOccurs="0"/>
</xsd:sequence> </xsd:sequence>
Figure 4: New Excerpt of typeDeclarationGroup Definition in the Figure 4: New Excerpt of typeDeclarationGroup Definition in the
schema schema
Additionally it appends to the declaration of the AtomicType this xml Additionally it appends to the declaration of the AtomicType this xml
(Figure 5) to allow default values to Atomic datatypes. (Figure 5) to allow default values to Atomic datatypes.
<xsd:element name="defaultValue" type="xsd:token" minOccurs="0"/> <xsd:element name="defaultValue" type="xsd:token" minOccurs="0"/>
Figure 5: Appending xml in of AtomicType Definition in the schema Figure 5: Appending xml in of AtomicType Definition in the schema
<dataTypeDef>
<name>Counter Values</name>
<synopsis>Example default values in struct</synopsis>
<struct>
<component componentID="1">
<name>GoodPacketCoutner</name>
<synopsis>A counter for good packets</synopsis>
<typeRef>uint32</typeRef>
<DefaultValue>0</DefaultValue>
</component>
<component componentID="2">
<name>BadPacketCoutner</name>
<synopsis>A counter for bad packets</synopsis>
<typeRef>uint32</typeRef>
<DefaultValue>0</DefaultValue>
</component>
</struct>
</dataTypeDef>
Figure 6: Example of optional default values
3.3. Optional Access Type for Structs 3.3. Optional Access Type for Structs
In the original schema, the access type can be only be defined on In the original schema, the access type can be only be defined on
components of LFB and not on components in structs or arrays. components of LFB and not on components in structs or arrays.
However when it's a struct datatype it is not possible to fine-tune However when it's a struct datatype it is not possible to fine-tune
access type per component in the struct. A simple use case would be access type per component in the struct. A simple use case would be
to have a read-write struct component where one of the components is to have a read-write struct component where one of the components is
a counter where the access-type could be read-reset or read-only, a counter where the access-type could be read-reset or read-only,
e.g. a read-reset or a read-only counter inside a struct. e.g. a read-reset or a read-only counter inside a struct.
skipping to change at page 7, line 42 skipping to change at page 8, line 26
struct component either in the datatype definitions or in the LFB struct component either in the datatype definitions or in the LFB
component definitions. component definitions.
When the optional access type for a struct component is defined it When the optional access type for a struct component is defined it
MUST override the access type of the struct. If by accident an MUST override the access type of the struct. If by accident an
access type for a component in a capability is defined, the access access type for a component in a capability is defined, the access
type MUST NOT be taken into account and MUST always be considered as type MUST NOT be taken into account and MUST always be considered as
read-only. read-only.
This extension alters the definition of the struct in the xml schema This extension alters the definition of the struct in the xml schema
from Figure 6 to Figure 7. from Figure 7 to Figure 8.
<xsd:complexType name="structType"> <xsd:complexType name="structType">
<xsd:sequence> <xsd:sequence>
<xsd:element name="derivedFrom" type="typeRefNMTOKEN" <xsd:element name="derivedFrom" type="typeRefNMTOKEN"
minOccurs="0"/> minOccurs="0"/>
<xsd:element name="component" maxOccurs="unbounded"> <xsd:element name="component" maxOccurs="unbounded">
<xsd:complexType> <xsd:complexType>
<xsd:sequence> <xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/> <xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/> <xsd:element ref="synopsis"/>
<xsd:element ref="description" minOccurs="0"/> <xsd:element ref="description" minOccurs="0"/>
<xsd:element name="optional" minOccurs="0"/> <xsd:element name="optional" minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/> <xsd:group ref="typeDeclarationGroup"/>
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="componentID" type="xsd:unsignedInt" <xsd:attribute name="componentID" type="xsd:unsignedInt"
use="required"/> use="required"/>
</xsd:complexType> </xsd:complexType>
</xsd:element> </xsd:element>
</xsd:sequence> </xsd:sequence>
</xsd:complexType> </xsd:complexType>
Figure 6: Initial xml for the struct definition in the schema Figure 7: Initial xml for the struct definition in the schema
<xsd:complexType name="structType">
<xsd:sequence>
<xsd:element name="derivedFrom" type="typeRefNMTOKEN"
minOccurs="0"/>
<xsd:element name="component" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description" minOccurs="0"/>
<xsd:element name="optional" minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/>
</xsd:sequence>
<xsd:attribute name="access" use="optional"
default="read-write">
<xsd:simpleType>
<xsd:list itemType="accessModeType"/>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="componentID" type="xsd:unsignedInt"
use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="structType"> Figure 8: New xml for the struct definition in the schema
<xsd:sequence>
<xsd:element name="derivedFrom" type="typeRefNMTOKEN"
minOccurs="0"/>
<xsd:element name="component" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description" minOccurs="0"/>
<xsd:element name="optional" minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/>
</xsd:sequence>
<xsd:attribute name="access" use="optional"
default="read-write">
<xsd:simpleType>
<xsd:list itemType="accessModeType"/>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="componentID" type="xsd:unsignedInt"
use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Figure 7: New xml for the struct definition in the schema <component componentID="1" access="read-write">
<name>PacketFlows</name>
<synopsis>Packet Flows, match and counter</synopsis>
<struct>
<component componentID="1">
<name>FlowMatch</name>
<synopsis>Flow Match</synopsis>
<typeRef>MatchType</typeRef>
</component>
<component componentID="2" access="read-only">
<name>MatchCounter</name>
<synopsis>Packets matching the flow match</synopsis>
<typeRef>uint32</typeRef>
<DefaultValue>0</DefaultValue>
</component>
</struct>
</component>
Figure 9: Example of optional access types for struct
3.4. New Event Condition: BecomesEqualTo 3.4. New Event Condition: BecomesEqualTo
This extensions adds one more event condition in the model schema, This extensions adds one more event condition in the model schema,
that of BecomesEqualTo. The difference between Greater Than and Less that of BecomesEqualTo. The difference between Greater Than and Less
Than, is that when the value is exactly that of the BecomesEqualTo, Than, is that when the value is exactly that of the BecomesEqualTo,
the event is triggered. This event condition is particular useful the event is triggered. This event condition is particular useful
when there is a need to monitor one or more states of an LFB or the when there is a need to monitor one or more states of an LFB or the
FE. For example in the CEHA [I-D.ietf-forces-ceha] document it may FE. For example in the CEHA [I-D.ietf-forces-ceha] document it may
be useful for the master CE to know which backup CEs have just become be useful for the master CE to know which backup CEs have just become
skipping to change at page 9, line 18 skipping to change at page 10, line 26
information but getting such an event will speed up the process and information but getting such an event will speed up the process and
the event may be useful in other cases as well for monitoring state. the event may be useful in other cases as well for monitoring state.
The event MUST be triggered only when the value of the targeted The event MUST be triggered only when the value of the targeted
component becomes equal to the event condition value and MUST NOT component becomes equal to the event condition value and MUST NOT
generate events while the targeted component's value remains equal to generate events while the targeted component's value remains equal to
the event condition's value. the event condition's value.
The BecomesEqualTo is appended to the schema as follows: The BecomesEqualTo is appended to the schema as follows:
<xsd:element name="eventBecomesEqualTo" <xsd:element name="eventBecomesEqualTo"
substitutionGroup="eventCondition"/> substitutionGroup="eventCondition"/>
Figure 8: New Excerpt of BecomesEqualTo event condition definition in Figure 10: New Excerpt of BecomesEqualTo event condition definition
the schema in the schema
It can become useful for the CE to be notified when the state has It can become useful for the CE to be notified when the state has
changed once the BecomesEqualTo event has been triggered, e.g. the CE changed once the BecomesEqualTo event has been triggered, e.g. the CE
may need to know when a backup CE has lost association. Such an may need to know when a backup CE has lost association. Such an
event can be generated either by defining a second event on the same event can be generated either by defining a second event on the same
component, namely an Event Changed, or by simply reusing component, namely an Event Changed, or by simply reusing
BecomesEqualTo and use event properties, in particular event BecomesEqualTo and use event properties, in particular event
hysteresis. We append the following definition for the event hysteresis. We append the following definition for the event
hysteresis defined in section 4.8.5.2 in [RFC5812], with V being the hysteresis defined in section 4.8.5.2 in [RFC5812], with V being the
hysteresis value: hysteresis value:
skipping to change at page 10, line 17 skipping to change at page 11, line 20
messages and errors for communication between CE and FE. These messages and errors for communication between CE and FE. These
properties are read-only. properties are read-only.
In order to avoid ambiguity on protocol path semantics, this document In order to avoid ambiguity on protocol path semantics, this document
reserves LFB component 0 for LFB properties. This reservation is reserves LFB component 0 for LFB properties. This reservation is
backwards compatible as no LFB definition uses LFB component 0. Any backwards compatible as no LFB definition uses LFB component 0. Any
command with a path starting from LFB component 0 refers to LFB command with a path starting from LFB component 0 refers to LFB
properties. The following change in the xml schema disallows usage properties. The following change in the xml schema disallows usage
of LFB component 0: of LFB component 0:
<xsd:attribute name="componentID" type="xsd:unsignedInt" <xsd:attribute name="componentID" type="xsd:unsignedInt"
use="required"> use="required">
Figure 9: Initial xml for LFB Component IDs Figure 11: Initial xml for LFB Component IDs
<!-- Extension Added restriction to component ID --> <!-- Extension Added restriction to component ID -->
<xsd:attribute name="componentID" use="required"> <xsd:attribute name="componentID" use="required">
<xsd:simpleType> <xsd:simpleType>
<xsd:restriction base="xsd:unsignedInt"> <xsd:restriction base="xsd:unsignedInt">
<xsd:minExclusive value="0"/> <xsd:minExclusive value="0"/>
</xsd:restriction> </xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
</xsd:attribute> </xsd:attribute>
<!-- End of extension --> <!-- End of extension -->
Figure 10: New xml for the disallowing usage of 0 as LFB Component Figure 12: New xml for the disallowing usage of 0 as LFB Component
The following datatype definitions are to be used as properties for The following datatype definitions are to be used as properties for
LFB instances. LFB instances.
<dataTypeDef> <dataTypeDef>
<name>LFBProperties</name> <name>LFBProperties</name>
<synopsis>LFB Properties definition</synopsis> <synopsis>LFB Properties definition</synopsis>
<struct> <struct>
<component componentID="1"> <component componentID="1">
<name>PacketsSentToCE</name> <name>PacketsSentToCE</name>
skipping to change at page 11, line 38 skipping to change at page 12, line 41
<component componentID="8"> <component componentID="8">
<name>ReceivedErrorBytesFromCE</name> <name>ReceivedErrorBytesFromCE</name>
<synopsis>Error Bytes received from CE</synopsis> <synopsis>Error Bytes received from CE</synopsis>
<typeRef>uint32</typeRef> <typeRef>uint32</typeRef>
</component> </component>
</struct> </struct>
</dataTypeDef> </dataTypeDef>
Properties for LFB instances Properties for LFB instances
3.6. Enhancing XML Validation 3.6. LFB class inheritance
The ForCES model [RFC5812] allows inheritance for LFB classes.
However the xml schema defines only the LFB class from which an LFB
class may inherit. Recent implementations have identified an issue
where ambiguity rises when different versions of an LFB class exists.
This document augments the derivedFrom part of the LFB class
definition with a mandatory version attribute when the derivedFrom
field is used.
This extension alters the definition of the derivedFrom in the xml
schema from Figure 13 to Figure 14.
<xsd:element name="derivedFrom" minOccurs="0"/>
Figure 13: Initial xml for the LFB class inheritance
<xsd:element name="derivedFrom" minOccurs="0">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:NMTOKEN">
<xsd:attribute name="version"
type="versionType" use="required"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
Figure 14: New xml for the LFB class inheritance
<derivedFrom version="1.0">EtherPHYCop</derivedFrom>
Figure 15: Example of use of new xml for LFB class Inheritance
3.7. Enhancing XML Validation
As specified earlier this is not an extension but an enhancement of As specified earlier this is not an extension but an enhancement of
the schema to provide additional validation rules. This includes the schema to provide additional validation rules. This includes
adding new key declarations to provide uniqueness as defined by the adding new key declarations to provide uniqueness as defined by the
ForCES Model [RFC5812]. Such validations work only on within the ForCES Model [RFC5812]. Such validations work only on within the
same xml file. same xml file.
The following validation rules have been appended in the original The following validation rules have been appended in the original
schema in [RFC5812]: schema in [RFC5812]:
skipping to change at page 12, line 17 skipping to change at page 14, line 7
3. Component ID, Capability ID and Event Base ID must be unique per 3. Component ID, Capability ID and Event Base ID must be unique per
LFB. LFB.
4. Event IDs must be unique per LFB. 4. Event IDs must be unique per LFB.
5. Special Values in Atomic datatypes must be unique per atomic 5. Special Values in Atomic datatypes must be unique per atomic
datatype. datatype.
4. XML Extension Schema for LFB Class Library Documents 4. XML Extension Schema for LFB Class Library Documents
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns:forces:lfbmodel:1.0" xmlns="urn:ietf:params:xml:ns:forces:lfbmodel:1.0"
xmlns:lfb="urn:ietf:params:xml:ns:forces:lfbmodel:1.0" xmlns:lfb="urn:ietf:params:xml:ns:forces:lfbmodel:1.0"
targetNamespace="urn:ietf:params:xml:ns:forces:lfbmodel:1.0" targetNamespace="urn:ietf:params:xml:ns:forces:lfbmodel:1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:annotation> <xsd:annotation>
<xsd:documentation xml:lang="en"> <xsd:documentation xml:lang="en">
Schema for Defining LFB Classes and associated types Schema for Defining LFB Classes and associated types
(frames, data types for LFB attributes, and metadata). (frames, data types for LFB attributes, and metadata).
</xsd:documentation> </xsd:documentation>
</xsd:annotation> </xsd:annotation>
<xsd:element name="description" type="xsd:string"/> <xsd:element name="description" type="xsd:string"/>
<xsd:element name="synopsis" type="xsd:string"/> <xsd:element name="synopsis" type="xsd:string"/>
<!-- Document root element: LFBLibrary --> <!-- Document root element: LFBLibrary -->
<xsd:element name="LFBLibrary"> <xsd:element name="LFBLibrary">
<xsd:complexType> <xsd:complexType>
<xsd:sequence>
<xsd:element ref="description" minOccurs="0"/>
<xsd:element name="load" type="loadType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="frameDefs" type="frameDefsType"
minOccurs="0"/>
<xsd:element name="dataTypeDefs" type="dataTypeDefsType"
minOccurs="0"/>
<xsd:element name="metadataDefs" type="metadataDefsType"
minOccurs="0"/>
<xsd:element name="LFBClassDefs" type="LFBClassDefsType"
minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="provides" type="xsd:Name"
use="required"/>
</xsd:complexType>
<!-- Uniqueness constraints -->
<xsd:key name="frame">
<xsd:selector xpath="lfb:frameDefs/lfb:frameDef"/>
<xsd:field xpath="lfb:name"/>
</xsd:key>
<xsd:key name="dataType">
<xsd:selector xpath="lfb:dataTypeDefs/lfb:dataTypeDef"/>
<xsd:field xpath="lfb:name"/>
</xsd:key>
<xsd:key name="metadataDef">
<xsd:selector xpath="lfb:metadataDefs/lfb:metadataDef"/>
<xsd:field xpath="lfb:name"/>
</xsd:key>
<xsd:key name="metadataDefID">
<xsd:selector xpath="lfb:metadataDefs/lfb:metadataDef"/>
<xsd:field xpath="lfb:metadataID"/>
</xsd:key>
<xsd:key name="LFBClassDef">
<xsd:selector xpath="lfb:LFBClassDefs/lfb:LFBClassDef"/>
<xsd:field xpath="lfb:name"/>
</xsd:key>
<xsd:key name="LFBClassDefID">
<xsd:selector xpath="lfb:LFBClassDefs/lfb:LFBClassDef"/>
<xsd:field xpath="@LFBClassID"/>
</xsd:key>
</xsd:element>
<xsd:complexType name="loadType">
<xsd:attribute name="library" type="xsd:Name" use="required"/>
<xsd:attribute name="location" type="xsd:anyURI"
use="optional"/>
</xsd:complexType>
<xsd:complexType name="frameDefsType">
<xsd:sequence>
<xsd:element name="frameDef" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description"
minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="dataTypeDefsType">
<xsd:sequence>
<xsd:element name="dataTypeDef" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element name="derivedFrom" type="xsd:NMTOKEN"
minOccurs="0"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description"
minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- Predefined (built-in) atomic data-types are: char, uchar,
int16, uint16, int32, uint32, int64, uint64, string[N], string,
byte[N], boolean, octetstring[N], float32, float64 -->
<xsd:group name="typeDeclarationGroup">
<xsd:choice>
<!-- Extension -->
<xsd:sequence>
<!-- /Extension -->
<xsd:element name="typeRef" type="typeRefNMTOKEN"/>
<!-- Extension -->
<xsd:element name="DefaultValue" type="xsd:token"
minOccurs="0"/>
</xsd:sequence>
<!-- /Extension -->
<xsd:element name="atomic" type="atomicType"/>
<xsd:element name="array" type="arrayType">
<!-- Extension -->
<!--declare keys to have unique IDs -->
<xsd:key name="contentKeyID">
<xsd:selector xpath="lfb:contentKey"/>
<xsd:field xpath="@contentKeyID"/>
</xsd:key>
<!-- /Extension -->
</xsd:element>
<xsd:element name="struct" type="structType">
<!-- Extension -->
<!-- key declaration to make componentIDs unique in a struct -->
<xsd:key name="structComponentID">
<xsd:selector xpath="lfb:component"/>
<xsd:field xpath="@componentID"/>
</xsd:key>
<!-- /Extension -->
</xsd:element>
<xsd:element name="union" type="structType"/>
<xsd:element name="alias" type="typeRefNMTOKEN"/>
</xsd:choice>
</xsd:group>
<xsd:simpleType name="typeRefNMTOKEN">
<xsd:restriction base="xsd:token">
<xsd:pattern value="\c+"/>
<xsd:pattern value="string\[\d+\]"/>
<xsd:pattern value="byte\[\d+\]"/>
<xsd:pattern value="octetstring\[\d+\]"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="atomicType">
<xsd:sequence> <xsd:sequence>
<xsd:element name="baseType" type="typeRefNMTOKEN"/> <xsd:element ref="description" minOccurs="0"/>
<xsd:element name="rangeRestriction" type="rangeRestrictionType" <xsd:element name="load" type="loadType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="frameDefs" type="frameDefsType"
minOccurs="0"/> minOccurs="0"/>
<xsd:element name="specialValues" type="specialValuesType" <xsd:element name="dataTypeDefs" type="dataTypeDefsType"
minOccurs="0">
<!-- Extension -->
<xsd:key name="SpecialValue">
<xsd:selector xpath="specialValue"/>
<xsd:field xpath="@value"/>
</xsd:key>
<!-- /Extension -->
</xsd:element>
<!-- Extension -->
<xsd:element name="defaultValue" type="xsd:token"
minOccurs="0"/> minOccurs="0"/>
<!-- /Extension --> <xsd:element name="metadataDefs" type="metadataDefsType"
</xsd:sequence> minOccurs="0"/>
</xsd:complexType> <xsd:element name="LFBClassDefs" type="LFBClassDefsType"
<xsd:complexType name="rangeRestrictionType">
<xsd:sequence>
<xsd:element name="allowedRange" maxOccurs="unbounded">
<xsd:complexType>
<xsd:attribute name="min" type="xsd:integer"
use="required"/>
<xsd:attribute name="max" type="xsd:integer"
use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="specialValuesType">
<xsd:sequence>
<xsd:element name="specialValue" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
</xsd:sequence>
<xsd:attribute name="value" type="xsd:token"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="arrayType">
<xsd:sequence>
<xsd:group ref="typeDeclarationGroup"/>
<xsd:element name="contentKey" minOccurs="0"
maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="contentKeyField"
type="xsd:string" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="contentKeyID" type="xsd:integer"
use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="type" use="optional" default="variable-size">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="fixed-size"/>
<xsd:enumeration value="variable-size"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="length" type="xsd:integer"
use="optional"/>
<xsd:attribute name="maxLength" type="xsd:integer"
use="optional"/>
</xsd:complexType>
<xsd:complexType name="structType">
<xsd:sequence>
<xsd:element name="derivedFrom" type="typeRefNMTOKEN"
minOccurs="0"/> minOccurs="0"/>
<xsd:element name="component" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description"
minOccurs="0"/>
<xsd:element name="optional" minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/>
</xsd:sequence>
<xsd:attribute name="access" use="optional"
default="read-write">
<xsd:simpleType>
<xsd:list itemType="accessModeType"/>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="componentID" type="xsd:unsignedInt"
use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="metadataDefsType">
<xsd:sequence>
<xsd:element name="metadataDef" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element name="metadataID" type="xsd:integer"/>
<xsd:element ref="description"
minOccurs="0"/>
<xsd:choice>
<xsd:element name="typeRef" type="typeRefNMTOKEN"/>
<xsd:element name="atomic" type="atomicType"/>
<!-- Extension -->
<xsd:element name="array" type="arrayType">
<!--declare keys to have unique IDs -->
<xsd:key name="contentKeyID1">
<xsd:selector xpath="lfb:contentKey"/>
<xsd:field xpath="@contentKeyID"/>
</xsd:key>
<!-- /Extension -->
</xsd:element>
<xsd:element name="struct" type="structType">
<!-- Extension -->
<!-- key declaration to make componentIDs unique
in a struct -->
<xsd:key name="structComponentID1">
<xsd:selector xpath="lfb:component"/>
<xsd:field xpath="@componentID"/>
</xsd:key>
<!-- /Extension -->
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="provides" type="xsd:Name"
use="required"/>
</xsd:complexType> </xsd:complexType>
<xsd:complexType name="LFBClassDefsType"> <!-- Uniqueness constraints -->
<xsd:sequence> <xsd:key name="frame">
<xsd:element name="LFBClassDef" maxOccurs="unbounded"> <xsd:selector xpath="lfb:frameDefs/lfb:frameDef"/>
<xsd:complexType> <xsd:field xpath="lfb:name"/>
<xsd:sequence> </xsd:key>
<xsd:element name="name" type="xsd:NMTOKEN"/> <xsd:key name="dataType">
<xsd:element ref="synopsis"/> <xsd:selector xpath="lfb:dataTypeDefs/lfb:dataTypeDef"/>
<xsd:element name="version" type="versionType"/> <xsd:field xpath="lfb:name"/>
<xsd:element name="derivedFrom" type="xsd:NMTOKEN" </xsd:key>
minOccurs="0"/> <xsd:key name="metadataDef">
<xsd:element name="inputPorts" <xsd:selector xpath="lfb:metadataDefs/lfb:metadataDef"/>
type="inputPortsType" minOccurs="0"/> <xsd:field xpath="lfb:name"/>
<xsd:element name="outputPorts" </xsd:key>
type="outputPortsType" minOccurs="0"/> <xsd:key name="metadataDefID">
<xsd:element name="components" <xsd:selector xpath="lfb:metadataDefs/lfb:metadataDef"/>
type="LFBComponentsType" minOccurs="0"/> <xsd:field xpath="lfb:metadataID"/>
<xsd:element name="capabilities" </xsd:key>
type="LFBCapabilitiesType" minOccurs="0"/> <xsd:key name="LFBClassDef">
<xsd:element name="events" type="eventsType" <xsd:selector xpath="lfb:LFBClassDefs/lfb:LFBClassDef"/>
minOccurs="0"/> <xsd:field xpath="lfb:name"/>
<xsd:element ref="description" </xsd:key>
minOccurs="0"/> <xsd:key name="LFBClassDefID">
</xsd:sequence> <xsd:selector xpath="lfb:LFBClassDefs/lfb:LFBClassDef"/>
<xsd:attribute name="LFBClassID" type="xsd:unsignedInt" <xsd:field xpath="@LFBClassID"/>
use="required"/> </xsd:key>
</xsd:complexType> </xsd:element>
<!-- Key constraint to ensure unique attribute names <xsd:complexType name="loadType">
within a class: --> <xsd:attribute name="library" type="xsd:Name" use="required"/>
<xsd:key name="components"> <xsd:attribute name="location" type="xsd:anyURI"
<xsd:selector xpath="lfb:components/lfb:component"/> use="optional"/>
<xsd:field xpath="lfb:name"/> </xsd:complexType>
</xsd:key> <xsd:complexType name="frameDefsType">
<xsd:key name="capabilities"> <xsd:sequence>
<xsd:selector xpath="lfb:capabilities/lfb:capability"/> <xsd:element name="frameDef" maxOccurs="unbounded">
<xsd:field xpath="lfb:name"/> <xsd:complexType>
</xsd:key> <xsd:sequence>
<xsd:key name="events"> <xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:selector xpath="lfb:events/lfb:event"/> <xsd:element ref="synopsis"/>
<xsd:field xpath="lfb:name"/> <xsd:element ref="description"
</xsd:key> minOccurs="0"/>
<xsd:key name="eventsIDs"> </xsd:sequence>
<xsd:selector xpath="lfb:events/lfb:event"/> </xsd:complexType>
<xsd:field xpath="@eventID"/> </xsd:element>
</xsd:key> </xsd:sequence>
<xsd:key name="componentIDs"> </xsd:complexType>
<xsd:selector xpath="lfb:components/lfb:component"/> <xsd:complexType name="dataTypeDefsType">
<xsd:field xpath="@componentID"/> <xsd:sequence>
<xsd:element name="dataTypeDef" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element name="derivedFrom" type="xsd:NMTOKEN"
minOccurs="0"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description"
minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:key> </xsd:complexType>
<xsd:key name="capabilityIDs"> <!-- Predefined (built-in) atomic data-types are: char, uchar,
<xsd:selector xpath="lfb:capabilities/lfb:capability"/> int16, uint16, int32, uint32, int64, uint64, string[N], string,
<xsd:field xpath="@componentID"/> byte[N], boolean, octetstring[N], float32, float64 -->
</xsd:key> <xsd:group name="typeDeclarationGroup">
<xsd:key name="ComponentCapabilityComponentIDUniqueness"> <xsd:choice>
<xsd:selector <!-- Extension -->
xpath="lfb:components/lfb:component|
lfb:capabilities/lfb:capability|lfb:events"/>
<xsd:field xpath="@componentID|@baseID"/>
</xsd:key>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="versionType">
<xsd:restriction base="xsd:NMTOKEN">
<xsd:pattern value="[1-9][0-9]*\.([1-9][0-9]*|0)"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="inputPortsType">
<xsd:sequence>
<xsd:element name="inputPort" type="inputPortType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="inputPortType">
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element name="expectation" type="portExpectationType"/>
<xsd:element ref="description" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="group" type="xsd:boolean"
use="optional" default="0"/>
</xsd:complexType>
<xsd:complexType name="portExpectationType">
<xsd:sequence> <xsd:sequence>
<xsd:element name="frameExpected" minOccurs="0"> <!-- /Extension -->
<xsd:complexType> <xsd:element name="typeRef" type="typeRefNMTOKEN"/>
<xsd:sequence> <!-- Extension -->
<!-- ref must refer to a name of a defined <xsd:element name="DefaultValue" type="xsd:token"
frame type --> minOccurs="0"/>
<xsd:element name="ref" type="xsd:string"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="metadataExpected" minOccurs="0">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<!--ref must refer to a name of a defined metadata-->
<xsd:element name="ref" type="metadataInputRefType"/>
<xsd:element name="one-of"
type="metadataInputChoiceType"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:sequence> </xsd:sequence>
</xsd:complexType> <!-- /Extension -->
<xsd:complexType name="metadataInputChoiceType"> <xsd:element name="atomic" type="atomicType"/>
<xsd:choice minOccurs="2" maxOccurs="unbounded"> <xsd:element name="array" type="arrayType">
<!-- ref must refer to a name of a defined metadata --> <!-- Extension -->
<xsd:element name="ref" type="xsd:NMTOKEN"/> <!--declare keys to have unique IDs -->
<xsd:element name="one-of" type="metadataInputChoiceType"/> <xsd:key name="contentKeyID">
<xsd:element name="metadataSet" type="metadataInputSetType"/> <xsd:selector xpath="lfb:contentKey"/>
</xsd:choice> <xsd:field xpath="@contentKeyID"/>
</xsd:complexType> </xsd:key>
<xsd:complexType name="metadataInputSetType"> <!-- /Extension -->
<xsd:choice minOccurs="2" maxOccurs="unbounded"> </xsd:element>
<!-- ref must refer to a name of a defined metadata --> <xsd:element name="struct" type="structType">
<xsd:element name="ref" type="metadataInputRefType"/> <!-- Extension -->
<xsd:element name="one-of" type="metadataInputChoiceType"/> <!-- key declaration to make componentIDs unique in a struct -->
</xsd:choice> <xsd:key name="structComponentID">
</xsd:complexType> <xsd:selector xpath="lfb:component"/>
<xsd:complexType name="metadataInputRefType"> <xsd:field xpath="@componentID"/>
<xsd:simpleContent> </xsd:key>
<xsd:extension base="xsd:NMTOKEN"> <!-- /Extension -->
<xsd:attribute name="dependency" use="optional" </xsd:element>
default="required"> <xsd:element name="union" type="structType"/>
<xsd:element name="alias" type="typeRefNMTOKEN"/>
</xsd:choice>
</xsd:group>
<xsd:simpleType name="typeRefNMTOKEN">
<xsd:restriction base="xsd:token">
<xsd:pattern value="\c+"/>
<xsd:pattern value="string\[\d+\]"/>
<xsd:pattern value="byte\[\d+\]"/>
<xsd:pattern value="octetstring\[\d+\]"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="atomicType">
<xsd:sequence>
<xsd:element name="baseType" type="typeRefNMTOKEN"/>
<xsd:element name="rangeRestriction" type="rangeRestrictionType"
minOccurs="0"/>
<xsd:element name="specialValues" type="specialValuesType"
minOccurs="0">
<!-- Extension -->
<xsd:key name="SpecialValue">
<xsd:selector xpath="specialValue"/>
<xsd:field xpath="@value"/>
</xsd:key>
<!-- /Extension -->
</xsd:element>
<!-- Extension -->
<xsd:element name="defaultValue" type="xsd:token"
minOccurs="0"/>
<!-- /Extension -->
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="rangeRestrictionType">
<xsd:sequence>
<xsd:element name="allowedRange" maxOccurs="unbounded">
<xsd:complexType>
<xsd:attribute name="min" type="xsd:integer"
use="required"/>
<xsd:attribute name="max" type="xsd:integer"
use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="specialValuesType">
<xsd:sequence>
<xsd:element name="specialValue" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
</xsd:sequence>
<xsd:attribute name="value" type="xsd:token"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="arrayType">
<xsd:sequence>
<xsd:group ref="typeDeclarationGroup"/>
<xsd:element name="contentKey" minOccurs="0"
maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="contentKeyField"
type="xsd:string" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="contentKeyID" type="xsd:integer"
use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="type" use="optional" default="variable-size">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="fixed-size"/>
<xsd:enumeration value="variable-size"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="length" type="xsd:integer"
use="optional"/>
<xsd:attribute name="maxLength" type="xsd:integer"
use="optional"/>
</xsd:complexType>
<xsd:complexType name="structType">
<xsd:sequence>
<xsd:element name="derivedFrom" type="typeRefNMTOKEN"
minOccurs="0"/>
<xsd:element name="component" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description"
minOccurs="0"/>
<xsd:element name="optional" minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/>
</xsd:sequence>
<xsd:attribute name="access" use="optional"
default="read-write">
<xsd:simpleType> <xsd:simpleType>
<xsd:restriction base="xsd:string"> <xsd:list itemType="accessModeType"/>
<xsd:enumeration value="required"/>
<xsd:enumeration value="optional"/>
</xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
</xsd:attribute> </xsd:attribute>
<xsd:attribute name="defaultValue" type="xsd:token" <xsd:attribute name="componentID" type="xsd:unsignedInt"
use="optional"/> use="required"/>
</xsd:extension> </xsd:complexType>
</xsd:simpleContent> </xsd:element>
</xsd:complexType> </xsd:sequence>
<xsd:complexType name="outputPortsType">
<xsd:sequence>
<xsd:element name="outputPort" type="outputPortType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType> </xsd:complexType>
<xsd:complexType name="outputPortType"> <xsd:complexType name="metadataDefsType">
<xsd:sequence> <xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/> <xsd:element name="metadataDef" maxOccurs="unbounded">
<xsd:element ref="synopsis"/> <xsd:complexType>
<xsd:element name="product" type="portProductType"/> <xsd:sequence>
<xsd:element ref="description" minOccurs="0"/> <xsd:element name="name" type="xsd:NMTOKEN"/>
</xsd:sequence> <xsd:element ref="synopsis"/>
<xsd:attribute name="group" type="xsd:boolean" <xsd:element name="metadataID" type="xsd:integer"/>
use="optional" default="0"/> <xsd:element ref="description"
</xsd:complexType> minOccurs="0"/>
<xsd:complexType name="portProductType"> <xsd:choice>
<xsd:sequence> <xsd:element name="typeRef" type="typeRefNMTOKEN"/>
<xsd:element name="frameProduced" minOccurs="0"> <xsd:element name="atomic" type="atomicType"/>
<xsd:complexType> <!-- Extension -->
<xsd:sequence> <xsd:element name="array" type="arrayType">
<!-- ref must refer to a name of a defined <!--declare keys to have unique IDs -->
frame type --> <xsd:key name="contentKeyID1">
<xsd:element name="ref" type="xsd:NMTOKEN" <xsd:selector xpath="lfb:contentKey"/>
maxOccurs="unbounded"/> <xsd:field xpath="@contentKeyID"/>
</xsd:sequence> </xsd:key>
</xsd:complexType> <!-- /Extension -->
</xsd:element> </xsd:element>
<xsd:element name="metadataProduced" minOccurs="0"> <xsd:element name="struct" type="structType">
<xsd:complexType> <!-- Extension -->
<xsd:choice maxOccurs="unbounded"> <!-- key declaration to make componentIDs unique
<!-- ref must refer to a name of a in a struct -->
defined metadata --> <xsd:key name="structComponentID1">
<xsd:element name="ref" <xsd:selector xpath="lfb:component"/>
type="metadataOutputRefType"/> <xsd:field xpath="@componentID"/>
<xsd:element name="one-of" </xsd:key>
type="metadataOutputChoiceType"/> <!-- /Extension -->
</xsd:element>
</xsd:choice> </xsd:choice>
</xsd:complexType> </xsd:sequence>
</xsd:element> </xsd:complexType>
</xsd:sequence> </xsd:element>
</xsd:complexType> </xsd:sequence>
<xsd:complexType name="metadataOutputChoiceType"> </xsd:complexType>
<xsd:choice minOccurs="2" maxOccurs="unbounded"> <xsd:complexType name="LFBClassDefsType">
<!-- ref must refer to a name of a defined metadata --> <xsd:sequence>
<xsd:element name="ref" type="xsd:NMTOKEN"/> <xsd:element name="LFBClassDef" maxOccurs="unbounded">
<xsd:element name="one-of" type="metadataOutputChoiceType"/> <xsd:complexType>
<xsd:element name="metadataSet" type="metadataOutputSetType"/> <xsd:sequence>
</xsd:choice> <xsd:element name="name" type="xsd:NMTOKEN"/>
</xsd:complexType> <xsd:element ref="synopsis"/>
<xsd:complexType name="metadataOutputSetType"> <xsd:element name="version" type="versionType"/>
<xsd:choice minOccurs="2" maxOccurs="unbounded"> <xsd:element name="derivedFrom" minOccurs="0">
<!-- ref must refer to a name of a defined metadata --> <xsd:complexType>
<xsd:element name="ref" type="metadataOutputRefType"/> <xsd:simpleContent>
<xsd:element name="one-of" type="metadataOutputChoiceType"/> <xsd:extension base="xsd:NMTOKEN">
</xsd:choice> <xsd:attribute name="version"
</xsd:complexType> type="versionType" use="required"/>
<xsd:complexType name="metadataOutputRefType"> </xsd:extension>
<xsd:simpleContent> </xsd:simpleContent>
<xsd:extension base="xsd:NMTOKEN"> </xsd:complexType>
<xsd:attribute name="availability" use="optional" </xsd:element>
default="unconditional"> <xsd:element name="inputPorts"
type="inputPortsType" minOccurs="0"/>
<xsd:element name="outputPorts"
type="outputPortsType" minOccurs="0"/>
<xsd:element name="components"
type="LFBComponentsType" minOccurs="0"/>
<xsd:element name="capabilities"
type="LFBCapabilitiesType" minOccurs="0"/>
<xsd:element name="events" type="eventsType"
minOccurs="0"/>
<xsd:element ref="description"
minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="LFBClassID" type="xsd:unsignedInt"
use="required"/>
</xsd:complexType>
<!-- Key constraint to ensure unique attribute names
within a class: -->
<xsd:key name="components">
<xsd:selector xpath="lfb:components/lfb:component"/>
<xsd:field xpath="lfb:name"/>
</xsd:key>
<xsd:key name="capabilities">
<xsd:selector xpath="lfb:capabilities/lfb:capability"/>
<xsd:field xpath="lfb:name"/>
</xsd:key>
<xsd:key name="events">
<xsd:selector xpath="lfb:events/lfb:event"/>
<xsd:field xpath="lfb:name"/>
</xsd:key>
<xsd:key name="eventsIDs">
<xsd:selector xpath="lfb:events/lfb:event"/>
<xsd:field xpath="@eventID"/>
</xsd:key>
<xsd:key name="componentIDs">
<xsd:selector xpath="lfb:components/lfb:component"/>
<xsd:field xpath="@componentID"/>
</xsd:key>
<xsd:key name="capabilityIDs">
<xsd:selector xpath="lfb:capabilities/lfb:capability"/>
<xsd:field xpath="@componentID"/>
</xsd:key>
<xsd:key name="ComponentCapabilityComponentIDUniqueness">
<xsd:selector
xpath="lfb:components/lfb:component|
lfb:capabilities/lfb:capability|lfb:events"/>
<xsd:field xpath="@componentID|@baseID"/>
</xsd:key>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="versionType">
<xsd:restriction base="xsd:NMTOKEN">
<xsd:pattern value="[1-9][0-9]*\.([1-9][0-9]*|0)"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="inputPortsType">
<xsd:sequence>
<xsd:element name="inputPort" type="inputPortType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="inputPortType">
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element name="expectation" type="portExpectationType"/>
<xsd:element ref="description" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="group" type="xsd:boolean"
use="optional" default="0"/>
</xsd:complexType>
<xsd:complexType name="portExpectationType">
<xsd:sequence>
<xsd:element name="frameExpected" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<!-- ref must refer to a name of a defined
frame type -->
<xsd:element name="ref" type="xsd:string"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="metadataExpected" minOccurs="0">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<!--ref must refer to a name of a defined metadata-->
<xsd:element name="ref" type="metadataInputRefType"/>
<xsd:element name="one-of"
type="metadataInputChoiceType"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="metadataInputChoiceType">
<xsd:choice minOccurs="2" maxOccurs="unbounded">
<!-- ref must refer to a name of a defined metadata -->
<xsd:element name="ref" type="xsd:NMTOKEN"/>
<xsd:element name="one-of" type="metadataInputChoiceType"/>
<xsd:element name="metadataSet" type="metadataInputSetType"/>
</xsd:choice>
</xsd:complexType>
<xsd:complexType name="metadataInputSetType">
<xsd:choice minOccurs="2" maxOccurs="unbounded">
<!-- ref must refer to a name of a defined metadata -->
<xsd:element name="ref" type="metadataInputRefType"/>
<xsd:element name="one-of" type="metadataInputChoiceType"/>
</xsd:choice>
</xsd:complexType>
<xsd:complexType name="metadataInputRefType">
<xsd:simpleContent>
<xsd:extension base="xsd:NMTOKEN">
<xsd:attribute name="dependency" use="optional"
default="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="required"/>
<xsd:enumeration value="optional"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="defaultValue" type="xsd:token"
use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="outputPortsType">
<xsd:sequence>
<xsd:element name="outputPort" type="outputPortType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="outputPortType">
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element name="product" type="portProductType"/>
<xsd:element ref="description" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="group" type="xsd:boolean"
use="optional" default="0"/>
</xsd:complexType>
<xsd:complexType name="portProductType">
<xsd:sequence>
<xsd:element name="frameProduced" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<!-- ref must refer to a name of a defined
frame type -->
<xsd:element name="ref" type="xsd:NMTOKEN"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="metadataProduced" minOccurs="0">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<!-- ref must refer to a name of a
defined metadata -->
<xsd:element name="ref"
type="metadataOutputRefType"/>
<xsd:element name="one-of"
type="metadataOutputChoiceType"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="metadataOutputChoiceType">
<xsd:choice minOccurs="2" maxOccurs="unbounded">
<!-- ref must refer to a name of a defined metadata -->
<xsd:element name="ref" type="xsd:NMTOKEN"/>
<xsd:element name="one-of" type="metadataOutputChoiceType"/>
<xsd:element name="metadataSet" type="metadataOutputSetType"/>
</xsd:choice>
</xsd:complexType>
<xsd:complexType name="metadataOutputSetType">
<xsd:choice minOccurs="2" maxOccurs="unbounded">
<!-- ref must refer to a name of a defined metadata -->
<xsd:element name="ref" type="metadataOutputRefType"/>
<xsd:element name="one-of" type="metadataOutputChoiceType"/>
</xsd:choice>
</xsd:complexType>
<xsd:complexType name="metadataOutputRefType">
<xsd:simpleContent>
<xsd:extension base="xsd:NMTOKEN">
<xsd:attribute name="availability" use="optional"
default="unconditional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="unconditional"/>
<xsd:enumeration value="conditional"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="LFBComponentsType">
<xsd:sequence>
<xsd:element name="component" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description"
minOccurs="0"/>
<xsd:element name="optional" minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/>
<xsd:element name="defaultValue" type="xsd:token"
minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="access" use="optional"
default="read-write">
<xsd:simpleType> <xsd:simpleType>
<xsd:restriction base="xsd:string"> <xsd:list itemType="accessModeType"/>
<xsd:enumeration value="unconditional"/> </xsd:simpleType>
<xsd:enumeration value="conditional"/> </xsd:attribute>
<!-- Extension Added restriction to component ID -->
<xsd:attribute name="componentID" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:unsignedInt">
<xsd:minExclusive value="0"/>
</xsd:restriction> </xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
</xsd:attribute> </xsd:attribute>
</xsd:extension> <!-- End of extension -->
</xsd:simpleContent> </xsd:complexType>
</xsd:complexType> </xsd:element>
<xsd:complexType name="LFBComponentsType">
<xsd:sequence>
<xsd:element name="component" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:element ref="synopsis"/>
<xsd:element ref="description"
minOccurs="0"/>
<xsd:element name="optional" minOccurs="0"/>
<xsd:group ref="typeDeclarationGroup"/>
<xsd:element name="defaultValue" type="xsd:token"
minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="access" use="optional"
default="read-write">
<xsd:simpleType>
<xsd:list itemType="accessModeType"/>
</xsd:simpleType>
</xsd:attribute>
<!-- Extension Added restriction to component ID -->
<xsd:attribute name="componentID" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:unsignedInt">
<xsd:minExclusive value="0"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<!-- End of extension -->
</xsd:complexType> </xsd:sequence>
</xsd:element> </xsd:complexType>
</xsd:sequence> <xsd:simpleType name="accessModeType">
</xsd:complexType> <xsd:restriction base="xsd:NMTOKEN">
<xsd:simpleType name="accessModeType"> <xsd:enumeration value="read-only"/>
<xsd:restriction base="xsd:NMTOKEN"> <xsd:enumeration value="read-write"/>
<xsd:enumeration value="read-only"/> <xsd:enumeration value="write-only"/>
<xsd:enumeration value="read-write"/> <xsd:enumeration value="read-reset"/>
<xsd:enumeration value="write-only"/> <xsd:enumeration value="trigger-only"/>
<xsd:enumeration value="read-reset"/> </xsd:restriction>
<xsd:enumeration value="trigger-only"/> </xsd:simpleType>
</xsd:restriction> <xsd:complexType name="LFBCapabilitiesType">
</xsd:simpleType> <xsd:sequence>
<xsd:complexType name="LFBCapabilitiesType"> <xsd:element name="capability" maxOccurs="unbounded">
<xsd:sequence> <xsd:complexType>
<xsd:element name="capability" maxOccurs="unbounded"> <xsd:sequence>
<xsd:complexType> <xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:sequence> <xsd:element ref="synopsis"/>
<xsd:element name="name" type="xsd:NMTOKEN"/> <xsd:element ref="description"
<xsd:element ref="synopsis"/> minOccurs="0"/>
<xsd:element ref="description" <xsd:element name="optional" minOccurs="0"/>
minOccurs="0"/> <xsd:group ref="typeDeclarationGroup"/>
<xsd:element name="optional" minOccurs="0"/> </xsd:sequence>
<xsd:group ref="typeDeclarationGroup"/> <xsd:attribute name="componentID" type="xsd:integer"
</xsd:sequence> use="required"/>
<xsd:attribute name="componentID" type="xsd:integer" </xsd:complexType>
use="required"/> </xsd:element>
</xsd:complexType> </xsd:sequence>
</xsd:element> </xsd:complexType>
</xsd:sequence> <xsd:complexType name="eventsType">
</xsd:complexType> <xsd:sequence>
<xsd:complexType name="eventsType"> <xsd:element name="event" maxOccurs="unbounded">
<xsd:sequence> <xsd:complexType>
<xsd:element name="event" maxOccurs="unbounded"> <xsd:sequence>
<xsd:complexType> <xsd:element name="name" type="xsd:NMTOKEN"/>
<xsd:sequence> <xsd:element ref="synopsis"/>
<xsd:element name="name" type="xsd:NMTOKEN"/> <xsd:element name="eventTarget"
<xsd:element ref="synopsis"/> type="eventPathType"/>
<xsd:element name="eventTarget" <xsd:element ref="eventCondition"/>
type="eventPathType"/> <xsd:element name="eventReports"
<xsd:element ref="eventCondition"/> type="eventReportsType" minOccurs="0"/>
<xsd:element name="eventReports" <xsd:element ref="description"
type="eventReportsType" minOccurs="0"/> minOccurs="0"/>
<xsd:element ref="description" </xsd:sequence>
minOccurs="0"/> <xsd:attribute name="eventID" type="xsd:integer"
</xsd:sequence> use="required"/>
<xsd:attribute name="eventID" type="xsd:integer" </xsd:complexType>
use="required"/> </xsd:element>
</xsd:sequence>
<xsd:attribute name="baseID" type="xsd:integer"
use="optional"/>
</xsd:complexType>
<!-- the substitution group for the event conditions -->
<xsd:element name="eventCondition" abstract="true"/>
<xsd:element name="eventCreated"
substitutionGroup="eventCondition"/>
<xsd:element name="eventDeleted"
substitutionGroup="eventCondition"/>
<xsd:element name="eventChanged"
substitutionGroup="eventCondition"/>
<xsd:element name="eventGreaterThan"
substitutionGroup="eventCondition"/>
<xsd:element name="eventLessThan"
substitutionGroup="eventCondition"/>
<!-- Extension -->
<xsd:element name="eventBecomesEqualTo"
substitutionGroup="eventCondition"/>
<!-- /Extension -->
<xsd:complexType name="eventPathType">
<xsd:sequence>
<xsd:element ref="eventPathPart" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<!-- the substitution group for the event path parts -->
<xsd:element name="eventPathPart" type="xsd:string"
abstract="true"/>
<xsd:element name="eventField" type="xsd:string"
substitutionGroup="eventPathPart"/>
<xsd:element name="eventSubscript" type="xsd:string"
substitutionGroup="eventPathPart"/>
<xsd:complexType name="eventReportsType">
<xsd:sequence>
<xsd:element name="eventReport" type="eventPathType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="booleanType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="0"/>
<xsd:enumeration value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="baseID" type="xsd:integer"
use="optional"/>
</xsd:complexType>
<!-- the substitution group for the event conditions -->
<xsd:element name="eventCondition" abstract="true"/>
<xsd:element name="eventCreated"
substitutionGroup="eventCondition"/>
<xsd:element name="eventDeleted"
substitutionGroup="eventCondition"/>
<xsd:element name="eventChanged"
substitutionGroup="eventCondition"/>
<xsd:element name="eventGreaterThan"
substitutionGroup="eventCondition"/>
<xsd:element name="eventLessThan"
substitutionGroup="eventCondition"/>
<!-- Extension -->
<xsd:element name="eventBecomesEqualTo"
substitutionGroup="eventCondition"/>
<!-- /Extension -->
<xsd:complexType name="eventPathType">
<xsd:sequence>
<xsd:element ref="eventPathPart" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<!-- the substitution group for the event path parts -->
<xsd:element name="eventPathPart" type="xsd:string"
abstract="true"/>
<xsd:element name="eventField" type="xsd:string"
substitutionGroup="eventPathPart"/>
<xsd:element name="eventSubscript" type="xsd:string"
substitutionGroup="eventPathPart"/>
<xsd:complexType name="eventReportsType">
<xsd:sequence>
<xsd:element name="eventReport" type="eventPathType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="booleanType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="0"/>
<xsd:enumeration value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
OpenFlow XML Library OpenFlow XML Library
5. Acknowledgements 5. Acknowledgements
The author would like to acknowledge Joel Halpern, Jamal Hadi and The author would like to acknowledge Joel Halpern, Jamal Hadi Salim
Dave Hood for their comments and discussion that helped shape this and Dave Hood for their comments and discussion that helped shape
document in a better way. this document in a better way.
6. IANA Considerations 6. IANA Considerations
This specification requests that LFB Component ID 0 to be reserved. This specification requests that LFB Component ID 0 to be reserved.
7. Security Considerations 7. Security Considerations
The security considerations that have been described in the ForCES The security considerations that have been described in the ForCES
Model RFC [RFC5812] apply to this document as well. Model RFC [RFC5812] apply to this document as well.
skipping to change at page 25, line 32 skipping to change at page 27, line 31
8.1. Normative References 8.1. Normative References
[I-D.ietf-forces-ceha] [I-D.ietf-forces-ceha]
Ogawa, K., Wang, W., Haleplidis, E., and J. Salim, "ForCES Ogawa, K., Wang, W., Haleplidis, E., and J. Salim, "ForCES
Intra-NE High Availability", draft-ietf-forces-ceha-08 Intra-NE High Availability", draft-ietf-forces-ceha-08
(work in progress), October 2013. (work in progress), October 2013.
[OpenFlowSpec1.1] [OpenFlowSpec1.1]
http://www.OpenFlow.org/, "The OpenFlow 1.1 http://www.OpenFlow.org/, "The OpenFlow 1.1
Specification.", , <http://www.OpenFlow.org/documents/ Specification.", <http://www.OpenFlow.org/documents/
OpenFlow-spec-v1.1.0.pdf>. OpenFlow-spec-v1.1.0.pdf>.
[RFC5810] Doria, A., Hadi Salim, J., Haas, R., Khosravi, H., Wang, [RFC5810] Doria, A., Hadi Salim, J., Haas, R., Khosravi, H., Wang,
W., Dong, L., Gopal, R., and J. Halpern, "Forwarding and W., Dong, L., Gopal, R., and J. Halpern, "Forwarding and
Control Element Separation (ForCES) Protocol Control Element Separation (ForCES) Protocol
Specification", RFC 5810, March 2010. Specification", RFC 5810, March 2010.
[RFC5812] Halpern, J. and J. Hadi Salim, "Forwarding and Control [RFC5812] Halpern, J. and J. Hadi Salim, "Forwarding and Control
Element Separation (ForCES) Forwarding Element Model", RFC Element Separation (ForCES) Forwarding Element Model", RFC
5812, March 2010. 5812, March 2010.
 End of changes. 46 change blocks. 
746 lines changed or deleted 830 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/