Standards for E2E QoS Delivery: Progress and Future Needs July 25, 2003 Al Morton.
-
Upload
sofia-mcmanus -
Category
Documents
-
view
215 -
download
1
Transcript of Standards for E2E QoS Delivery: Progress and Future Needs July 25, 2003 Al Morton.
![Page 1: Standards for E2E QoS Delivery: Progress and Future Needs July 25, 2003 Al Morton.](https://reader036.fdocuments.in/reader036/viewer/2022082701/5515405155034673228b5dff/html5/thumbnails/1.jpg)
Standards for E2E QoS Delivery:Progress and Future Needs
Standards for E2E QoS Delivery:Progress and Future Needs
July 25, 2003 July 25, 2003
Al Morton Al Morton
![Page 2: Standards for E2E QoS Delivery: Progress and Future Needs July 25, 2003 Al Morton.](https://reader036.fdocuments.in/reader036/viewer/2022082701/5515405155034673228b5dff/html5/thumbnails/2.jpg)
Viewpoints of QoS Viewpoints of QoS
CUSTOMERSERVICEPROVIDER
Customer’sQOS
Requirements
QOS OfferedBy
Provider
QOSAchieved byProvider
QOSPerceived
By Customer
From G.1000, “Communications Quality of Service: A Framework and Definitions”
ObjectivesReality
![Page 3: Standards for E2E QoS Delivery: Progress and Future Needs July 25, 2003 Al Morton.](https://reader036.fdocuments.in/reader036/viewer/2022082701/5515405155034673228b5dff/html5/thumbnails/3.jpg)
QoS Agreements - FutureQoS Agreements - Future
ObjectivesReality
QoSRequirements
PerceivedQoS
QoS Classes& DecisionsTopo/PolicyDesign/Eng.
ProvisioningQoS Mech.
Reports(SLAs)
ApplicationRequirements
Cnfg.Choices
Feedback
Monitoring
User Application Network(s)
Request
ACK/REJ/Mod
Request
ACK/REJ/Mod
![Page 4: Standards for E2E QoS Delivery: Progress and Future Needs July 25, 2003 Al Morton.](https://reader036.fdocuments.in/reader036/viewer/2022082701/5515405155034673228b5dff/html5/thumbnails/4.jpg)
Y.1541 "Provisional IP QoS Classes, Table 1”Y.1541 "Provisional IP QoS Classes, Table 1”
NetworkPerformance
Parameter
Nature of NetworkPerformance
Objective
Class 0 Class 1 Class 2 Class 3 Class 4Class 5
Un-specified
IPTD Upper bound on themean IPTD
100ms 400 ms 100ms 400ms 1 s U
IPDV Upper bound on the1-10 -3 quantile ofIPTD minus theminimum IPTD
50ms 50 ms U U U U
IPLR Upper bound on thepacket lossprobability
1*10 -3 1*10 -3 1*10 -3 1*10 -3 1*10 -3 U
IPER Upper bound 1*10 -4 U
Y.1541 Principles• Per Flow Objectives satisfy a wide range of User Applications • Small set of Network QoS classes simplifies network engineering• Evaluation Interval is 1 minute for most objectives• Packet Payload Sizes suggested for Evaluation: 160 and 1500 bytes• Objectives apply while IP Service is Available
![Page 5: Standards for E2E QoS Delivery: Progress and Future Needs July 25, 2003 Al Morton.](https://reader036.fdocuments.in/reader036/viewer/2022082701/5515405155034673228b5dff/html5/thumbnails/5.jpg)
Delivering E2E QoS -- More Work NeededDelivering E2E QoS -- More Work Needed
TE TE ER . . . . . .
AS
Network QoS (UNI-UNI)
AS ASCustomer Installation Customer Installation
End-End QoS (User-to-User)
LAN LAN
IP Network Cloud
UNI UNI R R R R ER
DSTSRC
Network QoS Mechanisms
User/Network QoS Signaling Protocols
? Automated Subscription? Authorization/Security? Accounting? Restoration Priority? Admission Priority
Standards and/or Agreement for:
Flexible Degreesof Management Performance
Monitoring
![Page 6: Standards for E2E QoS Delivery: Progress and Future Needs July 25, 2003 Al Morton.](https://reader036.fdocuments.in/reader036/viewer/2022082701/5515405155034673228b5dff/html5/thumbnails/6.jpg)
SummarySummary There are many perspectives on QoS: adjectives There are many perspectives on QoS: adjectives
provide more precision.provide more precision. For User-User QoS, customer expectation and For User-User QoS, customer expectation and
application design play a role.application design play a role. Network QoS Objectives are in terms of packet Network QoS Objectives are in terms of packet
transfer performance parameters, and are divided into transfer performance parameters, and are divided into a small number of Classesa small number of Classes
E2E QoS Signaling Requirements Development E2E QoS Signaling Requirements Development under way in SG 11 and IETF NSISunder way in SG 11 and IETF NSIS
Several pieces needed: Subscription, Authorization, Several pieces needed: Subscription, Authorization, Accounting, PrioritiesAccounting, Priorities