W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2009

RE: Review of Content-Encoding: value token [exi]

From: John Schneider <john.schneider@agiledelta.com>
Date: Mon, 24 Aug 2009 14:55:10 -0700
To: "'Henrik Nordstrom'" <henrik@henriknordstrom.net>
Cc: <ietf-http-wg@w3.org>
Message-ID: <F1C30A2197AC43E7A042C926693F8816@jcsdell8600>
Henrik,

Thank you again for the quick response and clear guidance. This makes a lot
of sense. I will let the EXI working group know and follow the defined IANA
process for registration. 

	Best wishes,

	John

> -----Original Message-----
> From: Henrik Nordstrom [mailto:henrik@henriknordstrom.net] 
> Sent: Monday, August 24, 2009 2:26 PM
> To: john.schneider@agiledelta.com
> Cc: ietf-http-wg@w3.org
> Subject: RE: Review of Content-Encoding: value token [exi]
> 
> mån 2009-08-24 klockan 12:06 -0700 skrev John Schneider:
> 
> > Thank you for your quick response to my message. It is 
> quite possible 
> > that this is my mistake and I misunderstood Mark. If it is more 
> > appropriate for us to follow the current IANA process for 
> > registration, we would be very happy to do that. Of course, we are 
> > also very interested in any further comments from HTTPbis 
> on the topic even it does not end up your action list.
> 
> For registration you need to follow the defined IANA process.
> 
> It's an extension, and extensions to HTTP is not in scope for 
> HTTPbis at the moment. Our task is to get RFC2616 + parts of 
> other closely related standards track documents cleaned up 
> and in good shape, and explicitly forbidden to add extensions 
> unless deemed absolutely required to correct errors or 
> serious shortcomings in the earlier specifications.
> 
> Regards
> Henrik
> 
Received on Monday, 24 August 2009 21:55:50 GMT

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