- gtld-tech - lists.icann.org

TLD Name Server Software/Appliances
by Robert Smith Jan. 31, 2015

Jan. 31, 2015

Good evening, I'm trying to find/compile a list of name server software that the primary TLD servers use. I've found the root servers use BIND, with a few using NSD; is this about the same usage across TLD servers, as well? Or perhaps some TLDs use particular appliances instead? Thank you, - RS

4 3

draft-ietf-eppext-launchphase-03 Posted
by Gould, James Jan. 29, 2015

Jan. 29, 2015

All, The fourth draft of draft-ietf-eppext-launchphase (draft-ietf-eppext-launchphase-03) was posted to the IETF as what should be ready for Working Group Last Call by the EPPEXT Working Group. There is a dependency to draft-ietf-eppext-tmch-smd, so the hope is that draft-ietf-eppext-tmch-smd can be reposted for Working Group Last Call as well. The following is the draft information: URL: http://www.ietf.org/internet-drafts/draft-ietf-eppext-launchphase-03.txt Status: https://datatracker.ietf.org/doc/draft-ietf-eppext-launchphase/ Htmlized: http://tools.ietf.org/html/draft-ietf-eppext-launchphase-03 Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-eppext-launchphase-03 The following is a description of the changes from draft-ietf-eppext-launchphase-02 to draft-ietf-eppext-launchphase-03: 1. Added the "Implementation Status" section based on an action item from the eppext IETF-91 meeting. 2. Moved Section 7 "IANA Considerations" and Section 9 "Security Considerations" before Section 5 "Acknowledgements". Moved "Change Log" Section to end. 3. Updated the text for the Claims Check Form and the Claims Create Form to support checking for the need of the claims notice and passing the claims notice outside of the "claims" phase. 4. Added the new Trademark Check Form to support determining whether or not a trademark exists that matches the domain name independent of whether a claims notice is required on create. This was based on a request from Trung Tran and a discussion on the eppext mailing list. Please review draft-ietf-eppext-launchphase-03 and post any issues to the eppext mailing list. I want to thank everyone that has contributed to this draft version as well as all the past draft versions. 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

Re: [gtld-tech] Upcoming publication of updated Whois advisory
by Mats Dufberg Jan. 29, 2015

Jan. 29, 2015

Cyrus, Will it be possible to join that meeting remotely? If so, please send details to this list. Yours, Mats -- Mats Dufberg DNS Specialist, .SE (The Internet Infrastructure Foundation) Mobile: +46 73 065 3899 https://www.iis.se/en/ <http://www.iis.se/en> Från: Cyrus Namazi <cyrus.namazi(a)icann.org> Datum: Thursday 29 January 2015 02:07 Till: "gtld-tech(a)icann.org" <gtld-tech(a)icann.org> Kopia: Krista Papac <krista.papac(a)icann.org>, Mike Zupke <Mike.Zupke(a)icann.org>, Fabien Betremieux <fabien.betremieux(a)icann.org> Ämne: 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> Date: Friday, January 23, 2015 at 12:38 PM To: <gtld-tech(a)icann.org> Cc: Krista Papac <krista.papac(a)icann.org>, Mike Zupke <Mike.Zupke(a)icann.org>, Francisco Arias <francisco.arias(a)icann.org>, Fabien Betremieux <fabien.betremieux(a)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 www.icann.org

1 0

Upcoming publication of updated Whois advisory
by Cyrus Namazi Jan. 29, 2015

Jan. 29, 2015

Dear RrSG 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 www.icann.org

3 3

Final Call for Presentations for TechDay 53 at ICANN Singapore
by Dr Eberhard Lisse Jan. 27, 2015

Jan. 27, 2015

Hi, We have one 20 minute slot available for TechDay Singapore. The contact addresses are still: el(a)lisse.na and/or ondrej.filip(a)nic.cz or any of the lists this appears on, as I subscribe to them. greetings, el On 27/11/14 08:11, Dr Eberhard Lisse wrote: > > Hi, > > As usual we shall be organizing TechDay on Monday of the coming > ICANN meeting in Singapore. > > This time we are considering to try and demonstrate how to > generate DNSSEC keys in low cost smartcards which can be used in > openDNSSEC and the like. Not a signing ceremony proper, but with > a write-up so it is a step towards fully auditable procedures. > > We'll ask for a (or the same) room for Sunday (afternoon), so we > can practice :-)-O > > Please submit ideas for presentations to the list addresses where > this message appears or to any of the following email addresses: > > el(a)lisse.na ondrej.filip(a)nic.cz > > As we have a very small budget presenters are responsible for > their own transport and room and board, though we might be able to > assist the most riveting proposal :-)-O > > As the name suggests, talks must be of a technical (or > operational, perhaps even administrative) nature, and should > revolve around TLDs, but otherwise we are quite open. > > African participants are in particular encouraged to present, as > are of course Asians :-)-O > > Please forward this to gNSO and other lists as well :-)-O > > el > >

