Download
1 / 5
50 likes | 150 Vues
Explore scenarios of localized congestion notification in IETF meetings, focusing on access congestion, network entities, and traffic generation. Consideration for both traffic senders and clients requesting generated traffic. Updates on draft-lei-ecn-localised-congestion-notification-01 presented by Lei Zhu.
E N D
Conex scenarios based on draft-lei-ecn-localised-congestion-notification-01 IETF 79th meeting Nov 2010 Lei Zhu
Update to last version • The slides to introduce the scenarios of localized congestion notification in IETF Maastricht meeting, the use case seems need to working group level. • A use case (Access Congestion in section 5.1) is written, in addition to the argument in 00 version. • Another use case mentioned in IETF 78th Maastricht meeting, which is to notice the traffic generated from network entities.
Use case – Access congestion RED RED RED RED RED Network Network HARQ timer Or Buffer length Or Something else HARQ timer Or Buffer length Or Something else
HTTP HTTP TCP TCP Client Server IP IP L2 L2 L1 L1 TCP SYN SEQ=1791872318 TCP ACK SEQ=1791872319 SYN, SEQ=3880988084 TCP ACK SEQ=3880988085 HTTP GET HTTP 200 OK (MIME Body) Use case – Generated traffic from network The Conex is good to consider not only the the traffic sender who Cause network congestion, but also the clients which really request the traffic generated by network entities.
