- gtld-tech - lists.icann.org

draft-ietf-eppext-launchphase-05 Posted
by Gould, James March 31, 2015

March 31, 2015

All, The sixth draft of draft-ietf-eppext-launchphase (draft-ietf-eppext-launchphase-05) was posted to the IETF to address the items discussed at the EPPEXT WG meeting to start the Working Group Last Call. The following is the draft information: The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eppext-launchphase/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eppext-launchphase-05 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-eppext-launchphase-05 The following is a description of the changes from draft-ietf-eppext-launchphase-04 to draft-ietf-eppext-launchphase-05: 1. Added a missing comma to the description of the <launch:phase> element, based on feedback from Keith Gaughan on the eppext mailing list. 2. Added the SIDN implementation status information. 3. Fixed a few indentation issues in the samples. Thanks, — JG [cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com] James Gould Distinguished Engineer jgould(a)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.” “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.”

1 0

Publishing of the IDN Table EPP Mapping IETF Draft
by Gould, James March 13, 2015

March 13, 2015

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(a)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.”

2 3

draft-ietf-eppext-tmch-smd-01 Posted
by Gustavo Lozano March 3, 2015

March 3, 2015

Hello colleagues, Version 01 of draft-ietf-eppext-tmch-smd was posted to the Internet-Draft repository. The draft is ready for Working Group Last Call (EPPEXT WG). The draft can be found here: https://tools.ietf.org/html/draft-ietf-eppext-tmch-smd-01 Your feedback is appreciated, please use the eppext mailing list. Regards, Gustavo

1 0

draft-ietf-eppext-launchphase-04 Posted
by Gould, James Feb. 27, 2015

Feb. 27, 2015

All, The fifth draft of draft-ietf-eppext-launchphase (draft-ietf-eppext-launchphase-04) was posted to the IETF to include the EPP Extension Registry section under the IANA Considerations. This draft is ready for Working Group Last Call by the EPPEXT Working Group. I support draft-ietf-eppext-tmch-smd moving to Working Group Last Call as well. The following is the draft information: URL: https://tools.ietf.org/id/draft-ietf-eppext-launchphase-04.txt<http://www.ietf.org/internet-drafts/draft-ietf-eppext-launchphase-03.txt> Status: https://datatracker.ietf.org/doc/draft-ietf-eppext-launchphase/ Htmlized: https://tools.ietf.org/html/draft-ietf-eppext-launchphase-04<http://tools.ietf.org/html/draft-ietf-eppext-launchphase-03> Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-eppext-launchphase-04<http://www.ietf.org/rfcdiff?url2=draft-ietf-eppext-launchphase-03> The following is a description of the changes from draft-ietf-eppext-launchphase-03 to draft-ietf-eppext-launchphase-04: 1. Amended XML Namespace section of IANA Considerations, added EPP Extension Registry section. Please review draft-ietf-eppext-launchphase-04 and post any issues to the eppext mailing list. Thanks, — JG [cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com] James Gould Distinguished Engineer jgould(a)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.” “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.”

1 0

Question on contact:chg / contact:postalInfo / contact:addr
by Volker Janzen Notify Feb. 25, 2015

Feb. 25, 2015

Hi all, I've a question regarding contact:addr inside of a contact:postalInfo block when using contact:chg. E.g. this XML snippet from RFC 5733 (excerpt only): C: <contact:chg> C: <contact:postalInfo type="int"> C: <contact:org/> C: <contact:addr> C: <contact:street>124 Example Dr.</contact:street> C: <contact:street>Suite 200</contact:street> C: <contact:city>Dulles</contact:city> C: <contact:sp>VA</contact:sp> C: <contact:pc>20166-6503</contact:pc> C: <contact:cc>US</contact:cc> C: </contact:addr> C: </contact:postalInfo> C: </contact:chg> contact:street may occur zero to three times. Is it intended that a single contact:street element should replace all existing contact:street elements or only the first contact:street element of the contact object? Volker Janzen Team Entwicklung -- InterNetX GmbH Maximilianstr. 6 93047 Regensburg Germany Tel: +49 941 59559-0 Fax: +49 941 59579-050 www.internetx.com www.facebook.com/InterNetX www.twitter.com/InterNetX Geschäftsführer/CEO: Thomas Mörz Amtsgericht Regensburg, HRB 7142 GPG-Key: 0x186C5F77 GPG-Fingerprint: 392E 8730 FE23 DCE8 8878 8524 5361 BCCC 186C 5F77

4 3

Publishing of the Change Poll EPP Extension 01 IETF Draft
by Gould, James Feb. 23, 2015

Feb. 23, 2015

