Subject: [forces] FW: New Version Notification for draft-haleplidis-forces-model-extension-04.txt

From: "Haleplidis Evangelos" <[email-masked]>
Date: Mon, 8 Jul 2013 19:56:49 +0300

Greetings to the list,

Just updated the forces model extensions draft.
Included is Jamal's request for LFB properties.

The document is also slightly restructured for readability.

Regards,
Evangelos Haleplidis.

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: Monday, July 08, 2013 7:52 PM
> To: Evangelos Haleplidis
> Subject: New Version Notification for draft-haleplidis-forces-model-
> extension-04.txt
> 
> 
> A new version of I-D, draft-haleplidis-forces-model-extension-04.txt
> has been successfully submitted by Evangelos Haleplidis and posted to
> the IETF repository.
> 
> Filename:	 draft-haleplidis-forces-model-extension
> Revision:	 04
> Title:		 ForCES Model Extension
> Creation date:	 2013-07-08
> Group:		 Individual Submission
> Number of pages: 26
> URL:             http://www.ietf.org/internet-drafts/draft-haleplidis-forces-model-extension-04.txt
> Status:          http://datatracker.ietf.org/doc/draft-haleplidis-forces-model-extension
> Htmlized:        http://tools.ietf.org/html/draft-haleplidis-forces-model-extension-04
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-haleplidis-forces-model-extension-04
> 
> Abstract:
>    Forwarding and Control Element Separation (ForCES) defines an
>    architectural framework and associated protocols to standardize
>    information exchange between the control plane and the forwarding
>    plane in a ForCES Network Element (ForCES NE).  RFC5812 has defined
>    the ForCES Model provides a formal way to represent the
> capabilities,
>    state, and configuration of forwarding elements within the context
> of
>    the ForCES protocol, so that control elements (CEs) can control the
>    FEs accordingly.  More specifically, the model describes the logical
>    functions that are present in an FE, what capabilities these
>    functions support, and how these functions are or can be
>    interconnected.
> 
>    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
>    while retaining backward compatibility with older xml libraries.
>    This document extends the model to allow complex datatypes for
>    metadata, optional default values for datatypes and optional access
>    types for structures.  The document also introduces three new
>    features, bitmap as a new datatype, a new event condition
>    BecomesEqualTo and LFB properties.
> 
> 
> 
> 
> The IETF Secretariat