110 likes | 236 Vues
This document outlines important developments in end-to-end IP network performance, particularly with the growth of real-time applications such as VoIP, multimedia conferencing, and streaming. It highlights the necessity for strictere IP packet transfer specifications and new RFCs addressing loss patterns and bulk transfer capacity. Key standards and initiatives discussed include Y.1540 and Y.1541, QoS classes and mechanisms, and performance objectives. The report identifies next steps for achieving these objectives, including process definitions, flexible agreements between networks, and enhanced QoS signaling methods.
E N D
IP Performance Specifications -Progress and Next Steps July 11, 2002 Al Morton
End-to-End IP Network Performance • Growth of real-time/CBR application use on IP nets • VoIP, Multi-Media Conferencing, Streaming... • New applications require stricter performance
New RFCs Loss Patterns Bulk Transfer Capacity Current I-Ds Packet Reordering Active Meas. Protocol Req. IPPM MIB Newly Chartered Work on Link Bandwidth Capacity Performance Objectives Y.1541 (May 2002), six QoS Classes Suggest QoS Signaling Support/Methods Parameter Revisions Y.1540 (Nov 2002) “other” Packet Transfer MPLS? Evolution of IPPM and Question 6/13
Y.1541 "Provisional IP QoS Classes” • Y.1221-based Traffic Contracts • IP transfer capabilities include: the service model, traffic descriptor, conformance definition and any QOS commitments. • Transfer Capabilities include Dedicated Bandwidth, Statistical Bandwidth, and Best Effort.
Viewpoints of QoS From G.1000, Communications quality of service: A framework and definitions
Elements of Service Provider’s IP QoS View QoS Framework Std IP Perf Parameters Std IP QoS Classes SLAs Objectives Reality Engineering & Implementation QoS Mechanisms Std Active Meas. Sampling Methodologies Passive Monitoring
QoS Agreements - Today and Tomorrow Published Req. Design& Eng. Reqmnts. IS Manager Cooperating Network Request ACK/REJ/Mod Objectives Reality Provisioning QoS Mech. Reports (SLAs) Users Apps
QoS Agreements - Viewed as 3 Entities Network: Published Req. Design& Eng. ... User Requirements IS Manager/ Requirements Objectives Reality Provisioning QoS Mech. Reports (SLAs) Reports Applications Perceived QoS
QoS Agreements - Future User Application Network(s) ... Application Requirements Cnfg.Choices Request ACK/REJ/Mod Request ACK/REJ/Mod QoS Requirements QoS Classes & Decisions Topo/Policy Design/Eng. Objectives Reality Provisioning QoS Mech. Reports (SLAs) Feedback Monitoring Perceived QoS
Next Steps • Define Process and Methods to ACHIEVE e-e Objectives • Begin with Single networks and Static Agreements • Static, with Two or Three Networks • difficult with more networks (see draft M.2301) • Build-in Flexibility (not too much) • Network to Network Signaling for QoS • In the “Oracle” model, each network has an entity with specific knowledge and control capabilities. These entities use a signaling protocol to communicate efficiently across network boundaries (accept/reject/modify requests). • Standardize Delay Variation Definitions • Revisit IP Service Availability Function Definition • Wide range of sensitivities across user applications