1. ForCES: Forwarding and Control Element Separation Working Group IETF 57 1300-1500 July 13, 2003

2. Agenda 1300-1305 WG Status – Chairs 1305-1320 ForCES Framework response to IESG Feedback – Ram Gopal http://www.ietf.org/internet-drafts/draft-ietf-forces-framework-06.txt http://www.ietf.org/internet-drafts/draft-ietf-forces-framework-06.txt 1320-1340ForwArding and Control ElemenT protocol (FACT) – H. Khosravi http://www.ietf.org/internet-drafts/draft-gopal-forces-fact-04.txt http://www.ietf.org/internet-drafts/draft-gopal-forces-fact-04.txt 1340-1400Netlink2 as ForCES Protocol – Robert Haas http://www.ietf.org/internet-drafts/draft-jhsrha-forces-netlink2-01.txt http://www.ietf.org/internet-drafts/draft-jhsrha-forces-netlink2-01.txt 1400-1415ForCES Forwarding Element Functional Model – Joel Halpern http://www.ietf.org/internet-drafts/draft-yang-forces-model-02.txt http://www.ietf.org/internet-drafts/draft-yang-forces-model-02.txt 1415-1430XML/TIPC based ForCES protocol and ForCES Pre-association Phase Protocol – Jon Maloy http://www.ietf.org/internet-drafts/draft-nait-forces-xml-model-00.txt http://www.ietf.org/internet-drafts/draft-nait-forces-pap-00.txt http://www.ietf.org/internet-drafts/draft-nait-forces-xml-model-00.txt http://www.ietf.org/internet-drafts/draft-nait-forces-pap-00.txt 1430-1445ForCES FE Functional Model Elements – Zsolt Haraszti http://www.petri-meat.com/slblake/networking/drafts/draft-haraszti- forces-model-00.txt http://www.petri-meat.com/slblake/networking/drafts/draft-haraszti- forces-model-00.txt 1445-1500Demonstration of working prototype of XML/TIPC for ForCES – Jon Maloy

3. WG Status: Tour de ForCES Requirements: In AD/IESG review states. Language clarification: "ForCES MAY NOT impose strict reliability"  "ForCES MUST NOT be restricted to strict reliability“ Discussed and reviewed on mailing list AD suggested language clarification: “ForCES…FEs must allow asynchronous processing”  “The ForCES model must allow asynchronous processing” Framework: In AD/IESG review states. Language clarification: Addition of text to clarify that the model itself does not need to explain how to offload any specific functions. Update to fit requirements: Applied TCP-friendly transport protocol requirement to multihop case – single-hop/in-box may consider alternatives Model: Individual drafts submitted – charter due date passed Two new drafts submitted: draft-nait-forces-xml-model-00 and draft-harastzti-forces-model-00 Authors of draft-yang-forces-model-02 asking to become WG item Protocol: Two individual drafts submitted – charter due date passed draft-gopal-forces-fact-04 and draft-jfsrha-netlink2-01 Protocol selection process to begin once requirements passes IESG review