30 Sep
2009
30 Sep
'09
9:27 a.m.
MURATA Makoto wrote:
So how about changing it just for the HTTP transport then?
You are proposing to fix HTTP 1.1. Then, you would need to write an internet draft which would obsolete RFC 2068 and have it approved by IESG. ...
Actually, it would be RFC2616, not RFC2068. Furthermore, we're actually doing this in the IETF HTTPbis Working Group. So let's rephrase it... do you have an opinion whether an update to HTTP/1.1 *should* make this change? BR, Julian