Re: Why the normative form of IETF Standards is ASCII
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Fri, 12 March 2010 05:26 UTC
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA4493A6855 for <ietf@core3.amsl.com>; Thu, 11 Mar 2010 21:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level:
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsP6o81YFnhA for <ietf@core3.amsl.com>; Thu, 11 Mar 2010 21:26:10 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id AB1033A6358 for <ietf@ietf.org>; Thu, 11 Mar 2010 21:26:09 -0800 (PST)
Received: (qmail 54883 invoked from network); 12 Mar 2010 06:33:35 -0000
Received: from p2031-ipbf5208marunouchi.tokyo.ocn.ne.jp (HELO necom830.hpcl.titech.ac.jp) (118.8.149.31) by necom830.hpcl.titech.ac.jp with SMTP; 12 Mar 2010 06:33:35 -0000
Message-ID: <4B99D050.3020900@necom830.hpcl.titech.ac.jp>
Date: Fri, 12 Mar 2010 14:25:36 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: Doug Ewell <doug@ewellic.org>
Subject: Re: Why the normative form of IETF Standards is ASCII
References: <201003120011.o2C0BHOx016564@fs4113.wdf.sap.corp> <4B99A30B.9090202@levkowetz.com> <1EE4D60F6CA6499D905E5E4C9C518CE2@DGBP7M81>
In-Reply-To: <1EE4D60F6CA6499D905E5E4C9C518CE2@DGBP7M81>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 05:26:10 -0000
Doug Ewell wrote: > These are two separate topics. You could have plain text encoded in > UTF-8. You could have HTML or PDF-A that uses nothing but ASCII > characters. As was demonstrated by Tim Bray against Martin Rex's ASCII message, they are strongly interrelated topics. Masataka Ohta
- Why the normative form of IETF Standards is ASCII Donald Eastlake
- Re: Why the normative form of IETF Standards is A… Andrew Sullivan
- RE: Why the normative form of IETF Standards is A… Richard Shockey
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Jorge Amodio
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… Mark Atwood
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Jorge Amodio
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Huub van Helvoort
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- RE: Why the normative form of IETF Standards is A… Eric Gray
- Re: Why the normative form of IETF Standards is A… Jorge Amodio
- Re: Why the normative form of IETF Standards is A… Jorge Amodio
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Henrik Levkowetz
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Donald Eastlake
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… John Levine
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… David Morris
- Re: Why the normative form of IETF Standards is A… Stefan Winter
- Re: Why the normative form of IETF Standards is A… Stefan Winter
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Ingemar Johansson S
- RE: Why the normative form of IETF Standards is A… Dearlove, Christopher (UK)
- Re: Why the normative form of IETF Standards is A… Dave Cridland
- Re: Why the normative form of IETF Standards is A… Arnt Gulbrandsen
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Andrew Sullivan
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Mark Andrews
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Rich Kulawiec
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… ned+ietf
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Jari Arkko
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Jari Arkko
- Re: Why the normative form of IETF Standards is A… Dave CROCKER
- Re: Why the normative form of IETF Standards is A… Jari Arkko
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Periodic debates Dave CROCKER
- Re: Periodic debates Jorge Amodio
- Re: Periodic debates Dave CROCKER
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Periodic debates Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is A… Lars Eggert
- Re: Why the normative form of IETF Standards is A… John R. Levine
- Re: I-Ds are not RFCs, was Why the normative form… John Levine
- Re: Why the normative form of IETF Standards is A… Tony Hansen
- Re: Why the normative form of IETF Standards is A… Richard Barnes
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is A… Dave Cridland
- Re: Why the normative form of IETF Standards is A… Bob Braden
- Re: Why the normative form of IETF Standards is A… John R. Levine
- Re: Why the normative form of IETF Standards is A… Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Arnt Gulbrandsen
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Marc Petit-Huguenin
- Re: Why the normative form of IETF Standards is A… Tony Finch
- Re: Why the normative form of IETF Standards is A… Tim Bray
- Re: Why the normative form of IETF Standards is A… John Levine
- Re: Why the normative form of IETF Standards is A… John Levine
- Re: Why the normative form of IETF Standards is A… Arnt Gulbrandsen
- Make HTML and PDF more prominent, was: Re: Why th… Iljitsch van Beijnum
- Re: Make HTML and PDF more prominent, was: Re: Wh… Dave Cridland
- Re: Make HTML and PDF more prominent, was: Re: Wh… Masataka Ohta
- Re: Make HTML and PDF more prominent, was: Re: Wh… Ole Jacobsen
- A state of spin ... presented in ASCII (was: Make… SM
- Re: Why the normative form of IETF Standards is A… Henning Schulzrinne
- Re: Make HTML and PDF more prominent, was: Re: Wh… todd glassey
- Re: Make HTML and PDF more prominent, was: Re: Wh… Michael Dillon
- Re: A state of spin ... presented in ASCII Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Bob Braden
- Re: Make HTML and PDF more prominent, was: Re: Wh… Iljitsch van Beijnum
- Re: A state of spin ... presented in ASCII todd glassey
- Re: Make HTML and PDF more prominent, was: Re: Wh… Martin Rex
- Re: A state of spin ... presented in ASCII Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Andrew Sullivan
- Re: Make HTML and PDF more prominent, was: Re: Wh… Peter Saint-Andre
- Re: Make HTML and PDF more prominent, was: Re: Wh… Randy Presuhn
- Re: Make HTML and PDF more prominent, was: Re: Wh… Martin Rex
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Melinda Shore
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: A state of spin ... presented in ASCII SM
- Re: A state of spin ... presented in ASCII Masataka Ohta
- Re: Make HTML and PDF more prominent, was: Re: Wh… Michael Dillon
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Make HTML and PDF more prominent, was: Re: Wh… Michael Dillon
- Re: Make HTML and PDF more prominent, was: Re: Wh… Donald Eastlake
- Re: Make HTML and PDF more prominent, was: Re: Wh… Tim Bray
- Re: A state of spin ... presented in ASCII Michael Dillon
- Re: Make HTML and PDF more prominent, was: Re: Wh… Bob Braden
- Re: Why the normative form of IETF Standards is A… Bob Braden
- Re: Why the normative form of IETF Standards is A… Tony Hansen
- Re: Make HTML and PDF more prominent, was: Re: Wh… Yoav Nir
- Re: Make HTML and PDF more prominent, was: Re: Wh… Yoav Nir
- Re: Make HTML and PDF more prominent, was: Re: Wh… Donald Eastlake
- Re: Why the normative form of IETF Standards is A… Andrew Sullivan
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: A state of spin ... presented in ASCII Doug Ewell
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Make HTML and PDF more prominent, was: Re: Wh… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Periodic debates Sean Turner
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: A state of spin ... presented in ASCII Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: A state of spin ... presented in ASCII Doug Ewell
- Re: Why the normative form of IETF Standards is A… Phillip Hallam-Baker
- RE: A state of spin ... presented in ASCII Wes Beebee (wbeebee)
- Re: Make HTML and PDF more prominent, was: Re: Wh… Dave Cridland
- Re: A state of spin ... presented in ASCII Phillip Hallam-Baker
- Re: Make HTML and PDF more prominent, was: Re: Wh… Martin Rex
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Masataka Ohta
- Using xml2rfc (was: Re: Why the normative form of… Doug Ewell
- Re: Why the normative form of IETF Standards is A… Doug Ewell
- Re: Using xml2rfc (was: Re: Why the normative for… Fred Baker
- Re: Why the normative form of IETF Standards is A… Stefan Santesson
- Re: Why the normative form of IETF Standards is A… Stefan Santesson
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- NroffEdit updated with December 2009 boilerplate Stefan Santesson
- Re: Why the normative form of IETF Standards is A… Stefan Santesson
- Re: Why the normative form of IETF Standards is A… Yoav Nir
- Re: Why the normative form of IETF Standards is A… Bill Fenner
- Re: Why the normative form of IETF Standards is A… Julian Reschke
- Re: Why the normative form of IETF Standards is A… Martin Rex
- Re: Why the normative form of IETF Standards is A… Stefan Santesson