40 likes | 265 Views
ForCES: Forwarding and Control Element Separation Working Group. IETF 59 0900-1130 March 2, 2004. ForCES Agenda, IETF 59. 0900-0915 WG Status & Agenda Bash – Chairs
E N D
ForCES: Forwarding and Control Element Separation Working Group IETF 59 0900-1130 March 2, 2004
ForCES Agenda, IETF 59 0900-0915 WG Status & Agenda Bash – Chairs 0915-0955 Transparent Inter Process Communication Protocol – Jon Maloyhttp://www.ietf.org/internet-drafts/draft-maloy-tipc-00.txt 0955-1015 A Testbed for GRMP Protocol – Dr. Ligang Donghttp://www.ietf.org/internet-drafts/draft-wang-forces-grmp-01.txt 1015-1035 ForCES FE Model – Steven Blake http://www.ietf.org/internet-drafts/draft-ietf-forces-model-02.txt
ForCES WG Status, March 2004 Requirements: In RFC Editor’s queue RFC 3654 issued • Congratulations! Framework: Feedback from IESG In RFC Editor’s queue • Numerous small changes due to IESG & WG feedback • Re-last called & passed • Reviewed & approved by IESG for publication as an RFC Charter: Needs milestone update – new proposed dates: • Model WG LC: Aug’04 • Controlled objects -00: Jun’04 • Controlled objects WG LC: Nov’04 • Protocol selection -00: Jun’04 • Protocol selection WG LC: Mar’05 • Applicability statement WG LC: Mar’05
ForCES WG Status, March 2004 Model: Accepted as WG draft New version -02 uploaded • First (mostly) complete version • Needs WG review • Large document (> 100 pages) – should we split it? Protocol: Three candidates Evaluation doc done, merge being considered • FACT, Netlink2, GRMP (also TIPC transport proposed) • Protocol evaluation doc complete, all three protocols largely satisfy requirements • Design team formed to examine if a merge is feasible, will report out on March 20, 2004 Applicability Statement: On hold On hold • Played key role as “anti-requirements” at start of WG. • Next step is to explain how/where protocols are used, will be done once protocol selected & details nailed down. • In between those two points so staying on hold.