Why Are We Here? The combination of ownership diversity and - - PowerPoint PPT Presentation

▶
why are we here
SMART_READER_LITE
LIVE PREVIEW

Why Are We Here? The combination of ownership diversity and - - PowerPoint PPT Presentation

Sep 07, 2022 561 likes •715 views

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

slide-1
SLIDE 1

GIBSON: Global IP-Based Service-Oriented Network

Ping Pan, Tom Nolle

S eptember 2006, Oslo Meeting

slide-2
SLIDE 2

2

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
slide-3
SLIDE 3

3

Metro Network Metro Network Core Network Ethernet MPLS Tunnel Optical A B C D

GIBSON Architecture and Operation Overview

IPsphere SMS Business Services

SMS Interface

Pseudowire Segment Pseudowire Segment Pseudowire Segment User Flow Us Flo

Policy Routing

er w

Mapping / Aggregation

GIBSON Pseudowire

Application Stream

slide-4
SLIDE 4

4

User 1 Packet Tunnel Pseudowire for User Flow 2 Pseudowire for User Flow 1 User 2

PW Label Control Word L1 / L2 / IP Header Application Header Data Payload L1 / L2 / IP Header Application Header Data Payload PW Label Control Word L1 / L2 / IP Header Application Header Data Payload L1 / L2 / IP Header Application Header Data Payload

Today’s Pseudowire Definition:

  • Encapsulate based on L1/L2 and IP headers
  • Emulate low layer services (OAM etc.)

GIBSON Pseudowire Definition:

  • Encapsulate based on application headers
  • Emulate high layer services (rate adaptation etc.)

A Review of Pseudowire

slide-5
SLIDE 5

5

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

slide-6
SLIDE 6

6

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

slide-7
SLIDE 7

7

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

slide-8
SLIDE 8

8

SMS Provider #1

GIBSON Endpoint A GIBSON Endpoint B Route Server E

SMS Provider #2

GIBSON Endpoint C Route Server F

SMS Provider #3

GIBSON Endpoint D Route Server G

Business Peering and Routing

GIBSON Pseudowire User Flow

GIBSON Policy Routing

slide-9
SLIDE 9

9 Service access device Service access device

Gibson Endpoint

Non-Gibson Endpoint

Gibson Endpoint Gibson Endpoint Gibson Endpoint

Interfaces in GIBSON

S1 S2 S3 S4 S5

Transport Tunnels Pseudowires within GIBSON-enabled network Data flows in best-effort IP networks

Access: lightweight signaling Aggregation (Pseudowire routing) Pseudowire Termination (Meshed VPN)

slide-10
SLIDE 10

10

SMS

IMS Control

Network 1

IMS Control

Network 3 Network 2 Media Flow SMS SMS GIBSON Endpoint GIBSON Endpoint GIBSON Endpoint

  • 1. tunnel setup
  • 1. tunnel setup
  • 1. tunnel setup
  • 3. populate IMS
  • 3. populate IMS
  • 4. Negotiating with resource awareness
  • 2. route exchange
  • 2. route exchange

GIBSON: IMS User Case

slide-11
SLIDE 11

11

SMS

IMS Control

Network 1

IMS Control

Network 3 Network 2 Media Flow SMS SMS GIBSON Endpoint GIBSON Endpoint GIBSON Endpoint

  • 5. Download session data
  • 5. Download session data
  • 6. Policy routing
  • 6. Policy routing
  • 7. Trigger PW setup
  • 7. Trigger PW setup
  • 8. Routing updates

GIBSON: IMS User Case (cont. 1)

slide-12
SLIDE 12

12

SMS

IMS Control

Network 1

IMS Control

Network 3 Network 2 Media Flow SMS SMS GIBSON Endpoint GIBSON Endpoint GIBSON Endpoint

  • 9. PW Setup
  • 10. PW Routing
  • 9. PW Setup
  • 11. Data aggregation, grouping and mapping

GIBSON: IMS User Case (cont. 2)

slide-13
SLIDE 13

13

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
slide-14
SLIDE 14

14

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