The second draft of the Change Poll EPP Extension ( https://tools.ietf.org/html/draft-gould-change-poll-01 ) has been published to the IETF. This draft includes the following change: 1. Added an optional caseId element that defines the case identifier from UDRP, URS, or custom case, based on feedback from Michael Holloway. 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(a)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.”

1 0

draft-lozano-tmch-func-spec and QLP addendum
by Rik Ribbers Feb. 10, 2015

Feb. 10, 2015

Hello, I've got a question concerning the QLP addendum in relation to the IETF TMCH functional specification draft (http://tools.ietf.org/id/draft-lozano-tmch-func-spec-09.txt ) In section "5.4.1. Domain Registration" of the IEFT draft a decision table is provided the services a registry must provide for the QLP allocation scenarios. This table suggests that a QLP registration during sunrise must be validated against the DNL list and the SURL list. However in the QLP addendum it is only mentioned that a QLP registration during sunrise must be validated against the SURL list. I assume that the addendum is correct, but is that a correct assumption? Kind regards, Rik Ribbers

2 2

TechDay ICANN 52 Final Agenda
by Dr Eberhard W Lisse Feb. 7, 2015

Feb. 7, 2015

Kristina, please find enclosed the agenda, as promised. All, please distribute widely. We are particularly grateful for ICANN IT staff to be available for an Adobe Connect Hands-On training. Anyone who has telephone issues when participating in conferences using Adobe Connect might benefit from learning how to use Adobe Connect's Audio facilities (two-ways). greetings, el

1 0

Adobe Connect Hands On Session at ICANN Singapore TechDay
by Dr Eberhard W Lisse Feb. 3, 2015

Feb. 3, 2015

Hi, we shall have us an Adobe Connect Hands on session over lunch (13:00) on Monday at TechDay ICANN Singapore in the Olivia Room thanks to ICANN IT staff. In particular would I like to make the feature known that one can interact with the conference call bridge by way of "connecting audio". This is helpful for those who find themselves in a situation of poor telephone reachability but with acceptable Internet connectivity as a fail-safe. I would appreciate if you could circulate this to lists and individuals who you think may benefit of this session. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Bachbrecht, Namibia ;____/

1 0

Re: [gtld-tech] Upcoming publication of updated Whois advisory
by Francisco Arias Feb. 2, 2015

Feb. 2, 2015

Colleagues, The meeting will be held on 11 February from 16:15 to 17:30 UTC+8 (Singapore time) in Moor room during the ICANN meeting in Singapore. Remote participation will be available as follows. https://icann.adobeconnect.com/whois_clar_icann52/ Phone access numbers can be found at https://mtginfo.pgi.com/globalcallmanagement.asp?bwebid=9820041&cid=da6de6b… or in the attached PDF. Access code: 1619764184. Regards, -- Francisco. On 1/28/15, 11:47 PM, "Alexander Mayrhofer" <alexander.mayrhofer(a)nic.at<mailto:alexander.mayrhofer@nic.at>> wrote: Cyrus, Thank you for that information. Can you elaborate in which session the advisory will be discussed during the ICANN meeting? I’d highly interested in joining that. thanks, Alex Von: gtld-tech-bounces(a)icann.org<mailto:gtld-tech-bounces@icann.org> [mailto:gtld-tech-bounces@icann.org] Im Auftrag von Cyrus Namazi Gesendet: Donnerstag, 29. Jänner 2015 02:07 An: gtld-tech(a)icann.org<mailto:gtld-tech@icann.org> Cc: Krista Papac; Mike Zupke; Fabien Betremieux Betreff: Re: [gtld-tech] Upcoming publication of updated Whois advisory Dear all; Following further correspondence and additional feedback from some of the stakeholders, we will hold off on publishing this advisory until after our face-to-face meeting at ICANN 52 in Singapore. Cheers, Cyrus Namazi ICANN From: Cyrus Namazi <cyrus.namazi(a)icann.org<mailto:cyrus.namazi@icann.org>> Date: Friday, January 23, 2015 at 12:38 PM To: <gtld-tech(a)icann.org<mailto:gtld-tech@icann.org>> Cc: Krista Papac <krista.papac(a)icann.org<mailto:krista.papac@icann.org>>, Mike Zupke <Mike.Zupke(a)icann.org<mailto:Mike.Zupke@icann.org>>, Francisco Arias <francisco.arias(a)icann.org<mailto:francisco.arias@icann.org>>, Fabien Betremieux <fabien.betremieux(a)icann.org<mailto:fabien.betremieux@icann.org>> Subject: Upcoming publication of updated Whois advisory Dear RySG and RrSG members and colleagues, Attached please find the Whois advisory scorecard identifying those issues raised during ICANN’s numerous consultations with various interested parties over the course of the previous several months. The scorecard contains (among other things) a description of the issue raised and ICANN’s response. I thank the group members for their valuable contributions throughout these discussions. We have updated the draft advisory on those issues where there was room for interpretation. There are a small number of issues (three) that we think the Whois specifications do not allow for the changes some of you have proposed (rows 3, 8, and 15 of the attached scorecard). Consequently, there are only three issues in which we found no option but to maintain the current Whois advisory language. ICANN intends to publish a final advisory by the end of January with an implementation date of 31 July 2015, providing contracted parties ample time to implement any necessary changes. Thank you again for your time and your constructive inputs. Please let us know should you have any further questions or comments. Cheers, Cyrus Namazi Vice President | Domain Name Services | Global Domains Division 801 17th St NW, Suite 400 | Washington, DC 20006 USA +1.202.249.7543 Office | +1.408.421.6894 Mobile | cyrus.namazi(a)icann.org<mailto:cyrus.namazi@icann.org> www.icann.org<http://www.icann.org>

1 1