qos service level agreement (sla) for tactical/deployed scenario
Post on 01-Jan-2016
Embed Size (px)
DESCRIPTIONQoS Service Level Agreement (SLA) for Tactical/Deployed Scenario. Deborah Goldsmith MITRE Corporation (619)758-7829 firstname.lastname@example.org. Outline. Problem Statement General Requirements Scenario Description Tactical /Deployed SLA Data Classification and Marking Issues Questions. - PowerPoint PPT Presentation
QoS Service Level Agreement (SLA)for Tactical/Deployed ScenarioDeborah GoldsmithMITRE Corporation (619)email@example.com
OutlineProblem StatementGeneral Requirements Scenario DescriptionTactical /Deployed SLAData Classification and MarkingIssuesQuestions
Problem StatementMeet QoS Service Level Agreements (SLAs) for the Tactical/Deployed platform across the End-to-End Circuit
General Requirements*Applications will converge to a common infrastructure (most likely Layer 3 IP)VoiceVideoDatagramControl/ManagementApplications MUST work end-to-end across wide diversity of LANs, MANs, WANsSystem MUST allow user to indicate mission-based priority and support priority handling to resolve end-to-end bottlenecksSystem MUST meet stringent IA requirements* DISA, 5-29-02
Scenario Description:The End-to-End Circuit* FIXEDTACTICALEND-TO-END DISNSolution must apply to ALL elements of the Defense Information Systems Network (C/P/S, WAN, TACTICAL)F-F, F-T, T-TMultiple domainsTraffic in the WAN traverses many network domains that may be considered analogous to external carrier networks with their own QoS/SLAs
* DISA, 5-29-02
Scenario Description:The Tactical/Deployed SegmentTactical \deployed communications use multiple RF gatewaysRF gateways represent bottlenecks due to bandwidth constraints
Scenario Description:The Tactical Platform & the RF GatewayWANGWWANGWLANLANLANRFGWSLA
Tactical/Deployed SLAMinimum bandwidth guarantees for specified data types or sourcesB/W, latency, jitter guarantees for VoIP and packet VTCLatency guarantees for tactical messagesNo starvation for Best Effort (BE) (aggregate)
Data Classification and Marking
Application Flow Categories*Each category has QoS Performance Metrics* DISA, 5-29-02
Sample DSCP Marking by Application CategoriesMarking by priority and latency requirements
IssuesMobilityAd-hoc NetworksLink outage and degradation
QuestionsCan DiffServ (DSCPs) be the basis of a near-term implementation plan to implement end-to-end QoS for the tactical/deployed scenario?Bandwidth Reservation for some applicationsB/W, Latency and Jitter guarantees for VOIP, VTCLatency guarantees for tactical messagesPriority and precedenceNo starvation for Best effortWhat are the end-to-end QoS mechanisms to implement a long-term implementation plan?Dynamic QoS based on policyAdmission controlQoS-aware applications signaling the networkReroute with QoS on link failure /degradationMobilityPerformance monitoring and control
The WG faced the challenge of determining the end-to-end IP QoS requirements of user application. Once the QoS requirements were understood, then it was possible to determine whether these applications can perform satisfactorily in the worst-case reference circuit environment.The WG settled upon six QoS application flow types; two incorporating TCP setup and UDP* flow; three incorporating TCP; and one including other protocols.Cited within each of these are practical examples of each application type. The final report contains the formal definitions for each application flow type; some derived from existing standards body activities, and others developed by the WG.
- If multiple decisions/endorsements are asked of the board, an endorsement slide should immediately follow the issue charts supporting that endorsement.
- Recap all decisions/endorsements in summary slide.