1 / 5

Congestion Notification Process for Real-Time Traffic

Congestion Notification Process for Real-Time Traffic. draft-babiarz-tsvwg-rtecn-03.txt. Jozef Babiarz (babiarz@nortel.com) Kwok Ho Chan (khchan@nortel.com) Victor Firoiu (victor.firoiu@baesystems.com). TSVWG, 62 th IETF, March. 7th , 2005. Status Update.

jfiller
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-03.txt Jozef Babiarz (babiarz@nortel.com) Kwok Ho Chan (khchan@nortel.com) Victor Firoiu (victor.firoiu@baesystems.com) TSVWG, 62th IETF, March. 7th , 2005

  2. Status Update • Sally Floyd has agreed to be an reviewer of rtecn draft. • Changed ECN semantics to align closer to RFC 3168 • Added example in Appendix A of token bucket metering that can be used to measure real-time traffic • Added description of ECN Marker behavior for rtecn • Added method for detecting mis-marking of ECN bits by routers • Added link to a companion draft that define a use case of rtecn http://www.ietf.org/internet-drafts/draft-alexander-rtecn-admission-control-use-case-00.txt Congestion Notification Process for Real-Time Traffic TSVWG, 62th IETF

  3. Comparison of ECN Semantics • Not- ECT – Endpoints are Not ECN-Capable • ECT(0) - ECN-Capable Transport (Endpoints are ECN-Capable) • ECT(1) - ECN-Capable Transport (Endpoints are ECN-Capable) • CE - Congestion Experienced • CE(1) – Congestion Experienced at 1st level • CE(2) – Congestion Experienced at 2nd level Congestion Notification Process for Real-Time Traffic TSVWG, 62th IETF

  4. Comparison of ECN • Congestion Detection Method • RTECN uses flow rate measurement with rate level comparison • RFC 3168 uses AQM • Congestion Level Indication • RTECN provides two levels • RFC 3168 only single level Congestion Notification Process for Real-Time Traffic TSVWG, 62th IETF

  5. Next Steps • Cleanup some remaining section in draft to reflect the current ECN semantics, etc. • Add text explaining the different configuration with ECN-capable and non-ECN-capable endpoints. • Address how real-time inelastic ECN-capable flow will react when it encounters non-DiffServ router that support RFC 3168. • Address any issues that come up from reviewers. Congestion Notification Process for Real-Time Traffic TSVWG, 62th IETF

More Related