Paul Hoffman wrote: > The proposed charter has: > * Document the security properties of HTTP and its associated > mechanisms (e.g., Basic and Digest authentication, cookies, TLS) > for common applications > So, would obviously-needed changes to the associated mechanisms be in > scope for the WG, or not? I would have hoped that we can concentrate on revising RFC2616, and do just that. However, we got signals from IESG members that a revision of RFC2616 would not be accepted unless it improves the security story. IMHO a very bad idea. Fixing it needs, but that needs to be done somewhere else. >> Are there any specific extensions you have in mind? > > Definitely not. I was asking whether or not we want to clamp down on > charter creep now or later. :-) I'd prefer the charter to be as small & precise as possible. Best regards, JulianReceived on Wednesday, 30 May 2007 15:45:05 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 October 2011 12:13:58 GMT