[provreg] Publishing of the IDN Table EPP Mapping IETF Draft

"Gould, James" <JGould@verisign.com> Thu, 05 February 2015 16:40 UTC

Return-Path: <JGould@verisign.com>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D57011A19F7; Thu, 5 Feb 2015 08:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 vHx_UgAmBmPR; Thu, 5 Feb 2015 08:40:45 -0800 (PST)
Received: from exprod6og126.obsmtp.com (exprod6og126.obsmtp.com [64.18.1.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DB1D1A89A7; Thu, 5 Feb 2015 08:40:45 -0800 (PST)
Received: from brn1lxmailout01.verisign.com ([72.13.63.41]) (using TLSv1) by exprod6ob126.postini.com ([64.18.5.12]) with SMTP ID DSNKVNOc+CsbphrMdfO3HlT2gcIngLM7/445@postini.com; Thu, 05 Feb 2015 08:40:45 PST
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t15GeNv0020190 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Feb 2015 11:40:23 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 5 Feb 2015 11:40:22 -0500
From: "Gould, James" <JGould@verisign.com>
To: "eppext@ietf.org" <eppext@ietf.org>, EPP Provreg <provreg@ietf.org>, "gtld-tech@icann.org" <gtld-tech@icann.org>
Thread-Topic: Publishing of the IDN Table EPP Mapping IETF Draft
Thread-Index: AQHQQWJumxRDFmqfz0eXkuVv273QPg==
Date: Thu, 05 Feb 2015 16:40:21 +0000
Message-ID: <96D1CC17-60A1-445A-8B2F-B56918E4D881@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_96D1CC1760A1445A8B2FB56918E4D881verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/provreg/9k90uCPzPGfdQaciJFnS8sEXqyo>
Subject: [provreg] Publishing of the IDN Table EPP Mapping IETF Draft
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>, <mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg/>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>, <mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 16:40:54 -0000

The first draft of the IDN Table EPP Mapping has been submitted to the IETF.  I co-authored this draft with Francisco Obispo and Luis Muñoz from Uniregistry to provide a mechanism for getting IDN Table information for the registration of IDNs, using the EPP domain name mapping, and optionally with the IDN mapping extension ( draft-ietf-eppext-idnmap ).  We would like this draft to be included in a re-charting of the EPPEXT Working Group.  The draft information is provided below.

URL:            http://www.ietf.org/internet-drafts/draft-gould-idn-table-00.txt
Status:         https://datatracker.ietf.org/doc/draft-gould-idn-table/
Htmlized:       http://tools.ietf.org/html/draft-gould-idn-table-00

Please review the draft and provide any feedback.

Thanks,


—


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

“This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”