W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2007

Re: NEW ISSUE: updating from RFC2048 to RFC4288

From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Wed, 25 Apr 2007 20:41:10 +0100
Message-ID: <462FAED6.2070602@isode.com>
To: Julian Reschke <julian.reschke@gmx.de>
CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>

Mark Nottingham wrote:

> Catching up... this is now issue 55.
>
> http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/issues/#i55
>
> Cheers,
>
> On 2007/01/06, at 12:50 AM, Julian Reschke wrote:
>
>> Hi.
>>
>> The update from RFC2048 to RFC4288 requires minor modifications for  
>> the media type registrations for "message/http", "application/http"  
>> and "multipart/byteranges", thus we probably should treat this as a  
>> separate issue.
>>
>> I've looked at RFC4288 and extended the registrations -- see  
>> <http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon- 
>> rfc2616bis-latest.html#rfc.section.A> and <http://www.w3.org/ 
>> Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis- 
>> latest.html#rfc.section.B>.  Feedback appreciated...
>
Hi Julian,
The change seems fine, but I am not sure that the "Interoperability 
considerations" and "Applications that use this media type" should stay 
empty.
Received on Wednesday, 25 April 2007 19:42:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:09 GMT