1 / 8

Enhancing Traffic Management Through Congestion Exposure: ConEx Concepts and Use Cases

This document outlines the ConEx (Congestion Exposure) framework, a novel approach designed to improve traffic management by exposing congestion levels within networks. It highlights key concepts, including congestion volume and definitions, and explores multiple use cases, particularly in informing traffic management procedures. The paper also assesses the benefits of using ConEx compared to existing methods, considers deployment arrangements, and addresses security concerns. This work aims to incentivize efficient transport strategies and enhance Quality of Service (QoS) for users.

gene
Télécharger la présentation

Enhancing Traffic Management Through Congestion Exposure: ConEx Concepts and Use Cases

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. draft-ietf-conex-concepts-uses B. Briscoe, Ed. R. Woundy, Ed. Cooper, Ed. IETF 82

  2. Status • Major rev from -02 to -03 • -03 published Oct 31 • List feedback since then

  3. -02 Contents -03 Contents • 1. Introduction • 2. Concepts • 2.1. Congestion • 2.2. Congestion-Volume • 2.3. Rest-of-Path Congestion • 2.4. Definitions • 3. Core Use Case: Informing Traffic Management • 3.1. Use Case Description • 3.2. Additional Benefits • 3.3. Comparison with Existing Approaches • 4. Other Use Cases • 5. Deployment Arrangements • 6. Security Considerations 1. Introduction 2. Concepts 2.1. Definitions 2.2. Non-Goals of ConEx and Common Misconceptions 3. Traffic Management 3.1. Existing Approaches to Traffic Management 4. Exposing Congestion 4.1. ECN - a Step in the Right Direction 5. ConEx Use Cases 5.1. Inform the Operator's Traffic Management 5.2. Consequence: Incentivise Scavenger Transports 5.3. Consequence: User-Controlled Intra-Class Quality of Service (QoS) 5.4. Other Use-Cases 6. Deployment Arrangements 6.1. Incremental Deployment Features of the Protocol Mechanism 6.2. Per-Network Deployment Concepts 6.3. Single Receiving Network Scenario 6.4. Other Initial Deployment Scenarios 7. Potential Issues or Non-Issues 7.1. Congestion as a Commercial Secret 7.2. Self Congestion 8. Security Considerations 8.1. Information Security

  4. 3 Core Use Case: Informing Traffic Management 3.1 Use Case Description • Borrowed congestion policer language from -abstract-mech • Added DSL example 3.2 Additional Benefits (formerly use cases) • Incentivizing scavenger, facilitating intra-class QoS 3.3 Comparison with Existing Approaches • Consolidated -02 intro text and section about existing approaches

  5. 4 Other Use Cases • Added informing capacity provisioning use case • Removed preventing congestion collapse use case 5 Deployment Arrangements • Replaced -02 text with discussion of minimum deployment requirements and pointer to draft-briscoe-conex-initial-deploy-00 6 Security Considerations • Punted to -abstract-mech

  6. Removed since the -02 • Non-goals and misconceptions • Discussion of ECN insufficiency • Potential issues or non-issues: trade secrecy of congestion, self-congestion

  7. Open issues • Is congestion policer description too much mechanism for this draft? (ticket 4) • Sec 3.1 could use a numeric example (ticket 6) • Congestion policer definition missing (ticket 3) • Terminology nits (tickets 1, 2, 5)

  8. Next step • WGLC

More Related