[eppext] what to do about IDN tables

James Galvin <galvin@elistx.com> Wed, 04 November 2015 21:00 UTC

Return-Path: <galvin@elistx.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 684611A6FAC for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 13:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TmFvrW_zNPi2 for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 13:00:44 -0800 (PST)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3138C1A6F82 for <eppext@ietf.org>; Wed, 4 Nov 2015 13:00:44 -0800 (PST)
Received: by qkcl124 with SMTP id l124so25107909qkc.3 for <eppext@ietf.org>; Wed, 04 Nov 2015 13:00:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elistx_com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-type:content-transfer-encoding; bh=3bpGpwY2C83J3/42vFYMcyupFP7JE4uzgZP5WpzZw60=; b=qmUft8w2tXvfiSU5abPn/7YmQoQdMufDfhg7Ewwxl1HfT88ZijoxjdyoTbX2lO70AN yMhI27g7hwTXa1Ym6Fcdxi9h0jrMhPzK6yk6Ra358xiMUlQlDabLkLI5+7bvloI1ufIk M5ISfjFKCloeml/RLe4ffh38fgD8+y6cV4PI1oTu9Y+VviTM8YggiS234AAwkX3yrhiB 5LndqTP20MIMtR8hKqHZ4e31tbIPx0QW6tlGV1Gj/ROlevZAwQ5EKd6030laogDYCtgW vGDZsxhnWToYH2epCFjYJbsgtY4FIIzO4wV6b6fy6WRnrZLdz42JdmFvGnReWrxsF2DH D/kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-type:content-transfer-encoding; bh=3bpGpwY2C83J3/42vFYMcyupFP7JE4uzgZP5WpzZw60=; b=Dja5SLrjbrlhErMggJ5TPBmEGSJ5QY8xE57hwC4YqTRrs3rfXea2cZYfrDNMdezrvw 72LxdKNbys5uo4KvmxL+uINmesS5uHOewFkIugRHf3bRd3r+NSK2nvGSrtBqCFKqGo35 EATOoXNdSgwcmSkvGD3z3tzKcYpRpJuup7F4JHg5hUYa4tejOAmu8c2NyDVSrp3/jQek nZ1CvUfr01Wx6w5N+7D8NjUYwIR0qdtr/hxxTVcJbkJzXVPnv9hUKEWYG3vIybRZ4vPd 9S4EhyGvjIbhcnHRE2EcbURpavlvMWkIVXK8j16pikcJ+NBcxxt/T7LTTiyLB+adL2VC XZsA==
X-Gm-Message-State: ALoCoQk2wPU6Hhq/2qxO47vbfTpvjyU0W0TYjSoNuQRIyh40pd7pJCL8oFW5T726n5IY0beq1hHn
X-Received: by 10.55.78.195 with SMTP id c186mr3832673qkb.41.1446670843273; Wed, 04 Nov 2015 13:00:43 -0800 (PST)
Received: from jgalvin-lt.local (c-73-133-108-218.hsd1.md.comcast.net. [73.133.108.218]) by smtp.googlemail.com with ESMTPSA id m23sm785969qkh.46.2015.11.04.13.00.42 for <eppext@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Nov 2015 13:00:42 -0800 (PST)
To: eppext <eppext@ietf.org>
From: James Galvin <galvin@elistx.com>
Message-ID: <563A7219.1050605@elistx.com>
Date: Wed, 4 Nov 2015 16:01:13 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/BGUaNKYCLUqpb9u3ey_qbF2trfQ>
Subject: [eppext] what to do about IDN tables
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2015 21:00:45 -0000

A question that will be asked in the working group meeting today is what 
to do about IDN tables?

There is a working group document that has recently expired:

draft-ietf-eppext-idnmap/

This document is languishing because Francisco has not gotten the 
required implementation statements yet.  We can certainly revive it but 
we may need to consider moving forward with incomplete implementation 
reports.

In addition, there were two related individual submissions that have 
also recently expired:

draft-gould-idn-table/
draft-wilcox-cira-idn-eppext/

These three documents are not all the same but they are related.  The 
question is how to move forward.

Are Gould and Wilcox withdrawing their documents?  Are they going to 
seek publication in the EPP Extensions Registry?

If they want to seek being adopted by the working group then we will 
need to address the apparent relationship with the existing working 
group document.

Comments and suggestions are welcome.

Thanks,

Jim