[ire] NNDN for IDN and Language element

"Johnson, Scott" <scott.johnson@neustar.biz> Mon, 22 July 2013 13:57 UTC

Return-Path: <scott.johnson@neustar.biz>
X-Original-To: ire@ietfa.amsl.com
Delivered-To: ire@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC75921F8235 for <ire@ietfa.amsl.com>; Mon, 22 Jul 2013 06:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.186
X-Spam-Level:
X-Spam-Status: No, score=-4.186 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0zpXSWtO7xY for <ire@ietfa.amsl.com>; Mon, 22 Jul 2013 06:57:37 -0700 (PDT)
Received: from neustar.com (keys.neustar.biz [156.154.17.104]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1E211E80F0 for <ire@ietf.org>; Mon, 22 Jul 2013 06:57:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1374501633; x=1689856765; q=dns/txt; h=From:Subject:Date:Message-ID:Content-Language: Content-Type; bh=D2ttQRmlNex3Hj7YjuvFvzpV+Tq+De9+HsDKTeyf4xc=; b=D6mMesCcpM0WYqSphWtvZIyj7JTt7yv5Gcdy9wTBb6zV/b5fG+UL+GtcymHKBs aR/ffU6u9IyXtOS1B/CbC/2Q==
Received: from ([10.31.58.70]) by stihiron2.va.neustar.com with ESMTP with TLS id J041124103.27198149; Mon, 22 Jul 2013 10:00:32 -0400
Received: from STNTEXMB11.cis.neustar.com ([169.254.1.236]) by stntexhc11.cis.neustar.com ([::1]) with mapi id 14.02.0342.003; Mon, 22 Jul 2013 09:57:33 -0400
From: "Johnson, Scott" <scott.johnson@neustar.biz>
To: "'ire@ietf.org'" <ire@ietf.org>
Thread-Topic: NNDN for IDN and Language element
Thread-Index: Ac6G42m9pvfWzYFTR1uvkdAZ4cz27Q==
Date: Mon, 22 Jul 2013 13:57:32 +0000
Message-ID: <4983B690CFAC4D41A920459F919250850B56EABA@stntexmb11.cis.neustar.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.33.202.100]
x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA==
x-ems-stamp: VORwwQaFnNhb+oJrNaGYHg==
Content-Type: multipart/alternative; boundary="_000_4983B690CFAC4D41A920459F919250850B56EABAstntexmb11cisne_"
MIME-Version: 1.0
Subject: [ire] NNDN for IDN and Language element
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ire>, <mailto:ire-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ire>
List-Post: <mailto:ire@ietf.org>
List-Help: <mailto:ire-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ire>, <mailto:ire-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2013 13:57:42 -0000

Requirement:

An OPTIONAL <idnTableId> element that references the IDN Table
      used for the NNDN.  This corresponds to the "id" attribute of the
      <idnTableRef> element.  This element MUST be present if the NNDN
      is an IDN.


The IDNs that exist in the reserved domain table are canonical - the simplest possible form - and may be valid in multiple languages.  Since they are not actual registered domains submitted by a registrar, we don't know the intended language.

How should this be handled?

Thanks.