weiming wang ([email protected])[email protected] institute of networks and...
TRANSCRIPT
Weiming Wang ([email protected])Institute of Networks and Communication Engineering
Zhejiang Gongshang University, P. R. ChinaFor 17th CJK-NGN meeting, Sanya, Nov 16, 2009
Progress in ForCES Technology
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
Introduction to ForCES
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
ForCES NE
CE1 CE2
FE2 FE1
Fp
Fif
Fr CE Manager
FE Manager
Fif
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
AttributesAttributes
LFBn
AttributesAttributes
... Datapath
FE
CEForCES Protocol
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
ElementAbstraction
Layer
Operations A
PIs
Services APIs
Functional APIs
ClassificationAPI
Traffic MgmtAPI
IPv4API
ApplicationsOSPF, RIP COPS, CLI, SNMP Other Applications
Control PlaneApplication Space
ForCES Protocol Interface
System Abstraction
Layer
Packet Handle
rAPI
InterfacesAPI
MPLSAPI
DiffservAPI
Progress in IETF ForCES Working Group
http://www.ietf.org/dyn/wg/charter/forces-charter.html
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
Drafts under Processing
Contents Documents Status
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
Contents Documents Status
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.txtdraft-ietf-forces-interoperability-04.txt
Auxiliary Drafts
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.
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.
Progress in Zhejiang Gongshang Univ. (ZJGSU)
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.
Important protocols and documents Jointly produced:
• ForCES Protocol
• ForCES LFB Lib
• ForCES TML
• Implementation and Interoperability Report
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
CE
User Operation Manager(UOM)
Routi ng（OSPF、RI P,
etc. )SNMP QoS
Application LayerOthers Appl i -cation
Abstract Adapter Layer
Adaptor for Interface
Management
Adapter for IP Routing
Adapter for UOM
FE
LFB Resources
LFB Resource Abstract Layer
LFB Resources Registration
……
ForCES Protocol
ForCES Middleware
ForCES Middleware
ForCES Middleware in ForCES System
LFB resources（LFB instances）
OSPF
SNMP
DSCP
Application Layer
Others Appl i -cation
ForCES
CE
FE
RIPUser Operation Manager(UOM)
Abstract adapter for Appl i cation Layer
LFB resources abstract layer
TML Middleware
ForCES Protocol Middleware
TML Middleware
ForCES Protocol Middleware
• provide the operation APIs that hide the complex details of the ForCES protocol
ForCES Middleware SDK
app
Makefile
LFBs
LFBsRegister
include
xml
srcinclude
libs
adapters
ce
fe
cefe
suported_lfbssysapp.c
Makefile
suported_lfbssysapp.c
Makefilesysapp.cnetcom_forces_sdk
app
Makefile
LFBs
LFBsRegister
include
bin (including ForCES dissector etc.)
xml
srcinclude
libs
adapters
ce
fe
cefe
suported_lfbssysapp.c
Makefile
suported_lfbssysapp.c
Makefilesysapp.cnetcom_forces_sdk
doc (development documents)
Middleware Implementation Environment
• Operation system: Linux/vxWorks• Language: C• Compiler: gcc
UOM in ForCES System
LFB resources（LFB instances）
OSPF
SNMP
DSCP
Application Layer
Others Appl i -cation
ForCES
CE
FE
RIP
Abstract adapter for Appl i cation Layer
LFB resources abstract layer
TML Middleware
ForCES Protocol Middleware
TML Middleware
ForCES Protocol Middleware
User OperationManager(UOM)
UOM Graphic Interface Overview 1
Main Manu area
FE tree Display area
Component Operation area
UOM Graphic Interface Overview 2
LFB topology Display
Demo of ForCES-based Router Prototype
Developed based on ForCES middleware and UOM
Physical architecture CE ： PC
FE ： PC + Intel IXDP2401
Internet
FE12(IXDP 2401)
Eth 192.168.0.12
P0P1P2P3
ForCES RouterForCES Protocol Channel
Eth 192.168.0.250
Routing protocol(RIP\OSPF) packets from SmartBits
IP packets for test from SmartBits
Routing protocol(RIP\OSPF) packets from ForTER
IP: 15.2.0.13MAC: 000001000002
IP: 16.2.0.14MAC: 000001000003
SmartBits 600LAN3321A
SmartBits 600LAN3101B
P1
P1
P2
P2P3P4P5P6
FE11(IXDP 2401)
Eth 192.168.0.11
P0P1P2P3
Switch
P1 P2 P3 P4 P5P0 P15
FE10(PC)
FE2(PC)
……
P0P1P0P1
Ipv4 Ipv4
to CE
Form CE
EtherPort(ingress)
Scheduler
EtherDecap
Ether IPv4 Validator
IPv4UcastLPM
IPv4Nexthop
Applicator
QueueMansger
EtherPort(egress)
Meta Classifier1
RedirectSink
Meta Classifier2
RedirectTap
Ipv4 Ether
Default
Ipv4Ether Encap
EtherIpv4 Ipv4
to CE
Form CE
EtherPort(ingress)
Scheduler
EtherDecap
Ether IPv4 Validator
IPv4UcastLPM
IPv4Nexthop
Applicator
QueueMansger
EtherPort(egress)
Meta Classifier1
RedirectSink
Meta Classifier2
RedirectTap
Ipv4 Ether
Default
Ipv4Ether Encap
Ether
FE1(PC)
P0P1
IP: 16.2.0.1IP: 15.2.0.1
CELinux
（Web Server、Routing Server）
IE
ForCES Router OSPF Test
OSPF Network Topology Simulated By SmartBits
Smartbits NetworkTester
SMB1-1 SMB1-2
ForCES Router
FE7 FEn……17.7.0.1
17.7.0.14
CE
Generates the routing entries:
200.xxx.xxx.xxx
Dynamical Configuration of ForCES LFB datapath
Build the connection between DSCPClassfier LFB and other LFBs
Choose LFB ports for connection
Demo Vedio Clips
ForCES and NGN
ForCES and NGN
• 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
ForCES and NGN
ForCES Protocol
Switch
P1 P2 P3 P4 P5P0 Pn
P0
CE Linux （Web Server、Routing Server）
FE1
P0P1P2P3
Ipv4 Ipv4
to CE
Form CE
EtherPort(ingress)
Scheduler
EtherDecap
Ether IPv4 Validator
IPv4UcastLPM
IPv4Nexthop
Applicator
QueueMansger
EtherPort(egress)
Meta
Classifier1RedirectSink
Meta Classifier2
RedirectTap
Ipv4 Ether
Default
Ipv4Ether Encap
Ether
P0
FEn
P0P1P2P3
Ipv4 Ipv4
to CE
Form CE
EtherPort(ingress)
Scheduler
EtherDecap
Ether IPv4 Validator
IPv4UcastLPM
IPv4Nexthop
Applicator
QueueMansger
EtherPort(egress)
Meta
Classifier1RedirectSink
Meta Classifier2
RedirectTap
Ipv4 Ether
Default
Ipv4Ether Encap
Ether
ForCES-based Network Devices
Dynamical Configuration of ForCES LFBs
ISP Services Layer
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.
Thanks!