GIBSON: Global IP-Based Service-Oriented Network Ping Pan, Tom Nolle S eptember 2006, Oslo Meeting
Why Are We Here? • The combination of ownership diversity and technology diversity is reflected in a more complex set of management interfaces to control infrastructure: Access/ metro and backbone networks may belong to different carriers or • business entities Different technologies among providers (Metro/ Access and Core networks) • Different service “ values” : per-flow for video streams vs. per-aggregation • group for voice sessions vs. best-effort Regulatory issues such as intercept/ surveillance which may result in routing • and aggregation decisions • Difficult to control user traffic Core networks have no ability or incentive to provide special treatment on • import ant user flows End-user congestion and flow control (e,g, TCP) may not be sufficient • Routing mechanisms like OS PF or IS -IS may not be good enough when it comes • to business-based route selection • Providers need to create more services with manageable operation cost 2
GIBSON Architecture and Operation Overview Business Services IPsphere SMS Mapping / Aggregation Policy Routing SMS Interface Core Metro Metro Network Network Network A B C D Application Stream Ethernet MPLS Tunnel Optical Pseudowire Pseudowire Pseudowire Us er User Segment Segment Segment Flo w Flow GIBSON Pseudowire 3
A Review of Pseudowire Today’s Pseudowire Definition: • Encapsulate based on L1/L2 and IP headers • Emulate low layer services (OAM etc.) L1 / L2 / IP Application Data Control L1 / L2 / IP Application Data PW Label Header Header Payload Word Header Header Payload User 1 Pseudowire for User Flow 1 User 2 Pseudowire for User Flow 2 Packet Tunnel L1 / L2 / IP Application Data Control L1 / L2 / IP Application Data Header Header Payload PW Label Word Header Header Payload GIBSON Pseudowire Definition: • Encapsulate based on application headers • Emulate high layer services (rate adaptation etc.) 4
Pseudowire provides the following today… • Transport Agnostic Pseudowires can support IP and Ethernet, and even optical cross-connections • • IP-friendly Pseudowires are provisioned and controlled via IP control plane • • Inter-network capable PWE3 multi-hop [MHOP] and switching [S WITCH] techniques enable the providers to • provision Pseudowires over multiple intra-domain or inter-domain networks. • VPN capable Pseudowire has been extended in IETF to create a nested topology for VPN applications, • which include VPLS and VPWS . • SLA capable Pseudowire technique can provide QoS , protection and restoration and congestion • control functionality at per-flow basis. • Flow type agnost ic Pseudowires can encapsulate any type of data flows. As defined today, Pseudowires can • encapsulate Layer-1 flows in S ONET/ S DH format (the technique is known as Circuit Emulation), Layer-2 flows such as ATM, Frame Relay, PPP and Ethernet, and IP All in deployment today 5
The Importance of Application-Awareness • New data services may require per-application-flow management and control: Application flow examples • • RTP for session-based applications such as VoD and VoIP • MPEG for multimedia applications Application flows need to be managed inside the network • • New applications bring an entirely different set of service requirements: Examples: • • Packet video: tolerate packet out-of-order delivery • Packet voice: tolerate packet drop, but not delay • “ S eamless Convergence ” offerings: user flows can adapt to the change of link bandwidth, but maintain constant-bit-rate Traditional mechanisms (IEEE 802.1p or IP DiffS erv) are not adequate • to handle such applications. Map application flows into Pseudowires � Consistent e2e behavior 6
GIBSON Attributes • Application-awareness GIBS ON Pseudowires map and aggregate data flows from any layer • (i.e., layer 1 to 7) Aggregation method depends on applications: • One flow/ Pseudowire: high-bandwidth and long-duration VoD • streams Multiple flows/ Pseudowire: low-speed and short-lived VoIP • sessions • Business-driven routing At network border, GIBS ON pseudowires are switched based on • business-driven routing • SMS Interfacing GIBS ON pseudowires are provisioned as a result of S MS Administration, • S MS Parent, and S MS Child communication 7
GIBSON Policy Routing Business Peering and Routing SMS SMS SMS Provider #2 Provider #1 Provider #3 Route Server Route Server Route Server F E G User Flow GIBSON GIBSON GIBSON GIBSON Endpoint Endpoint Endpoint Endpoint A B C D GIBSON Pseudowire 8
Interfaces in GIBSON S3 (Pseudowire routing) S1 S2 Service Service Gibson Gibson Gibson access access Endpoint Endpoint Endpoint device device Access: lightweight signaling Aggregation S5 (Meshed VPN) Gibson S4 Endpoint Pseudowire Termination Transport Tunnels Pseudowires within GIBSON-enabled network Data flows in Non-Gibson best-effort IP networks Endpoint 9
GIBSON: IMS User Case 4. Negotiating with resource awareness IMS IMS Control Control 3. populate IMS 3. populate IMS SMS SMS SMS 2. route exchange 2. route exchange 1. tunnel setup 1. tunnel setup 1. tunnel setup GIBSON GIBSON GIBSON Endpoint Endpoint Endpoint Network 1 Network 2 Network 3 Media Flow 10
GIBSON: IMS User Case (cont. 1) IMS IMS Control Control 5. Download session data 5. Download session data SMS SMS SMS 6. Policy routing 6. Policy routing 8. Routing updates 7. Trigger PW setup 7. Trigger PW setup GIBSON GIBSON GIBSON Endpoint Endpoint Endpoint Network 1 Network 2 Network 3 Media Flow 11
GIBSON: IMS User Case (cont. 2) IMS IMS Control Control SMS SMS SMS 10. PW Routing 9. PW Setup 9. PW Setup GIBSON GIBSON GIBSON Endpoint Endpoint Endpoint Network 1 Network 2 Network 3 Media Flow 11. Data aggregation, grouping and mapping 12
Summary on GIBSON • Open interface for business service creation and provisioning • Operate in both intra-provider and inter-provider environment • Provide consistent edge-to-edge per-flow forwarding behavior • Flow type agnostics – capable of processing flows in any format • S upport for “ nesting” of Pseudowires to facilitate traffic management and virtual service creation • S upport for “ virtual segment s” that envelope multipoint service behavior created by capabilities like RFC 2547, to permit end-to-end multipoint delivery • Independent of underlying network transport tunneling mechanism • Applicable on all service devices, with less dependency on IP routing • Leverage and extend a proven and simple technology: Pseduowire 13
What’s Next… • Gather more feedback from service providers • Define and implement S MS interfaces • Investigate more on routing interfaces Routing updates, and scalability • Interface with PCE • • Investigate more on RACF interfaces How to deal with all those QoS policies? • • Apply GIBSON to other user cases Business access (leased line services) • FMC • • Working toward standardizing the GIBS ON concept in IPsphere 14
Recommend
More recommend
