Internet-Drafts | 7 Oct 2008 15:45
Picon
Favicon

I-D Action:draft-ietf-forces-model-16.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF.

	Title           : ForCES Forwarding Element Model
	Author(s)       : J. Halpern, J. Hadi Salim
	Filename        : draft-ietf-forces-model-16.txt
	Pages           : 132
	Date            : 2008-10-07

This document defines the forwarding element (FE) model used in the
Forwarding and Control Element Separation (ForCES) protocol [2].  The
model represents 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.  This FE model is
intended to satisfy the model requirements specified in the ForCES
requirements document, RFC3654 [6].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-forces-model-16.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
(Continue reading)

The IESG | 13 Oct 2008 18:19
Picon
Favicon

Protocol Action: 'ForCES Forwarding Element Model' to Proposed Standard

The IESG has approved the following document:

- 'ForCES Forwarding Element Model '
   <draft-ietf-forces-model-16.txt> as a Proposed Standard

This document is the product of the Forwarding and Control Element 
Separation Working Group. 

The IESG contact persons are Ross Callon and David Ward.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-forces-model-16.txt

Technical Summary

   This document defines the forwarding element (FE) model used in the
   Forwarding and Control Element Separation (ForCES) protocol (see 
   draft-ietf-forces-protocol).  The model represents 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.  This FE model is intended to satisfy the model
   requirements specified in the ForCES requirements document, RFC3654.

Working Group Summary

   Good working group consensus. 

(Continue reading)

Internet-Drafts | 30 Oct 2008 16:15
Picon
Favicon

I-D Action:draft-ietf-forces-protocol-18.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF.

	Title           : ForCES Protocol Specification
	Author(s)       : L. Dong, et al.
	Filename        : draft-ietf-forces-protocol-18.txt
	Pages           : 124
	Date            : 2008-10-30

This document specifies the Forwarding and Control Element Separation
(ForCES) protocol.  ForCES protocol is used for communications
between Control Elements(CEs) and Forwarding Elements (FEs) in a
ForCES Network Element (ForCES NE).  This specification is intended
to meet the ForCES protocol requirements defined in RFC3654.  Besides
the ForCES protocol, this specification also defines the requirements
for the Transport Mapping Layer (TML).Authors

The participants in the ForCES Protocol Team, primary co-authors and
co-editors, of this protocol specification, are:

Ligang Dong (Zhejiang Gongshang University), Avri Doria (Lulea
University of Technology), Ram Gopal (Nokia), Robert Haas (IBM),
Jamal Hadi Salim (Znyx), Hormuzd M Khosravi (Intel), and Weiming Wang
(Zhejiang Gongshang University).  Special acknowledgement goes to
Joel Halpern who has done extensive editing in support of congruence
between the model and this protocol specification.  Without his
participation and persistence, this specification might never have
been completed.

A URL for this Internet-Draft is:
(Continue reading)


Gmane