1. Weiming Wang (wmwang@mail.zjgsu.edu.cn)wmwang@mail.zjgsu.edu.cn Institute of Networks and Communication Engineering Zhejiang Gongshang University, P. R. China For 17th CJK-NGN meeting, Sanya, Nov 16, 2009 Progress in ForCES Technology

2. Content Introduction to ForCES Progress in IETF ForCES Working Group Progress in Zhejiang Gongshang Univ. (ZJGSU) Demo of ForCES-based Router Prototype ForCES and NGN

3. Introduction to ForCES

4. ForCES Architecture ForCES - Forwarding and Control Element Separation This framework was proposed in 2000 ， and the IETF ForCES working group was established in 2001. RFC3746: “ForCES Framework” defines –CE ： Control Element –FE ： Forwarding Element CE may be required to control hundreds of FEs

5. ForCES Architecture - FE –ForCES Protocol To provide a universal standardized control interface for FEs –LFB – Logical Functional Block e.g., Classifier LFB, IPv4 LPF LFB, IPv6 LPF LFB, Scheduler LFB Description: –in XML –Attributes, Capabilities, Event, Statistics –Datapath Can configure dynamically LFB topology for supporting various over IP services FE Model LFB1 ForCES Protocol Stack Attributes LFBn Attributes... Datapath FE CE ForCES Protocol

6. ForCES Architecture - CE IETF ForCES WG has not yet tried to define the CE model. The following CE structure is one of the possible models Element Abstraction Layer Operations APIs Services APIs Functional APIs Classification API Traffic Mgmt API IPv4 API Applications OSPF, RIPCOPS, CLI, SNMPOther Applications Control Plane Application Space ForCES Protocol Interface System Abstraction Layer Packet Handle r API Interfaces API MPLS API Diffserv API

7. Progress in IETF ForCES Working Group http://www.ietf.org/dyn/wg/charter/forces-charter.html http://www.ietf.org/dyn/wg/charter/forces-charter.html

8. Completed Protocols –RFC 3654 (Informational) – Requirements for Separation of IP Control and Forwarding –RFC 3746 (Informational) – Forwarding and Control Element Separation (ForCES) Framework –draft-ietf-forces-protocol-22.txt - ForCES Protocol Specification –draft-ietf-forces-model-16.txt - ForCES Forwarding Element Model –draft-ietf-forces-mib-10.txt - ForCES MIB –The last 3 documents are now in RFC ed. Queue and will be published soon

9. Drafts under Processing ContentsDocumentsStatus ForCES TML (Transport Mapping Layer) draft-ietf-forces-tcptml-04.txt draft-ietf-forces-tmlsp-01.txt draft-ietf-forces-sctptml-06.txt SCTP TML is now under IESG evaluation by IETF ForCES LFB Lib draft-ietf-forces-lfb-lib-00.txt Working group draft

10. ContentsDocumentsStatus ForCES Applicability draft-ietf-forces-applicability-07.txt Working group draft FE Intra-NE Topology Discovery draft-ietf-forces-discovery-02.txt ForCES Implementation and Interoperability draft-ietf-forces-implementation-report- 00.txt draft-ietf-forces-interoperability-04.txt Auxiliary Drafts

11. Interoperability Test of ForCES Protocol In July 2009, ZJGSU, Univ. of Patras, and NTT Corp. successfully carried out local and remote interoperability test of the ForCES protocol.

12. Dissector for ForCES Protocol ZJGSU and Jamal Hadi Salim (Mojatatu Networks) have implemented the dissector for the ForCES protocol used in Ethereal and Tcpdump, individually.

13. Progress in Zhejiang Gongshang Univ. (ZJGSU)

14. Research Process In 2003, a ForCES research Team was established in ZJGSU and a GRMP protocol was designed. – In 2005, GRMP was accepted by IETF as one candidate of the ForCES protocol. Since 2003, join the design of several important IETF ForCES drafts. Since 2006, have implemented a ForCES-based router prototype on the platform of Intel IXP2400/2851 NP. –Developed a ForCES protocol middleware, UOM( User Operating Management tool) and relative software that can be used for developing ForCES devices by third party.

15. Important protocols and documents Jointly produced: ForCES Protocol ForCES LFB Lib ForCES TML Implementation and Interoperability Report

16. Have developed software tools for ForCES applications Include: –ForCES Middleware and related SDK –User Operation Management (UOM) System for ForCES architecture –Other supporting softwares, e.g., Adapter Layer Software Tools for Testing –Dissector, generator, etc Application Layer Software, for routing, SNMP, multicast, VPN, firewall etc., The tools can greatly reduce the development expenses when vendors try to apply ForCES technology for various network equipments like routers, firewalls, VPN, base-station, etc

17. ForCES Middleware in ForCES System provide the operation APIs that hide the complex details of the ForCES protocol

18. ForCES Middleware SDK

19. Middleware Implementation Environment Operation system: Linux/vxWorks Language: C Compiler: gcc

20. UOM in ForCES System

21. UOM Graphic Interface Overview 1 Main Manu area FE tree Display area Component Operation area

22. UOM Graphic Interface Overview 2 LFB topology Display

23. Demo of ForCES-based Router Prototype

24. Developed based on ForCES middleware and UOM Physical architecture CE ： PC FE ： PC + Intel IXDP2401

26. ForCES Router OSPF Test Generates the routing entries: 200.xxx.xxx.xxx

27. Dynamical Configuration of ForCES LFB datapath Build the connection between DSCPClassfier LFB and other LFBs Choose LFB ports for connection

28. Demo Vedio Clips

29. ForCES and NGN

30. NGN may aim to construct a highly operable, maintainable, and manageable networks. –ForCES fine-grained LFBs may provide high operability and manageability of network devices for ISPs as well as vendors –ForCES dynamic configuration of LFB topology may provide ISPs very high operability to deploy brand-new services –ForCES Standardization process may provide opportunities for vendors to develop modular network devices rather than whole network device systems

31. ForCES and NGN

32. Researches supported by: The National Natural Science Foundation of China under Grant No.60603072 The National High Technology Development 863 Program of China under Grant No. 2007AA01Z201, 2008AA01A323, Zhejiang Provincial NSF China No. Z106829, Y106747, Y1080078, Zhejiang Sci & Tech Project No. 2008C21093.

33. Thanks!