30 likes | 144 Views
ForCES: Forwarding and Control Element Separation Working Group. IETF 58 1300-1500 November 10, 2003. ForCES Agenda, IETF 58. 1300-1305 WG Status & Agenda Bash – Chairs
E N D
ForCES: Forwarding and Control Element Separation Working Group IETF 58 1300-1500 November 10, 2003
ForCES Agenda, IETF 58 1300-1305 WG Status & Agenda Bash – Chairs 1305-1315 A proposed vocabulary and conceptual model for discussing metadata within ForCES - Alan DeKokhttp://www.ietf.org/internet-drafts/draft-dekok-forces-metadata-00.txt 1315-1340 ForCES Model Update - Steven Blakehttp://www.ietf.org/internet-drafts/draft-ietf-forces-model-01.txtW 1340-1400 General Router Management Protocol (GRMP) Version 1 - Weiming Wanghttp://www.ietf.org/internet-drafts/draft-wang-forces-grmp-00.txt 1400-1405 Topology representation for ForCES FE model - Weiming Wanghttp://www.ietf.org/internet-drafts/draft-wang-forces-model-topology-00.txt 1405-1425 Netlink2 protocol - Steven Blakehttp://www.ietf.org/internet-drafts/draft-jhsrha-forces-netlink2-02.txt 1425-1445 Status update for FACT protocol - Ram Gopal http://www.ietf.org/internet-drafts/draft-gopal-forces-fact-05.txt 1445-1500 15 min - Linux traffic control extensions & the forces model - Jamal Hadi Salim(no draft available)
ForCES WG Status Requirements: In AD/IESG review state In IESG Editor’s queue • Some text changes discussed on list that will be made during authors’ 48 hours period. See website for details. Framework: In AD/IESG review state Feedback received from IESG • Authorization needs to be explicitly called out post-authentication • Security architecture when FE proxy used needs to be elaborated • See mailing list for details. Model: Individual drafts submitted Accepted as WG draft • Model draft revised to version -01 • Still more work to be done Protocol: Two candidates Three candidates, protocol evaluation starting • FACT, Netlink2, GRMP • Protocol evaluation draft started and accepted as WG draft • November 21 deadline for authors to contribute to evaluation draft 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 selection progresses further. • In between those two points so staying on hold.