[Fwd: I-D Action:draft-ietf-forces-model-11.txt]

"Joel M. Halpern" <joel@stevecrocker.com> Mon, 25 February 2008 21:07 UTC

Message-Id: <MON.25.FEB.2008.160710.0500.>
Date: Mon, 25 Feb 2008 16:07:10 -0500
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: [Fwd: I-D Action:draft-ietf-forces-model-11.txt]
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------090304000107010108000509"

Here is the revision to the ForCES model draft.  It addresses all
received comments to the best of my ability.
Once the Protocol document is also ready, I would ask the chairs to
deliver both documents to the AD for IETF last call.


PS: Did folks see the Juniper JCS 1200 announcement?

-------- Original Message --------
Subject: I-D Action:draft-ietf-forces-model-11.txt
Date: Mon, 25 Feb 2008 12:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
CC: forces@peach.ease.lsoft.com

A New Internet-Draft is available from the on-line Internet-Drafts
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, et al.
	Filename        : draft-ietf-forces-model-11.txt
	Pages           : 129
	Date            : 2008-02-25

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 [4].

A URL for this Internet-Draft is: