Transcript ForCES and NGN

Progress in ForCES Technology
Weiming Wang ([email protected])
Institute of Networks and Communication Engineering
Zhejiang Gongshang University, P. R. China
For 17th CJK-NGN meeting, Sanya, Nov 16, 2009
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 NE
Fr
CE Manager
CE1
CE2
Fp
FE Manager
FE1
FE2
Fif
Fif
• 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 Architecture - FE
• FE Model
CE
ForCES Protocol
FE
ForCES Protocol Stack
LFB1
Attributes
Datapath
...
LFBn
Attributes
– 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
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
Applications
OSPF, RIP
COPS, CLI, SNMP
Other Applications
Operations APIs
Services APIs
Interfaces
API
Packet
Handle
r
API
IPv4
API
MPLS
API
System
Abstraction
Layer
Diffserv
API
Classification
API
Traffic Mgmt
API
Functional APIs
ForCES Protocol Interface
Control Plane
Application Space
Element
Abstraction
Layer
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
draft-ietf-forces-tcptml-04.txt
draft-ietf-forces-tmlsp-01.txt
(Transport
Mapping Layer) draft-ietf-forces-sctptml-06.txt
SCTP TML is
now under IESG
evaluation by
IETF
ForCES LFB
Lib
Working group
draft
draft-ietf-forces-lfb-lib-00.txt
Auxiliary Drafts
Contents
Documents
ForCES
Applicability
draft-ietf-forces-applicability-07.txt
FE Intra-NE
Topology
Discovery
draft-ietf-forces-discovery-02.txt
ForCES
Implementation
and
Interoperability
draft-ietf-forces-implementationreport-00.txt
draft-ietf-forces-interoperability04.txt
Status
Working
group
draft
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
User
Oper at i on
Manager
( UOM)
CE
Adapter
for UOM
Application Layer
Rout i ng
（ OSPF（ RI P,
et c. )
Adapter for
IP Routing
SNMP
Adaptor for
Interface
Management
QoS
Ot her s
Appl i cat i on
……
Abstract Adapter Layer
ForCES Middleware
ForCES Protocol
ForCES Middleware
FE
LFB Resource Abstract Layer
LFB Resources Registration
LFB Resources
ForCES Middleware in ForCES System
• provide the operation
APIs that hide the
complex details of the
ForCES protocol
Application Layer
User Oper at i on
Manager ( UOM)
CE
RI P
SNMP
OSPF
DSCP
Ot her s
Appl i cat i on
Abst r act adapt er f or Appl i cat i on Layer
For CES Pr ot ocol Mi ddl ewar e
TML Mi ddl ewar e
ForC
TML Mi ddl ewar e
For CES Pr ot ocol Mi ddl ewar e
FE
LFB resources abstract layer
LFB resources（LFB instances）
ForCES Middleware SDK
libs
app
ce
cefe
fe
netcom_forces_sdk
Makefile
suported_lfbs
sysapp.c
Makefile
suported_lfbs
sysapp.c
Makefile
sysapp.c
adapters
LFBs
LFBsRegister
xml
src
include
include
bin (including ForCES dissector etc.)
doc (development documents)
Middleware Implementation Environment
• Operation system: Linux/vxWorks
• Language: C
• Compiler: gcc
UOM in ForCES System
Application Layer
User Oper at i on
Manager ( UOM)
CE
RI P
SNMP
OSPF
DSCP
Ot her s
Appl i cat i on
Abst r act adapt er f or Appl i cat i on Layer
For CES Pr ot ocol Mi ddl ewar e
TML Mi ddl ewar e
ForCES
TML Mi ddl ewar e
For CES Pr ot ocol Mi ddl ewar e
FE
LFB resources abstract layer
LFB resources（LFB instances）
UOM Graphic Interface Overview 1
Main Manu area
Component Operation area
FE tree Display 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
IE
Internet
ForCES Router
Linux
（Web Server、Routing Server）
CE
Eth 192.168.0.250
ForCES Protocol Channel
Eth 192.168.0.12
Eth 192.168.0.11
Meta
Classifier2
Form CE
P0
P1
Ipv4
IPv4
Validator
Ipv4
IPv4
UcastLPM
IPv4
Nexthop
Applicator
Ipv4
Ipv4
Ether
Encap
Ether
Queue
Mansger
Ether
EtherPort
(egress)
EtherPort
(ingress)
Ether
Ipv4
Ether
Decap
IPv4
Validator
Ipv4
Scheduler
Ip
mca v4
st
IPv4
UcastLPM
Ipv4
IPv4
Nexthop
Applicator
Ipv4
Ether
Encap
Ether
Queue
Mansger
P0
P3
Meta
Classifier1
Default
P2
RedirectSink
P1
FE12
(IXDP 2401)
to CE
P3
P0
pk
p
Exc
p
Exc
FE11
(IXDP 2401)
ts
pk
ts
Ether
Decap
cp
Ex kts
p
P0 P1
(PC)
Ether
cp
Ex kts
p
P1
…… FE10
FE2
(PC)
FE1
(PC)
EtherPort
(ingress)
Meta
Classifier2
RedirectTap
Scheduler
Ip
mca v4
st
Ip
uca v4
st
RedirectTap
Ip
uca v4
st
Form CE
Meta
Classifier1
Default
P2
IP: 15.2.0.1
P0 P1 P2 P3 P4 P5
Switch
Routing protocol(RIP\OSPF) packets from ForTER
IP packets for test from SmartBits
IP: 15.2.0.13
MAC: 000001000002
to CE
P1
IP: 16.2.0.1
P15
Routing protocol(RIP\OSPF) packets from SmartBits
RedirectSink
P1
P2
IP: 16.2.0.14
MAC: 000001000003
SmartBits 600
LAN3321A
SmartBits 600
LAN3101B
P6 P5 P4 P3 P2 P1
P0
Ether
EtherPort
(egress)
ForCES Router OSPF Test
ForCES Router
CE
FE7
……
FEn
Generates the
routing entries:
17.7.0.1
17.7.0.14
SMB1-1
SMB1-2
200.xxx.xxx.xxx
OSPF Network Topology
Simulated By SmartBits
Smartbits
NetworkTester
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
ISP Services Layer
Dynamical Configuration of
ForCES LFBs
Linux
CE（Web Server、Routing
Server）
ForCES Protocol
Meta
Classifier2
Form CE
Ipv4
IPv4
Validator
Ipv4
IPv4
UcastLPM
P2
Ipv4
Ether
Encap
Ether
Queue
Mansger
Ex
cp
Meta
Classifier1
P3
IPv4
Nexthop
Applicator
Ether
EtherPort
(egress)
EtherPort
(ingress)
Ether
Default
Ether
Decap
Ipv4
IPv4
Validator
Ipv4
IPv4
UcastLPM
cp
Ex kts
p
cp
Ex kts
p
FE1
Ipv4
RedirectSink
P1 P0
P0 P1 P2 P3 P4 P5
Switch
FEn
to CE
P0
Meta
Classifier1
P3
P2
Ipv4
IPv4
Nexthop
Applicator
Ipv4
Ether
Encap
Ether
Queue
Mansger
Ether
EtherPort
(egress)
pk
ts
Ether
Decap
Scheduler
Ip
mc v4
ast
Ex
cp
Ether
pk
ts
EtherPort
(ingress)
Meta
Classifier2
RedirectTap
Scheduler
Ip
mc v4
ast
Ip
uc v4
as
t
RedirectTap
Ip
uc v4
as
t
Form CE
Default
RedirectSink
P1 P0
to CE
P0
Pn
ForCES-based Network Devices
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!