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

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 10 April 2012 13:18 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7C221F860D for <apps-discuss@ietfa.amsl.com>; Tue, 10 Apr 2012 06:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.301
X-Spam-Level:
X-Spam-Status: No, score=-102.301 tagged_above=-999 required=5 tests=[AWL=0.298, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id piaL-um3UZyb for <apps-discuss@ietfa.amsl.com>; Tue, 10 Apr 2012 06:18:08 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id DA2E021F8606 for <apps-discuss@ietf.org>; Tue, 10 Apr 2012 06:18:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1334063886; d=isode.com; s=selector; i=@isode.com; bh=ZwcsBolAUqw+PIP8e0x/7ZOicBJr1rMjzdNV3DvEit8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=TlRKpDudhz1OdEn+p4e6cLIwmB8bpUD3RPzbExfF9DxWOd23iSOuFFWx/xugd+aWDTQ8z7 It+q7QA4+blqQlk8vny9SRwzqDrVfjgoy98fWC09ciF2FKHW7CRwV7n9MZ0qEkLFKKg0sB xpbLcv7NykovKTPp3oNyh6kDsEbRkhM=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <T4QzDQAg26be@rufus.isode.com>; Tue, 10 Apr 2012 14:18:06 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F843332.7060705@isode.com>
Date: Tue, 10 Apr 2012 14:18:42 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Ned Freed <ned.freed@mrochek.com>
References: <9452079D1A51524AA5749AD23E0039280C9874@exch-mbx901.corp.cloudmark.com> <01OE2UNN2HJ000ZUIL@mauve.mrochek.com> <4F82B5F6.3050806@gmx.de> <01OE3UQGECV600ZUIL@mauve.mrochek.com>
In-Reply-To: <01OE3UQGECV600ZUIL@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] WGLC for draft-ietf-appsawg-mime-default-charset
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2012 13:18:08 -0000

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.