I-D Action:draft-ietf-forces-protocol-12.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-12.txt
	Pages           : 126
	Date            : 2007-11-18

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 messages, the specification also defines the
framework, the mechanisms, and the Transport Mapping Layer (TML)
requirements for ForCES protocol.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).

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

To remove yourself from the I-D Announcement list, send a message to

I-D Action:draft-ietf-forces-protocol-13.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-13.txt
	Pages           : 125
	Date            : 2007-12-04

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 messages, the specification also defines the
framework, the mechanisms, and the Transport Mapping Layer (TML)
requirements for ForCES protocol.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 whose 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.

Forces Applicability Statement

Hi,

As we get closer to completing the model and protocol drafts, I think  
we need to do a review of this informational draft that was alwasy  
intended to go to the IESG at the same time.
it can currently be found at: http://www.watersprings.org/pub/id/ 
draft-ietf-forces-applicability-05.txt

I am willing to do the update to this draft (including converting it  
to xml), but i think it would be good to have a review of it, before  
i do that.

thanks

a.

presentations posted

All,

I have posted the presentations.

1) Jamal: http://www3.ietf.org/proceedings/07dec/slides/forces-1.pdf

2) Joel on Model at:
http://www3.ietf.org/proceedings/07dec/slides/forces-0.pdf

3)Avri on Protocol at:
http://www3.ietf.org/proceedings/07dec/slides/forces-2.pdf

4)Kentaro on sctp at: 
http://www3.ietf.org/proceedings/07dec/slides/forces-3.pdf

5) Evangelos on implementation experience at:
http://www3.ietf.org/proceedings/07dec/slides/forces-4.pdf

6) Demo by Evengelos at:
http://www3.ietf.org/proceedings/07dec/slides/forces-5.pdf

cheers,
jamal

Preliminary minutes

Here are the preliminary minutes for the ForCES IETF 70 in Vancouver.
Many many thanks to Peter McCann <pete.mccann <at> motorola.com>
For helping out in taking the minutes.

I would like to post them on the IETF website by monday, so please stare
at the notes and correct any innacuracies.

cheers,
jamal

Preliminary

Chair: Jamal Hadi Salim <hadi <at> znyx.com> 

1) Chair (10 minutes)
     *) Administrivia
     *) Blue Sheets
     *) Jabber & Minute scribes appointment
     *) Agenda bashing
     *)	WG Status

2) Joel M. Halpern <jmh <at> joelhalpern.com> (15-20 minutes)
     ForCES Forwarding Element Model, Pre-requisite reading material:
     ftp://ftp.znyx.com/users/hadi/private/forces/draft-ietf-forces-model-09.txt

* Working on making things clearer with Jamal which resulted in
an updated model.

I-D Action:draft-ietf-forces-model-09.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, et al.
	Filename        : draft-ietf-forces-model-09.txt
	Pages           : 126
	Date            : 2007-12-21

This document defines the forwarding element (FE) model used in the
Forwarding and Control Element Separation (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 [2].

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 

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

From: <Internet-Drafts <at> ietf.org>
Subject: I-D Action:draft-ietf-forces-model-09.txt
Date: 2007-12-21 21:20:01 GMT

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, et al.
	Filename        : draft-ietf-forces-model-09.txt
	Pages           : 126
	Date            : 2007-12-21

This document defines the forwarding element (FE) model used in the
Forwarding and Control Element Separation (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

question about transaction operation in ForCES protocol draft!

Re: question about transaction operation in ForCES protocol draft!

On Sun, 2007-23-12 at 19:12 +0800, Chuanhuang Li wrote:
> Hi:
>     we are implementing the ForCES protocol,I have one question in the
> Transaction Protocol part.
>  
> in the draft:
>    1: TRCOMP is sent by the CE to signal the FE(s) that the
>    transaction they have COMMITed is now over.  This allows the FE(s)
> an
>    opportunity to clear state they may have kept around to perform a
>    rollback (if it became necessary). (page 22)
>    2: The FE MUST respond to the CE's EOT message.  (page 22)
>    If all participating FE(s) respond with a success indicator within
>    the expected time, then the CE MUST issue a TRCOMP operation to all
>    participating FEs.  An FE MUST NOT respond to a TRCOMP. (page 23)
>  
> question:
>    We assume that the transaction operation is occured between CE and
> one FE, 

Note: Transactional operation is used for the case where you have to
transfer state to _more than one_ FE and where such state has to be
consistent (eg adding a single route on more than one FE).

> if there is failure when FE executes the full transaction, and it
> tells the result to CE through sending COMMIT-RESPONSE message.
> Whether FE should clear state they have kept still after it received
> the TRCOMP message? 

It should wait for TRCOMP.

> or CE shouldn't send the TRCOMP message in this case,and FE will clear
> the information once there is error? 

This would be inconsistent. If you use transaction, then the state
machine says you have to wait for TRCOMP.

> I think the latter may be a better solution,but the draft hasn't
> explained it clearly.

If you have a single FE and dont want to incur the extra overhead of
transactional procedure, then dont use transacational messaging.

>  
>     Hope your answers!!

Hope above is helpful.

cheers,
jamal

Re: question about transaction operation in ForCES protocol draft!