ForCES: Forwarding and Control Element Separation

Working Group

David Putzolu (david.putzolu@intel.com) Patrick Droz (dro@zurich.ibm.com)

IETF 61

1300-1500

November 8, 2004

ForCES Meeting, IETF 61• Blue Sheets• Note Takers

–Volunteers needed–Email notes to chairs

• Jabber Taker–Group/Room: forces–Server: ietf.xmpp.org

ForCES Agenda, IETF 615 min WG status & Agenda Bash - chairs30 min ForCES Protocol Draft Status & Changes - Jamal

Hadi Salim - draft-forces-protocol-01.txt20 min Options for LFB-level multicast and related issues –

Robert Haas15 min IP TML Proposal – Alex Audu -

draft-audu-forces-iptml-00.txt20 min TIPC Transport Mapping Layer Proposal – Jon

Maloy - draft-maloy-tipc-01.txt5 min ForCES IP TML Proposal – Furquan Ansari

draft-khosravi-forces-tcptml-00.txt15 min ForCES Element Discovery Proposal – Furquan

Ansari - draft-ansari-forces-discovery-01.txt10 min Flexinet EU ForCES Protocol Implementation

Experience - Robert Haas

ForCES WG Status, Nov-2004Prior Art: RFC 3549 issuedRequirements: RFC 3654 issuedFramework: RFC 3746 issued

Model: Draft-03 published, Draft-04 waiting for protocol• Protocol & model teams working together to harmonize drafts

Protocol: Working group document selected• draft-forces-protocol-01.txt• Based on merged proposal by design team consisting of authors of original three

candidates• Expect another revision before last call

TML Proposals: Three proposals to review – pick one or more• Protocol draft covers semantics. TML shows how to carry them in different

environments (intra-cluster, single L2 hop, regular IP network)• draft-audu-forces-iptml-00.txt• draft-khosravi-tcptml-00.txt• draft-maloy-tipc-01.txt

Applicability Statement: Still on hold• Pending model & protocol finalization

New work: ForCES Intra-NE Topology Discovery• Proposal for how FE/CE discover each other• Group to determine if should be included in charter