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> Wed, 09 May 2012 12:54 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 7FB1021F856C for <apps-discuss@ietfa.amsl.com>; Wed, 9 May 2012 05:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level:
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103, 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 65LEbNKCRmMG for <apps-discuss@ietfa.amsl.com>; Wed, 9 May 2012 05:54:31 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 999FB21F8525 for <apps-discuss@ietf.org>; Wed, 9 May 2012 05:54:31 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF9O5UCG0G0017BX@mauve.mrochek.com> for apps-discuss@ietf.org; Wed, 9 May 2012 05:54:28 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF7HODY84G0006TF@mauve.mrochek.com>; Wed, 9 May 2012 05:54:25 -0700 (PDT)
Message-id: <01OF9O5SHJG40006TF@mauve.mrochek.com>
Date: Wed, 09 May 2012 05:52:05 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 09 May 2012 13:04:11 +0200" <4FAA4F2B.3000307@gmx.de>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format="flowed"
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> <4FAA4F2B.3000307@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: 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: Wed, 09 May 2012 12:54:32 -0000
> On 2012-05-09 04:33, Ned Freed wrote: > > ... > > So what you're saying is that someone could look at this document and conclude > > that it allows inherently ambiguous registrations? > > > > I guess I give the people who'd actually bother to read these specifications at > > this level of detail a bit more credit than that, but fair enough. > > ... > +1 > > It's still a bad idea to continue to rely on the old rule in any way. The other > > problem with the RFC 2045 rule is that it fell apart the minute HTTP overrode > > it and said that text/html without a charset parameter defaults to iso-8859-1. > Actually, text/*. But we have fixed this in httpbis > (<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/20>). A *very* good thing IMO. > > So right there you have what is likely the most commonly used subtype of text > > at this point breaking the rule you're now saying is what old types fall back > > to. Talk about confusing! (Really, in regards to that rule, all this document > > is doing is formalizing something that's been true for almost two decades.) > > > > So how about: > > > > Rgardless of the approach chosen, all new text/* registrations MUST > > clearly specify how the charset of the content is determined; relying > > on the RFC 2045 is no longer permitted. However, existing text/* > > registrations that fail to specify how the charset is determined still > > default to US-ASCII. > Sounds good to me. > > Note that this is different than the old rule, which says that if no charset > > parameter is present the charset must default to us-ascii. > > > > And we probably want to update the main registration document with something > > similar. > I consider this document to be an RFC-ized erratum. If we're going to > update RFC 2045, it should include the changes we're doing here, and > obsolete this document (-> historic), right? That's a good way to look at it. And yes, if RFC 2045 gets updated, we'll need to replace what's there with some version of this. Ned
- [apps-discuss] Last Call: <draft-ietf-appsawg-mim… The IESG
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Barry Leiba
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Ned Freed
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Ned Freed
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Barry Leiba
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Ned Freed
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Barry Leiba
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Ned Freed
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… t.petch
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Ned Freed
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… t.petch
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Ned Freed
- Re: [apps-discuss] Last Call: <draft-ietf-appsawg… Ned Freed