1 / 14

QoS Service Level Agreement (SLA) for Tactical/Deployed Scenario

QoS Service Level Agreement (SLA) for Tactical/Deployed Scenario. Deborah Goldsmith MITRE Corporation (619)758-7829 deborah@mitre.org. Outline. Problem Statement General Requirements Scenario Description Tactical /Deployed SLA Data Classification and Marking Issues Questions.

dara-holcomb
Download Presentation

QoS Service Level Agreement (SLA) for Tactical/Deployed Scenario

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. QoS Service Level Agreement (SLA)for Tactical/Deployed Scenario Deborah Goldsmith MITRE Corporation (619)758-7829 deborah@mitre.org

  2. Outline • Problem Statement • General Requirements • Scenario Description • Tactical /Deployed SLA • Data Classification and Marking • Issues • Questions

  3. Problem Statement • Meet QoS Service Level Agreements (SLA’s) for the Tactical/Deployed platform across the End-to-End Circuit

  4. General Requirements* • Applications will converge to a common infrastructure (most likely Layer 3 IP) • Voice • Video • Datagram • Control/Management • Applications MUST work end-to-end across wide diversity of LANs, MANs, WANs • System MUST allow user to indicate mission-based priority and support priority handling to resolve end-to-end bottlenecks • System MUST meet stringent IA requirements *DISA, 5-29-02

  5. CAMP/POST/STATION WIDE AREA NETWORK TACTICAL/DEPLOYED Scenario Description:The End-to-End Circuit* FIXED TACTICAL END-TO-END DISN • Solution must apply to ALL elements of the Defense Information Systems Network (C/P/S, WAN, TACTICAL) • F-F, F-T, T-T • Multiple domains • Traffic in the WAN traverses many network domains that may be considered analogous to external carrier networks with their own QoS/SLA’s *DISA, 5-29-02

  6. Scenario Description:The Tactical/Deployed Segment • Tactical \deployed communications use multiple RF gateways • RF gateways represent bottlenecks due to bandwidth constraints

  7. LOS VPN VPN enclave enclave enclave Scenario Description:The Tactical Platform & the RF Gateway SLA WAN GW LAN WAN GW LAN RF GW LAN

  8. Tactical/Deployed SLA • Minimum bandwidth guarantees for specified data types or sources • B/W, latency, jitter guarantees for VoIP and packet VTC • Latency guarantees for tactical messages • No starvation for Best Effort (BE) (aggregate)

  9. Data Classification and Marking

  10. Application Flow Categories* Each category has QoS Performance Metrics *DISA, 5-29-02

  11. Marking RFC’s

  12. Sample DSCP Marking by Application Categories • Marking by priority and latency requirements

  13. Issues • Mobility • Ad-hoc Networks • Link outage and degradation

  14. Questions • Can DiffServ (DSCP’s) be the basis of a near-term implementation plan to implement end-to-end QoS for the tactical/deployed scenario? • Bandwidth Reservation for some applications • B/W, Latency and Jitter guarantees for VOIP, VTC • Latency guarantees for tactical messages • Priority and precedence • No starvation for Best effort • What are the end-to-end QoS mechanisms to implement a long-term implementation plan? • Dynamic QoS based on policy • Admission control • QoS-aware applications signaling the network • Reroute with QoS on link failure /degradation • Mobility • Performance monitoring and control YesNo

More Related