1 heidelberg, 14 - 15 october 1998 how can qos be guaranteed/managed in a multi-provider ip...

1Heidelberg, 14 - 15 October 1998

How can QoS be guaranteed/managed in a multi-provider IP environment

QUTE’98 WorkshopMichael Smirnov, GMD FOKUS

How can QoS be guaranteed/managed in a multi-provider IP

environment

Michael SmirnovGMD FOKUS

COST 263




COST 263: "Quality of Internet Services"

IETF: > 100 short-lived WGs in 5 areasCOST: WGs within a long-lived Action

IETF: lacks inter-group coordinationCOST: committed to co-ordination

IETF: hard to join with new work itemsCOST: easy to join with new work items




COST 263 MoU: R&D

QoS Engineering for the Internet

QoS Enhancements for the Internet protocol stack

QoS in Multicast

QoS in NG protocols QoS in Applications

Charging for Premium IP Services

Liaisons




About Guarantee ...

• Assurance - n, confidence ..., • belief and trust ..., • promise ...• Guarantee - n, promise or undertaking ... that certain conditions • agreed to in a transaction will be fulfilled

• A.S.Hornby, Ed., Oxford Dictionary, 1986




– Business usage: Virtual Enterprise?– Real-time communication over the

Internet?– IETF promises: IntServ, DiffServ, MPLS, ... – How in the multi-provider environment?– What’s coming next?

What are the promises?




Multi-provider issues

• NSF Internet: each hop is a provider

• Commercial Internet:– Peering– ISP Certification– Roaming– Shared trouble ticketing– Charging and accounting collaboration




Network Access Point

Peering Point

No congestion hereNo congestion here

Add BW on demandAdd BW on demand

Peering Rules




The only QoS guaranteed communication so far was always connection-oriented:

- always only one hop;- QoS set-up at root.

QoS assurance in a connectionless worldhas to repeat the QoS set-up step ateach hop: IntServ ~ characterisation point DiffServ ~ PHBs mapping

Connection oriented vs Connectionlessfrom the QoS assurance viewpoint




The Big Picture

QoSrouting

?

ISP

L3/L2Classif. Sched.

Capacity

QoSset-up

Policy

IntServ

DiffServ




End-to-end QoS request

Achieved QoS

Needed QoS

SrcDst

IntServ’s Characterisation Point




• The IntServ characterisation point is important in a multi-provider environment:– IntServ is not only RSVP– RSVP is complex (or too generic?).

• The DiffServ reflects the backbone´s needs only– the end-to-end QoS is questionable.

What is wrong with IntServ and DiffServ?




• DiffServ is simple but has no end-to-end guarantees: need for the top level control;

• IntServ guarantees end-to-end but is complex and needs admission controls;

• The combination (IIS+DS) seems to be OK, however it needs QoS routing support, and qosr has no progress

IntServ + DiffServ ?




VAIP

VAIP

Best Effort Internet

QOSR IP/FEC Tunnel

(Shortcut)

VAIP GW

VAIP GW

QoS InterworkingMore than 1

provider




IN and Internet

1 800 345...

codepoint behaviour

ServiceDBase

switch

Dst IP, TOS, ...

codepoints

behaviours

router

RoutingDBase

TOSDBase




IN and Internet Interworking

R R

R

Sw

SCP MG

SG

MC

MGSw

SCP SG

MC

Sw

SCP

MG




• The AN paradigm: networks programmable by applications:– are networks ready for this? (see e.g. IPv6

transition plan for an example);• The needed advances in SW development

are missing (component software), however ...

• attempts are numerous (...)

What is coming next: Active Networks?




• We should go back to a CO world:– ATM is there with the QoS guarantees;– AAL5´s overhead is minimal.

• Then the qosr is simply a shortcut management? (we do have solutions for IP and IP multicast over ATM with QoS!)

• IETF: ION, ISSLL - no integration, MPLS is a solution?

What is coming next: Shortcuts !




MPLS is a solution?

R

RR

RMPLS Trunk

RSVP signalling




• “The Internet has met its enemy and its name is QoS “ (B. Carpenter, J. Crowcroft)

• Integrational approach is needed– protocol co-design, – better integration of L3/L2 issues

• The issue: who pays, what for and how much?

Conclusions

1 heidelberg, 14 - 15 october 1998 how can qos be guaranteed/managed in a multi-provider ip...

Documents