Re: [apps-discuss] WGLC for draft-ietf-appsawg-mime-default-charset

[Alexey Melnikov <[e-mail]>]

On 09/04/2012 15:28, Ned Freed wrote:
>> On 2012-04-08 23:08, Ned Freed wrote:
>> >> This message starts Working Group Last Call for 
>> draft-ietf-appsawg-mime-default-charset.  Please review the document 
>> and provide comments to the list, the co-chairs, or the authors by 
>> Friday, April 20th.
>> >
>> >> The datatracker link is 
>> https://datatracker.ietf.org/doc/draft-ietf-appsawg-mime-default-charset/.
>> >
>> >> -MSK, APPSAWG co-chair
>> >
>> > I just reviewed this document and it's looking good to me.
>> >
>> > You'll probably want to remove the anchor2 bit at the end of the WGLC.
>> Of course.
>> I'm also not totally convinced that HTTPbis actually needs to reference
>> this document at all; any opinions on this?
>
> Really ard to say without knowing how they deal with the iso-8859-1. I 
> can see
> it being done in a way that doesn't need a reference. Or it could be 
> done in a
> way where a reference would be helpful.
>
> Not sure I see any need for a normative reference though.

(I've mentioned my opinion to Julian, but I would like to state it for 
the record.)
I think an update to RFC 2616 should have a reference to 
draft-ietf-appsawg-mime-default-charset and make it clear that the 
previous default was removed. An Informative reference to 
draft-ietf-appsawg-mime-default-charset should be fine.