Re: [idn] draft-ietf-idn-requirements-07.txt
Andrea Vine <avine@eng.sun.com> Thu, 21 June 2001 02:32 UTC
Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA00613 for <idn-archive@lists.ietf.org>; Wed, 20 Jun 2001 22:32:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1) id 15Ctf9-0003TV-00 for idn-data@psg.com; Wed, 20 Jun 2001 18:53:39 -0700
Received: from c3po.netscape.com ([205.217.237.46] helo=netscape.com) by psg.com with esmtp (Exim 3.16 #1) id 15Ctf8-0003Sd-00 for idn@ops.ietf.org; Wed, 20 Jun 2001 18:53:38 -0700
Received: from u-gotmail.red.iplanet.com (u-gotmail.red.iplanet.com [192.18.73.45]) by netscape.com (8.10.0/8.10.0) with ESMTP id f5L1qxY19277; Wed, 20 Jun 2001 18:52:59 -0700 (PDT)
Received: from eng.sun.com (h-192-18-127-177.red.iplanet.com [192.18.127.177]) by we-gotmail.red.iplanet.com (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTPS id <0GF9003GJ6DT41@we-gotmail.red.iplanet.com>; Wed, 20 Jun 2001 16:53:53 -0700 (PDT)
Date: Wed, 20 Jun 2001 16:52:27 -0700
From: Andrea Vine <avine@eng.sun.com>
Subject: Re: [idn] draft-ietf-idn-requirements-07.txt
To: Zita Wenzel <zita@ISI.EDU>, jseng@pobox.org.sg
Cc: idn@ops.ietf.org
Message-id: <3B31373B.395B8642@eng.sun.com>
MIME-version: 1.0
X-Mailer: Mozilla 4.7 [en]C-AOLNSCP (WinNT; U)
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
X-Accept-Language: fr,en,de,it,ja,ru
References: <200106192046.UAA12542@gin.isi.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit
Zita, James, A few minor comments and questions: 1.1 Definitions and Conventions 1-4 There is no ACR, CCS, CEF, or CES called Latin-15. If you mean ISO-8859-15, it is called Latin 9 (usually with no hyphen and often no space). 6. "...Examples: 8bit, Quoted-Printable, BASE64, UTF-7 (defunct), (UTF-5, and RACE)." Is UTF-7 defunct, or deprecated? Also, why are UTF-5 and RACE in parens? 2.2 Internationalization "[15] The protocol SHOULD NOT invent a new CCS for the purpose of IDN only and SHOULD use existing CES." ^an "[21] In order to retain backwards compatibility" ^^^^^^^^^ backward Andrea iPlanet i18n architect avine@eng.sun.com
- Re: [idn] draft-ietf-idn-requirements-07.txt Dan
- Re: [idn] draft-ietf-idn-requirements-07.txt Andrea Vine
- Re: [idn] draft-ietf-idn-requirements-07.txt Eric Brunner-Williams in Portland Maine
- Re: [idn] draft-ietf-idn-requirements-07.txt Dan
- Re: [idn] draft-ietf-idn-requirements-07.txt Florian Weimer
- Re: [idn] draft-ietf-idn-requirements-07.txt Paul Hoffman / IMC
- Re: [idn] draft-ietf-idn-requirements-07.txt Andrea Vine
- Re: [idn] draft-ietf-idn-requirements-07.txt Florian Weimer
- [idn] draft-ietf-idn-requirements-07.txt Zita Wenzel