IETF Logo Mail Archive

Re: [apps-discuss] Last Call: <draft-ietf-appsawg-mime-default-charset-03.txt> (Update to MIME regarding Charset Parameter Handling in Textual Media Types) to Proposed Standard

Ned Freed <ned.freed@mrochek.com> Fri, 11 May 2012 16:05 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 923D421F86B3 for <apps-discuss@ietfa.amsl.com>; Fri, 11 May 2012 09:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 OljFvam2fkWk for <apps-discuss@ietfa.amsl.com>; Fri, 11 May 2012 09:05:13 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id CA71B21F85B4 for <apps-discuss@ietf.org>; Fri, 11 May 2012 09:05:12 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OFCNDSESZ40018AN@mauve.mrochek.com> for apps-discuss@ietf.org; Fri, 11 May 2012 09:05:01 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF7HODY84G0006TF@mauve.mrochek.com>; Fri, 11 May 2012 09:04:47 -0700 (PDT)
Message-id: <01OFCNDIQVO20006TF@mauve.mrochek.com>
Date: Fri, 11 May 2012 08:59:30 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 11 May 2012 16:02:12 +0200" <011601cd2f7e$b140a140$4001a8c0@gateway.2wire.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120423132812.32410.11259.idtracker@ietfa.amsl.com> <CAC4RtVDZfXi1JwGJLGwOVgsGuU-1dH-uj8bXTGCmjrva80mNhg@mail.gmail.com> <01OF8RSPPS320006TF@mauve.mrochek.com> <CALaySJLFrKSF9JPBC54j0EaTQ6SNXM2+tag2uU2SmVjWxE7Erg@mail.gmail.com> <01OF98WFXDKI0006TF@mauve.mrochek.com> <00a801cd2f7a$90e429c0$4001a8c0@gateway.2wire.net> <4FAD26E7.5020800@gmx.de> <011601cd2f7e$b140a140$4001a8c0@gateway.2wire.net>
To: "t.petch" <ietfc@btconnect.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, Barry Leiba <barryleiba@computer.org>, Ned Freed <ned.freed@mrochek.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-mime-default-charset-03.txt> (Update to MIME regarding Charset Parameter Handling in Textual Media Types) to Proposed Standard
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, 11 May 2012 16:05:13 -0000

> But ... that is saying that XML recognises the need to be able to auto-detect
> the character encoding and is designed to do so.  This change to mime default
> charset imposes the need to auto-detect on all future text/* where the encoding
> is transported inside the payload, which the old rules did not.

It does nothing of the sort. The preferential use of inline information is a
SHOULD, not a MUST. If a given syntax carries such information inline but
doesn't define a reliable standalone way to extract it (it depends on
additional external information, for example), that would be more than
sufficient reason not to use inline information.

> Perhaps a corner case not worth mentioning.

It's not even that.

				Ned

v2.23.0 | Report a Bug | By Email