Re: [eppext] what to do about IDN tables

Patrick Mevzek <pm@dotandco.com> Thu, 05 November 2015 00:55 UTC

Return-Path: <patrick@shaktot.patoche.org>
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 179F01A03A1 for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 16:55:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 c4NeQ-OAtZqQ for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 16:55:25 -0800 (PST)
Received: from shaktot.patoche.org (shaktot.patoche.org [212.85.152.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D858A1B350B for <eppext@ietf.org>; Wed, 4 Nov 2015 16:46:56 -0800 (PST)
Received: from shaktot.patoche.org (localhost.localdomain [127.0.0.1]) by shaktot.patoche.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id tA50kki8027097 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 5 Nov 2015 01:46:46 +0100
Received: (from patrick@localhost) by shaktot.patoche.org (8.14.3/8.14.3/Submit) id tA50kkHR027096; Thu, 5 Nov 2015 01:46:46 +0100
Date: Thu, 5 Nov 2015 01:46:44 +0100
From: Patrick Mevzek <pm@dotandco.com>
To: "Gould, James" <JGould@verisign.com>
Message-ID: <20151105004644.GA11762@home.patoche.org>
References: <563A7219.1050605@elistx.com> <973C1210-541C-46DC-8754-D06B1799DC4A@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <973C1210-541C-46DC-8754-D06B1799DC4A@verisign.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Scanned-By: shaktot_dot_patoche_dot_org on 212.85.152.86
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/V8MyhYA6YgGOFX2JKr2n_gR7DV8>
Cc: eppext <eppext@ietf.org>, James Galvin <galvin@elistx.com>
Subject: Re: [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: Thu, 05 Nov 2015 00:55:27 -0000

Gould, James <JGould@verisign.com> 2015-11-04 22:25
> I will be speaking to draft-gould-idn-table at meeting.
> I haven’t reviewed draft-wilcox-cira-idn-eppext, so I’m unsure of the overlap with draft-ietf-eppext-idnmap and draft-gould-idn-table.  

I've implemented draft-wilcox-cira-idn-eppext and plan to implement
draft-gould-idn-table which I have read already.

There is not so much overlap between them.

First, the terminology is not the same, as I've outlined in the past
here (repertoire vs table). It would maybe be a good idea if the WG can 
come to some terminology guidelines for IDNs so that at least various 
extensions are using the same words.

The CIRA extension is more closely related to the problem of variants,
and how one domain can block registration of another, so that one is 
able to query the server for one domain and having back the list of
variants.

I believe both extensions can advance forward independently from each
other.
But, if needed, draft-wilcox-cira-idn-eppext could use
draft-gould-idn-table as a terminology basis.

HTH,

-- 
Patrick Mevzek