I look through the whole document and I really think it's a good idea to 
propagate congestion signals through different networks,
it will be good to deal with the congestion situation especially when there are 
lower layer en route.



> >Date: Mon, 04 Nov 2013 22:03:45 +0000
> >To: "tsvwg IETF list" <[email protected]>, AQM IETF list <[email protected]>
> >From: Bob Briscoe <[email protected]>
> >Subject: Who supports tsvwg adoption of adding ECN to L2 or tunnel
> protocols?
> >Cc: John Kaippallimalil <[email protected]>, Pat Thaler
> ><[email protected]>,
> >[email protected]
> >
> >Folks,
> >
> >Pls respond if you support this being adopted as a work-group item in
> >the IETF transport services w-g (tsvwg). The WG chairs need visibility
> >of interest.
> >Even better, if you're willing to read / comment / review / implement
> >
> >Guidelines for Adding Congestion Notification to Protocols that
> >Encapsulate IP
> ><http://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-encap-guidelines>
> >
> >Abstract
> >
> >    The purpose of this document is to guide the design of congestion
> >    notification in any lower layer or tunnelling protocol that
> >    encapsulates IP.  The aim is for explicit congestion signals to
> >    propagate consistently from lower layer protocols into IP.  Then the
> >    IP internetwork layer can act as a portability layer to carry
> >    congestion notification from non-IP-aware congested nodes up to the
> >    transport layer (L4).  Following these guidelines should assure
> >    interworking between new lower layer congestion notification
> >    mechanisms, whether specified by the IETF or other standards bodies.
> >
> >
> >[Cross-posting tsvwg & aqm, just in case]
> >
> >
> >Bob Briscoe,
> >also for co-authors Pat Thaler and John Kaippallimalil
> >
> >__________________________________________________________
> ______
> >Bob Briscoe,                                                  BT
> 
> ___________________________________________________________
> _____
> Bob Briscoe,                                                  BT

_______________________________________________
aqm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/aqm

Reply via email to