Re: [apps-discuss] [happiana] comments on draft-freed-media-type-regs

Ned Freed <ned.freed@mrochek.com> Sun, 05 February 2012 20:58 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 DF4E721F856F for <apps-discuss@ietfa.amsl.com>; Sun, 5 Feb 2012 12:58:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level:
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 HJdsWqJcrYZf for <apps-discuss@ietfa.amsl.com>; Sun, 5 Feb 2012 12:58:57 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6921121F854D for <apps-discuss@ietf.org>; Sun, 5 Feb 2012 12:58:57 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OBMRKKWHV400KI3Q@mauve.mrochek.com> for apps-discuss@ietf.org; Sun, 5 Feb 2012 12:58:52 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OBHM72OXPS00ZUIL@mauve.mrochek.com>; Sun, 5 Feb 2012 12:58:47 -0800 (PST)
Message-id: <01OBMRKHFVU800ZUIL@mauve.mrochek.com>
Date: Sun, 05 Feb 2012 12:52:26 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sun, 05 Feb 2012 15:28:37 -0500" <B5EEE7F9167ED9C6CE1284BD@PST.JCK.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <4EEBA03D.7000906@stpeter.im> <01OBLLE13ULY00ZUIL@mauve.mrochek.com> <B5EEE7F9167ED9C6CE1284BD@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
Cc: Ned Freed <ned.freed@mrochek.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] [happiana] comments on draft-freed-media-type-regs
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: Sun, 05 Feb 2012 20:58:58 -0000

> --On Saturday, February 04, 2012 16:42 -0800 Ned Freed
> <ned.freed@mrochek.com> wrote:

> >...
> >> 5. Encodings
> >
> >> When mentioning "7bit US-ASCII text", perhaps reference RFC
> >> 5198.
> >
> > Er, no. RFC 5198 doesn't even mention US-ASCII. And the
> > Unicode format it defines is 8bit, not 7bit!

> It mentions ASCII and, IIR, NVT ASCII.  As far as charsets are
> concerned, the latter, along with RFC 20 ASCII, are a 7bit code
> embedded in an 8bit field.  But they are mentioned largely in
> the context of moving beyond them.   (Abbreviated version of a
> long tirade: there is no such thing as "US-ASCII" and the term/
> attempted distinction doesn't even have informal value unless
> you think there are, e.g., Canadian-ASCII, Mexican-ASCII,
> Brazilian-ASCII, etc.).

But not US-ASCII, and as you say, it discusses ASCII in any form only in
passing. If we really need a reference for that we can copy the one that's in
MIME that actually points to a defining document. But seriously, does anyone
really think we need such a reference? We're concerned with encodings, not
charsets, here, and US-ASCII is simply being mentioned in some text providing
context as to why encodings are even part of a registration.

				Ned