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; Sat, 12 Feb 2005 23:03:49 +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 99261621C1; Sat, 12 Feb 2005 23:03:48 +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 14949-01; Sat, 12 Feb 2005 23:03:42 +0100 (CET) Received: from eikenes.alvestrand.no (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 5675761DEA; Sat, 12 Feb 2005 23:03:36 +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 7C6F361C31 for ; Sat, 12 Feb 2005 23:03:33 +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 14803-04 for ; Sat, 12 Feb 2005 23:03:31 +0100 (CET) Received: from pechora.icann.org (pechora.icann.org [192.0.34.35]) by eikenes.alvestrand.no (Postfix) with ESMTP id 5CFB761B9D for ; Sat, 12 Feb 2005 23:03:30 +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 j1CM2qq08630 for ; Sat, 12 Feb 2005 14:02:52 -0800 Received: from lns-p19-8-idf-82-65-67-203.adsl.proxad.net ([82.65.67.203] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1D05ML-0003yy-Dy; Sat, 12 Feb 2005 14:03:26 -0800 Message-Id: <6.1.2.0.2.20050212143117.04d42510@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Sat, 12 Feb 2005 15:21:46 +0100 To: "Peter Constable" , From: "JFC (Jefsey) Morfin" In-Reply-To: References: Mime-Version: 1.0 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: Subject: RE: LANGUAGE TAG REGISTRATION FORM: mn-Mong-CN 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: , Content-Type: multipart/mixed; boundary="===============0596612777==" Sender: ietf-languages-bounces@alvestrand.no Errors-To: ietf-languages-bounces@alvestrand.no X-Virus-Scanned: by amavisd-new at alvestrand.no --===============0596612777== Content-Type: multipart/alternative; boundary="=====================_226458730==.ALT" --=====================_226458730==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 10:39 12/02/2005, Peter Constable wrote: >"The important thing for us is not to establish precisely what every >distinction is (an endless task involving an ever-changing domain over >which different interpretations are possible), but rather to ensure that >the intended meaning of any tag is understood by all and for which it is >clear, to some minimal level, how to utilize it." IANA registrations are for computers to use. There are no minimal level, there is a yes/no. With the lang3tag this understanding concerns the whole language without graduated level nor different possible interpretations. To match your pragmatic remark from your experience of reality I proposed (and we start using) the lang5tag format where levels and interpretations are included as styles and authority (because computers like positive rather than controvertible language). jfc PS. Some information on what is the IANA function may be of use. Confusion over the purpose of the IANA registrations would only push for this function to be reassigned and would only add to the pressures or decisions towards its management by a more widely accepted structure. http://ietf.org/overview.html "The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols. The IANA is chartered by the Internet Society (ISOC) to act as the clearinghouse to assign and coordinate the use of numerous Internet protocol parameters." http://www.icann.org/general/iana-contract-09feb00.htm NTIA has a requirement for a contractor to maintain the smooth operation of the Internet by performing the technical functions collectively known as the Internet Assigned Numbers Authority (IANA). The IANA technical functions are currently operated by the Information Sciences Institute at the University of Southern California pursuant to a contract with the Department of Defense's Advanced Research Projects Agency. In performance of this purchase order, the contractor shall perform the following IANA functions: - Coordination of the assignment of technical protocol parameters. This involves the review and assignment of unique values to various parameters (e.g., operation codes, port numbers, object identifiers, protocol numbers) used in various Internet protocols. This function also includes the dissemination of the listings of assigned parameters through various means (including on-line publication) and the review of technical documents for consistency with assigned values. - Administrative functions associated with root management. This function involves facilitation and coordination of the root zone of the domain name system. It includes receiving requests for and making routine updates of ccTLD contact and nameserver information. It also includes receiving delegation and redelegation requests, investigating the circumstances pertinent to those requests, and reporting on the requests. This function, however, does not include authorizing modifications, additions, or deletions to the root zone file or associated information that constitute delegation or redelegation of top-level domains. The purchase order award will not alter root system responsibilities defined in Amendment 11 of the Cooperative Agreement. - Allocation of IP address blocks. This involves overall responsibility for the allocation of IPv4 and IPv6 address space. It includes delegations of IP address blocks to regional registries for routine allocation, typically through downstream providers, to Internet end-users within the regions served by those registries. It also includes reservation and direct allocation of space for special purposes, such as multicast addressing, cable blocks, addresses for private networks as described in RFC 1918, and globally specified applications. - Other services. The contractor will perform other IANA functions as needed upon request of DOC. These functions may include the performance of periodic functions or supplemental functions identified by the contractor as part of the three (3) month performance progress report. --=====================_226458730==.ALT Content-Type: text/html; charset="us-ascii" At 10:39 12/02/2005, Peter Constable wrote:
"The important thing for us is not to establish precisely what every distinction is (an endless task involving an ever-changing domain over which different interpretations are possible), but rather to ensure that the intended meaning of any tag is understood by all and for which it is clear, to some minimal level, how to utilize it."

IANA registrations are for computers to use. There are no minimal level, there is a yes/no. With the lang3tag this understanding concerns the whole language without graduated level nor different possible interpretations. To match your pragmatic remark from your experience of reality I proposed (and we start using) the lang5tag format where levels and interpretations are included as styles and authority (because computers like positive rather than controvertible language).
jfc

PS. Some information on what is the IANA function may be of use. Confusion over the purpose of the IANA registrations would only push for this function to be reassigned and would only add to the pressures or decisions towards its management by a more widely accepted structure.

http://ietf.org/overview.html
"The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols. The IANA is chartered by the Internet Society (ISOC) to act as the clearinghouse to assign and coordinate the use of numerous Internet protocol parameters."

http://www.icann.org/general/iana-contract-09feb00.htm
NTIA has a requirement for a contractor to maintain the smooth operation of the Internet by performing the technical functions collectively known as the Internet Assigned Numbers Authority (IANA). The IANA technical functions are currently operated by the Information Sciences Institute at the University of Southern California pursuant to a contract with the Department of Defense's Advanced Research Projects Agency. In performance of this purchase order, the contractor shall perform the following IANA functions:

- Coordination of the assignment of technical protocol parameters. This involves the review and assignment of unique values to various parameters (e.g., operation codes, port numbers, object identifiers, protocol numbers) used in various Internet protocols. This function also includes the dissemination of the listings of assigned parameters through various means (including on-line publication) and the review of technical documents for consistency with assigned values.

- Administrative functions associated with root management. This function involves facilitation and coordination of the root zone of the domain name system. It includes receiving requests for and making routine updates of ccTLD contact and nameserver information. It also includes receiving delegation and redelegation requests, investigating the circumstances pertinent to those requests, and reporting on the requests. This function, however, does not include authorizing modifications, additions, or deletions to the root zone file or associated information that constitute delegation or redelegation of top-level domains. The purchase order award will not alter root system responsibilities defined in Amendment 11 of the Cooperative Agreement.

- Allocation of IP address blocks. This involves overall responsibility for the allocation of IPv4 and IPv6 address space. It includes delegations of IP address blocks to regional registries for routine allocation, typically through downstream providers, to Internet end-users within the regions served by those registries. It also includes reservation and direct allocation of space for special purposes, such as multicast addressing, cable blocks, addresses for private networks as described in RFC 1918, and globally specified applications.

- Other services. The contractor will perform other IANA functions as needed upon request of DOC. These functions may include the performance of periodic functions or supplemental functions identified by the contractor as part of the three (3) month performance progress report.

--=====================_226458730==.ALT-- --===============0596612777== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ietf-languages mailing list Ietf-languages@alvestrand.no http://www.alvestrand.no/mailman/listinfo/ietf-languages --===============0596612777==--