Re: [apps-discuss] Feedback about "Update to MIME regarding Charset Parameter Handling in Textual Media Types"

Ned Freed <ned.freed@mrochek.com> Fri, 30 March 2012 18:16 UTC

Return-Path: <ned.freed@mrochek.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 4935021F8656 for <apps-discuss@ietfa.amsl.com>; Fri, 30 Mar 2012 11:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level:
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599]
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 qxBi7v2lSDsW for <apps-discuss@ietfa.amsl.com>; Fri, 30 Mar 2012 11:16:08 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6F65D21F8646 for <apps-discuss@ietf.org>; Fri, 30 Mar 2012 11:16:05 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01ODQ3PM20C0017PSW@mauve.mrochek.com> for apps-discuss@ietf.org; Fri, 30 Mar 2012 11:15:57 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01ODNXKOYL8000ZUIL@mauve.mrochek.com>; Fri, 30 Mar 2012 11:15:48 -0700 (PDT)
Message-id: <01ODQ3PGNAFW00ZUIL@mauve.mrochek.com>
Date: Fri, 30 Mar 2012 11:15:22 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 30 Mar 2012 14:24:00 +0200" <4F75A5E0.4020908@gmx.de>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format="flowed"
References: <CAJQvAudekOKa2mzas-igD_6pa2je000Darin2HDNda-sk9TLCQ@mail.gmail.com> <01OCB41ZCJES00ZUIL@mauve.mrochek.com> <4F75A5E0.4020908@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Anne van Kesteren <annevk@opera.com>, Ned Freed <ned.freed@mrochek.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Feedback about "Update to MIME regarding Charset Parameter Handling in Textual Media Types"
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: Fri, 30 Mar 2012 18:16:09 -0000

> On 2012-02-23 04:59, Ned Freed wrote:
>  > ...
> >> For backwards compatibility, pretty much every existing text/* type
> >> >  will have to violate this "SHOULD NOT".
> > Yep. That's the main reason why it needs to be a SHOULD.
>  > ...

> Alexey and myself just discussed this, and we do agree that the SHOULD
> will need to be violated for updates of text/xml and text/html, but we
> believe this is ok (the authors of the new registrations will understand
> what the SHOULD is about and how to deal with it).

Sounds like we're all in agreement then.

				Ned