Return-Path: Received: from eikenes.alvestrand.no ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.1.11-Mandrake-RPM-2.1.11-1mdk) with LMTP; Sun, 09 Jan 2005 03:10:17 +0100 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3EB7161B8E; Sun, 9 Jan 2005 03:10:17 +0100 (CET) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18592-06; Sun, 9 Jan 2005 03:10:16 +0100 (CET) Received: from eikenes.alvestrand.no (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2DC2161B93; Sun, 9 Jan 2005 03:10:12 +0100 (CET) X-Original-To: ietf-languages@alvestrand.no Delivered-To: ietf-languages@alvestrand.no Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6555261B7D for ; Sun, 9 Jan 2005 03:10:10 +0100 (CET) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18592-03 for ; Sun, 9 Jan 2005 03:10:08 +0100 (CET) Received: from pechora.icann.org (pechora.icann.org [192.0.34.35]) by eikenes.alvestrand.no (Postfix) with ESMTP id AA51461AD4 for ; Sun, 9 Jan 2005 03:10:07 +0100 (CET) Received: from montage.altserver.com (montage.altserver.com [63.247.74.122]) by pechora.icann.org (8.11.6/8.11.6) with ESMTP id j0929n420475 for ; Sat, 8 Jan 2005 18:09:49 -0800 Received: from lns-p19-19-idf-82-249-7-129.adsl.proxad.net ([82.249.7.129] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.43) id 1CnSWq-0006UZ-4Q; Sat, 08 Jan 2005 18:10:04 -0800 Message-Id: <6.1.2.0.2.20050109021836.043c86a0@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Sun, 09 Jan 2005 03:09:58 +0100 To: "Mark Davis" From: "JFC (Jefsey) Morfin" In-Reply-To: <0b8601c4f5da$6c39a7d0$46733009@sanjose.ibm.com> References: <0b8601c4f5da$6c39a7d0$46733009@sanjose.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed; x-avg-checked=avg-ok-70A55B10 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - iana.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: by amavisd-new at alvestrand.no Cc: ietf-languages@iana.org Subject: Re: Language tags, the phillips draft, and procedures X-BeenThere: ietf-languages@alvestrand.no X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Language tag discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ietf-languages-bounces@alvestrand.no Errors-To: ietf-languages-bounces@alvestrand.no X-Virus-Scanned: by amavisd-new at alvestrand.no On 00:33 09/01/2005, Mark Davis said: >I believe that what Misha was trying to do with this message was not to try >to pressure for special treatment in any way. Instead it was to address the >issue voiced by some on this list, that "there is not much support" for >3066bis. In fact there is a great deal of support; a large number of people, >companies, and organizations are in favor of it. In particular, both the W3C >and Unicode committees are strongly in favor. (And if the IETF wants >official liaison statements to that effect, that could easily be >forthcoming). Dear Mark, As expressed many times, I fully support the Draft too, provided (a) it is restricted to the areas where it is currently used, and further on to new areas only after being discussed new area per new area - what Addison refused (b) that registrations are carried in a standard IETF way through an IETF WG with an IAB appoved charter warranting network architecture consistency. Would this draft be accepted as a global BCP it would conflict with my own needs the way I understand them (but I may be wrong) if are not included in the tag: (a) the language usage framework (b) the language authoritative reference (so there may be as many tags for a same language, for a same scripting and for a same country as needed to cover the requirements/specifics of the concerned usages and parties). As I indicated to Misha, what would really help would be a list of motivated support from IAB, Chairs of the IETF WGs from the different concerned areas, and non-English or non-American mother tongue involved network experts or authorities. Support from some leading persons of organizations or entities such as MINC, ITU, WSIS and UNESCO, from ETSI or GAC, from WTO and WIPO, would obviously help clarifying things a lot. Again, I oppose nothing, but I do not want us to make a big mistake. jfc _______________________________________________ Ietf-languages mailing list Ietf-languages@alvestrand.no http://www.alvestrand.no/mailman/listinfo/ietf-languages