[76all] On the Technical Plenary

"Stephanie McCammon" <smccammon@amsl.com> Thu, 12 November 2009 05:16 UTC

Return-Path: <smccammon@amsl.com>
X-Original-To: 76all@core3.amsl.com
Delivered-To: 76all@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73F593A68E6 for <76all@core3.amsl.com>; Wed, 11 Nov 2009 21:16:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 QZJNaHnnlISk for <76all@core3.amsl.com>; Wed, 11 Nov 2009 21:16:34 -0800 (PST)
Received: from mail.amsl.com (unknown [IPv6:2001:1890:1112:1::14]) by core3.amsl.com (Postfix) with ESMTP id B21AD3A6875 for <76all@ietf.org>; Wed, 11 Nov 2009 21:16:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id BEECCE0831 for <76all@ietf.org>; Wed, 11 Nov 2009 21:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjZUzw1yjLYd for <76all@ietf.org>; Wed, 11 Nov 2009 21:17:03 -0800 (PST)
Received: from ams3mxglf1 (host-24-26.meeting.ietf.org [133.93.24.26]) by c1a.amsl.com (Postfix) with ESMTPA id 40595E07FA for <76all@ietf.org>; Wed, 11 Nov 2009 21:17:03 -0800 (PST)
From: Stephanie McCammon <smccammon@amsl.com>
To: 76all@ietf.org
Date: Thu, 12 Nov 2009 14:16:59 +0900
Message-ID: <68F7D251898244C98EA48410BEFAB01A@ams3mxglf1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-index: AcpiwOUTohNxzppSSQKEijSrLko/9QAleORQ
Subject: [76all] On the Technical Plenary
X-BeenThere: 76all@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: smccammon@amsl.com
List-Id: <76all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/76all>, <mailto:76all-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/76all>
List-Post: <mailto:76all@ietf.org>
List-Help: <mailto:76all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/76all>, <mailto:76all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2009 05:16:35 -0000

IETF 76 Technical Plenary, 1630-1930 Thursday 12th November 2009.

Internationalization in
 Names and Other Identifiers


This technical plenary can be seen as following on from the plenary at
IETF68 on March 2007 in Prague on "Internationalization and Internet
Engineering" and builds on an old realization that smooth and interoperable
functioning&#8232; of the Internet depends on text strings&#8232; being
interpreted in the same way &#8232;by all systems connected to it. RFC 2277
(IETF Policy on Character Sets and Languages, January 1998) and RFC 5198
(Unicode Format for Network Interchange, March
2008) discuss the use of international text in Internet protocols.

Internationalization of protocol elements is ongoing work within the IETF
(e.g. IDNABIS WG, EAI WG, IRI BOF) and deployment of these technologies is
ongoing. For example, there has been much publicity and excitement around
the announcement that ICANN plans to start issuing international text
country-code top level domains soon. 

The issues and complexities of handling international text affect many of
our protocols, most Internet users, and many IETF Working Groups. However,
the issues are complicated and there is not always a shared understanding
even among experts in the field.

This IETF Technical Plenary presentation will explore examples of the kinds
of things that can go wrong with internationalized text, and examples of
cases where even when things go "right", the result may still not be what
the average human might expect or want. The IAB is currently working on
draft-iab-idn-encoding, with the goal of describing some of the important
issues and problems, and giving guidance for future protocol design to
reduce such problems.

This plenary is a working session of the IAB where we want to share our
experiences and learn from yours.


For the IAB,
  Olaf Kolkman, Chair.
_______________________________________________