1 0

Re: [gtld-tech] WHOIS Clarification Advisory Scorecard
by Francisco Arias Jan. 16, 2015

Jan. 16, 2015

It seems I was missing text in row #7. Please use the attached. The only difference with v05 is adding one sentence in row #7. -- Francisco. On 1/7/15, 6:13 PM, "Francisco Arias" <francisco.arias(a)icann.org> wrote: >Dear colleagues, > >I’ve attached a scorecard with the list of issues that have been raised >and ICANN’s response. We provide rational in the cases in which we think >we should follow a different path than that proposed by the reporter(s) of >the issue. > >This is still a draft and we plan to host a conference call on next >Tuesday 13 January 2015 at 17:00 UTC for 60 minutes. We’ll share call >details in a separate email. > >Regards, > >-- >Francisco. >

2 3

WHOIS Clarification Advisory Scorecard
by Francisco Arias Jan. 8, 2015

Jan. 8, 2015

Dear colleagues, I’ve attached a scorecard with the list of issues that have been raised and ICANN’s response. We provide rational in the cases in which we think we should follow a different path than that proposed by the reporter(s) of the issue. This is still a draft and we plan to host a conference call on next Tuesday 13 January 2015 at 17:00 UTC for 60 minutes. We’ll share call details in a separate email. Regards, -- Francisco.

1 0

Whois advisory status
by Francisco Arias Dec. 22, 2014

Dec. 22, 2014

Dear colleagues, Just to let you know that ICANN is still reviewing the input received from you in writing and the teleconferences held this week. We plan to provide an status update in the first week of January. Best regards, -- Francisco.

2 1

Draft Updated WHOIS Clarification Advisory v.20141209
by Gustavo Lozano Dec. 21, 2014

Dec. 21, 2014

Hello colleagues, Attached you will find the Draft Updated WHOIS Clarification Advisory. Two versions are provided for your reference: clean version and redline against the original advisory (v 1.0) as published on 12 September 2014 (https://www.icann.org/resources/pages/registry-agreement-spec4-raa-rdds-201 4-09-12-en). This draft version incorporates feedback gathered from various contracted parties, cases/emails sent to ICANN, the WHOIS Clarification Advisory meeting held at IETF 91 in November, and feedback sent to the gtld-tech mailing list. A conference call, with the objective of gathering feedback on this draft version, will take place on Tuesday 16 December 2014. If you want to participate in the conference call, please send me an email to fabien.betremieux(a)icann.org. Please send any feedback or questions you have on this version of the advisory to the mailing list as soon as possible, in order for ICANN Staff to discuss internally and provide an answer during the conference call. It's important to remember: * This advisory is not meant to create new requirements for contracted parties. * This advisory is not meant to redefine the WHOIS protocol. * This advisory resulted from questions sent by contracted and third parties seeking clarification on the Whois (RDDS) requirements in the New gTLD base RA and 2013 RAA. Regards, Gustavo ICANN

11 19

Re: [gtld-tech] host attributes issue
by Loesje Hermans Dec. 16, 2014

Dec. 16, 2014

Dear Francisco, After the conf call on the WHOIS clarifications I would like to clarify the issues we experience with host attributes and the current specs from ICANN about WHOIS. Since we are using the host attributes instead of host objects, we do not have a sponsoring registrar for hosts. According to the spec 4 of the registry agreement we do need to output these data in case of a nameserver query. In case we have a domain name in the zone that holds glue for a certain host, we could use the data of the sponsoring registrar of that domain name to output in the results of the nameserver query. But that will definitely not be the case for every host. What to display for the fields ‘Registrar’, ‘WHOIS server’ and ‘Referral URL’ in those cases? We also have no ROIDs for hosts. That leaves us with the only option of implementing clarification 32 and return all matching records. This will look weird since we have no data to fill in except for the Server name and the IP Address. As mentioned before, we do not have sponsoring registrars so the rest of the output fields will remain empty or will not be shown. Registrars will be enforced to specify glue when they specify a nameserver in the same domain as the domain name. Therefor we can only have multiple matches when performing a WHOIS query on IP address. Wouldn’t it be more logic to show all possible server names without any other keys in this case? Since the search was on IP, it is not really needed to output this IP address in every record. It would shorten the output and narrow it down to the relevant information. Kind regards, Loesje Hermans Functional Analyst +32 16 29 89 23 DNS Belgium vzw/asbl Ubicenter - Philipssite 5, bus 13 - 3001 Leuven www.dnsbelgium.be<http://www.dnsbelgium.be/> [cid:09ee086c0b7e41ef0f09e359060c1a61f817d422@zimbra]

1 0