1 / 5

Congestion Notification Process for Real-Time Traffic

Congestion Notification Process for Real-Time Traffic. draft-babiarz-tsvwg-rtecn-00.txt. Kwok Ho Chan khchan@nortelnetworks.com. Jozef Babiarz babiarz@nortelnetworks.com. 59 th IETF, March 1, 2004. DiffServ Field & Explicit Congestion Notification.

kirby-terrell
Télécharger la présentation

Congestion Notification Process for Real-Time Traffic

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. Congestion Notification Process for Real-Time Traffic draft-babiarz-tsvwg-rtecn-00.txt Kwok Ho Chan khchan@nortelnetworks.com Jozef Babiarz babiarz@nortelnetworks.com 59th IETF, March 1, 2004

  2. DiffServ Field & Explicit Congestion Notification Explicit Congestion Notification (ECN) reserved for bits 6 & 7 0 1 2 3 4 5 6 7 ECN DSCP 0 15 4 8 31 Version HLen DS field Length Identification Flags Fragment offset IP header TTL Protocol Header checksum Source address Destination address Data The DiffServ (DS) Field is an 8-bit field in the IP header and is defined in RFC 2474. • The first six bits contain the DiffServ Code Points (DSCP). • The two least significant bits (LSBs) of the DiffServ Field (bits 6 & 7) are used for Explicit Congestion Notifications (ECN) RFC 3168 defines method for TCP flows. Congestion Notification Process for Real-Time Traffic 59th IETF

  3. Major Points • ECN marking for real-time non TCP flows • Does not impact ECN for TCP (RFC 3168) • Meter real-time flows • Mark ECN bits if congestion detected • Metering and marking is deploy only where needed • Requires separation of real-time flows • Reaction to ECN marking is the responsibility of end devices / application Congestion Notification Process for Real-Time Traffic 59th IETF

  4. Usage • Flow admission control of real-time traffic • Rate control of established flows • Features • Allows end-to-end control • Based on current network load conditions • Selective deployment of metering and ECN marking in network • End stations need to support ECN capability Congestion Notification Process for Real-Time Traffic 59th IETF

  5. Next Steps • Would like to request that this draft be considered as a workgroup item Congestion Notification Process for Real-Time Traffic 59th IETF

More Related