[Bloat] Re-ECN

[Bloat] Re-ECN

[Dave Täht]

JG's blog comments contain a wealth of information as yet unexplored and
quantified. I ran across mention of re-ECN[1], which seems to have some
potential. 

In particular, I liked the full backward compatibility with RFC3514[2].

Is the "is it safe to use ECN" research going on exploring what happens
when the last unused bit in the TCP header is also set?

-- 
Dave Taht
http://nex-6.taht.net

1: http://tools.ietf.org/html/draft-briscoe-tsvwg-re-ecn-tcp-09
2: http://tools.ietf.org/html/rfc3514

Re: [Bloat] Re-ECN

[Richard Scheffenegger]

Right now, focus is on IPv6 - IPv4 may follow is the IETF find the benefits 
valuable enough to spend the last bit on this scheme..


See https://datatracker.ietf.org/wg/conex/charter/
and http://www.ietf.org/mail-archive/web/conex/current/maillist.html

Regards,
   Richard
----- Original Message ----- 
From: "Dave "Täht"" <d@taht.net>
To: "bloat" <bloat@lists.bufferbloat.net>
Cc: "Steven Bellovin" <smb@cs.columbia.edu>
Sent: Sunday, February 13, 2011 6:31 AM
Subject: [Bloat] Re-ECN


>
> JG's blog comments contain a wealth of information as yet unexplored and
> quantified. I ran across mention of re-ECN[1], which seems to have some
> potential.
>
> In particular, I liked the full backward compatibility with RFC3514[2].
>
> Is the "is it safe to use ECN" research going on exploring what happens
> when the last unused bit in the TCP header is also set?
>
> -- 
> Dave Taht
> http://nex-6.taht.net
>
> 1: http://tools.ietf.org/html/draft-briscoe-tsvwg-re-ecn-tcp-09
> 2: http://tools.ietf.org/html/rfc3514
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat