December 2014 - Gnso-impl-irtpc-rt

Save the Date - Next IRTP-C IRT Call Thurs 8 Jan 2015 at 1700 UTC
by Caitlin Tubergen Dec. 22, 2014

Dec. 22, 2014

Hi All, Thank to those who responded to the request for alternatives to exchanging pins via email. During our next call, I would like to take some time to discuss the alternatives that IRT members suggested to get around the problem presented during our last call. I plan to go through all of the suggestions in a short presentation and then let the IRT discuss how it proposes to move forward. If you have any other suggestions in the meantime, please feel free to email me. Details for our next call appear below: Details for 8 January 2015 Call The next Inter-Registrar Transfer Policy (IRTP) Part C Implementation Review Team teleconference is scheduled for Thursday 8 January 2014 at 17:00 UTC. 09:00 PST, 12:00 EST, 17:00 London, 17:00 CET, 03:00 (+1 day) Sydney. Link to Adobe Connect (with audio enabled):https://icann.adobeconnect.com/irtppartc/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers:https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=6458688446&num =1-719-457-6209 <https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=6458688446&num=1-719- 457-6209> Participant Passcode: 6458688446 I hope everyone has a wonderful holiday season. Kind regards, and happy holidays, Caitlin

1 0

Outstanding Issue from today's IRT Call (email/account holder)
by Caitlin Tubergen Dec. 20, 2014

Dec. 20, 2014

Hi, All, Thank you to everyone who attended the call; it was a very robust discussion. For those who were unable to attend, I have attached instructions on how to listen to the recording. At the start of the call, I presented a scenario whereby a Prior Registrant would be unable to ACK/affirm a Change of Registrant request (COR) request because their email account no longer exists. (Perhaps they left their company, university, etc.) Similarly, if someone were to move and suddenly have a new address, telephone, email address, ISP provider, it would be impossible to ACK a COR via email, postal mail, phone, etc. While this is narrow use case, ICANN staff and the IRT are trying to ensure that we are not creating an unworkable scenario where a Prior Registrant cannot update his or her email address. Section 3.4 of the draft COR Policy would allow a registrant to log into their account and update their information via their verified account. This gets around the non-existent email address issue, but some have expressed concerns about the risk of hijacking since resellers, hosting providers, et. al., may be an account holder. ICANN staff is currently seeking solutions to the problem mentioned above. Specifically, we are looking for alternative authentication methods besides the exchange of pin. A couple of suggestions mentioned on the call include: 1. FOAs for change of registrant. (The Prior Registrant would receive an informative FOA at its email address (listed in Whois) and if it doesn¹t contact the registrar within a certain number of days, the email change would go through.) 2. Alternative authentication depending on the type of registrant change, i.e., a different authentication method could be used if the name is staying in the same account rather than a ³push² between accounts Please feel free to elaborate on the above or provide new suggestions entirely. We discussed the difficulty with the resolution of this particular problem and how this may need to back to the GNSO for more guidance if it cannot be resolved within the IRT, particularly since the IRT is not a representative body of the ICANN community. Please provide any suggestions to me by COB Thursday, 18 December. Thank you in advance for your feedback. Kind regards, Caitlin

3 6

Re: [gnso-impl-irtpc-rt] Save the Date: IRTP-C Implementation Review Team Call 11 Dec 2014
by James M. Bladel Dec. 11, 2014

Dec. 11, 2014

Mikey & Theo: Totally agree. This was discussed on the last call (or at least, the last call I attended). It is a giant loophole that undermines the entire intent and we must find a way to close it. Thanks— J. From: Theo Geurts <theo.geurts(a)firstfind.nl<mailto:theo.geurts@firstfind.nl>> Date: Thursday, December 11, 2014 at 6:47 To: Mike O'Connor <mike(a)haven2.com<mailto:mike@haven2.com>> Cc: Caitlin Tubergen <caitlin.tubergen(a)icann.org<mailto:caitlin.tubergen@icann.org>>, Barbara Knight <BKnight(a)verisign.com<mailto:BKnight@verisign.com>>, Leticia Castillo <leticia.castillo(a)icann.org<mailto:leticia.castillo@icann.org>>, James Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>, Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, Gisella Gruber <Gisella.Gruber(a)icann.org<mailto:Gisella.Gruber@icann.org>>, Arthur Zonnenberg <azonnenberg(a)hostnet.nl<mailto:azonnenberg@hostnet.nl>>, Phil Corwin <psc(a)vlaw-dc.com<mailto:psc@vlaw-dc.com>>, Lars Hoffmann <lars.hoffmann(a)icann.org<mailto:lars.hoffmann@icann.org>>, "gnso-impl-irtpc-rt(a)icann.org<mailto:gnso-impl-irtpc-rt@icann.org>" <gnso-impl-irtpc-rt(a)icann.org<mailto:gnso-impl-irtpc-rt@icann.org>>, Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>, Terri Agnew <terri.agnew(a)icann.org<mailto:terri.agnew@icann.org>>, "Sedo :: Simonetta Batteiger" <simonetta(a)sedo.com<mailto:simonetta@sedo.com>>, Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>>, Rob Golding <rob.golding(a)astutium.com<mailto:rob.golding@astutium.com>>, Michele Neylon - Blacknight <michele(a)blacknight.com<mailto:michele@blacknight.com>>, Mike Zupke <Mike.Zupke(a)icann.org<mailto:Mike.Zupke@icann.org>>, Bob Mountain <bmountain(a)godaddy.com<mailto:bmountain@godaddy.com>> Subject: Re: [gnso-impl-irtpc-rt] Save the Date: IRTP-C Implementation Review Team Call 11 Dec 2014 Thanks Mike, Being the one that raised this issue a few times, i decided to write a lil FAQ for our resellers, incase 3.2 would apply. I give up after an hour or so, i could not come up with a scenario where 3.4 did NOT apply. So for me to carry out this PDP in it's current language as a registrar, is pretty easy, as i would have to do nothing at all. I can't speak for other registrars but i would assume more of us would be in the same boat. So yes, this needs to be addressed one way or another. Talk to you folks on the call. Best regards, Theo Geurts Compliance Officer Realtime Register B.V. Ceintuurbaan 32A 8024 AA - ZWOLLE - The Netherlands T: +31.384530759 F: +31.384524734 U: www.realtimeregister.com E: support(a)realtimeregister.com<mailto:support@realtimeregister.com> ________________________________ Van: "Mike O'Connor" <mike(a)haven2.com<mailto:mike@haven2.com>> Aan: "Caitlin Tubergen" <caitlin.tubergen(a)icann.org<mailto:caitlin.tubergen@icann.org>> Cc: "Theo Geurts" <theo.geurts(a)firstfind.nl<mailto:theo.geurts@firstfind.nl>>, "Barbara Knight" <BKnight(a)verisign.com<mailto:BKnight@verisign.com>>, "Leticia Castillo" <leticia.castillo(a)icann.org<mailto:leticia.castillo@icann.org>>, "James Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>, "Marika Konings" <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, "Gisella Gruber" <Gisella.Gruber(a)icann.org<mailto:Gisella.Gruber@icann.org>>, "Arthur Zonnenberg" <azonnenberg(a)hostnet.nl<mailto:azonnenberg@hostnet.nl>>, "Phil Corwin" <psc(a)vlaw-dc.com<mailto:psc@vlaw-dc.com>>, "Lars Hoffmann" <lars.hoffmann(a)icann.org<mailto:lars.hoffmann@icann.org>>, gnso-impl-irtpc-rt(a)icann.org<mailto:gnso-impl-irtpc-rt@icann.org>, "Steve Chan" <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>, "Terri Agnew" <terri.agnew(a)icann.org<mailto:terri.agnew@icann.org>>, "Sedo :: Simonetta Batteiger" <simonetta(a)sedo.com<mailto:simonetta@sedo.com>>, "Nathalie Peregrine" <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>>, "Rob Golding" <rob.golding(a)astutium.com<mailto:rob.golding@astutium.com>>, "Michele Neylon - Blacknight" <michele(a)blacknight.com<mailto:michele@blacknight.com>>, "Mike Zupke" <Mike.Zupke(a)icann.org<mailto:Mike.Zupke@icann.org>>, "Bob Mountain" <bmountain(a)godaddy.com<mailto:bmountain@godaddy.com>> Verzonden: Donderdag 11 december 2014 14:16:14 Onderwerp: Re: [gnso-impl-irtpc-rt] Save the Date: IRTP-C Implementation Review Team Call 11 Dec 2014 dear all, sorry to respond to this note within hours of the meeting. but i wanted to let you know that i’ll be strenuously opposing Section 3.4 as it represents a change in the intent and policy of IRTP-C. at a minimum, if the IRT insists on the addition of this language, i will raise the “change of policy which needs to go through Policy/Implementation review” flag. i haven’t been following the Policy/Implementation WG so i don’t know where they are at, but this will make a nifty test case for them because this is a really good example of core policy being changed during implementation. mike On Dec 2, 2014, at 3:52 PM, Caitlin Tubergen <caitlin.tubergen(a)icann.org<mailto:caitlin.tubergen@icann.org>> wrote: > Hi All, > > Please save the date for the final IRTP-C IRT call before the draft Change of Registrant Policy goes out for public comment. > > The draft policy is attached; a briefing document, describing two outstanding issues, is also attached. If you would like to distribute the documents to your colleagues, or other interested parties, please do so before the the call on Thursday, 11 December 2014. Comments on the policy or the briefing document should be delivered to me prior to the call on Thursday, 11 December. > > Details for 11 December Call > The next Inter-Registrar Transfer Policy (IRTP) Part C Implementation Review Team teleconference is scheduled for Thursday 11 December 2014 at 17:00 UTC. > 09:00 PST, 12:00 EST, 17:00 London, 17:00 CET, 03:00 (+1 day) Sydney. > > Link to Adobe Connect (with audio enabled): https://icann.adobeconnect.com/irtppartc/ > *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). > After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. > If you are Unable to log into Adobe Connect and can only join via phone: > List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=6458688446&num=1-719-… > Participant Passcode: 6458688446 > > Please let me know if you have any questions. > > Kind regards, > > Caitlin > <Mail Attachment.ics><Draft Change of Registrant Policy_13Nov[2].docx><Updated Change of Registrant Policy Issues Briefing Document 2Dec.docx> PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

3 3

Save the Date: IRTP-C Implementation Review Team Call 11 Dec 2014
by Caitlin Tubergen Dec. 11, 2014

Dec. 11, 2014

Hi All, Please save the date for the final IRTP-C IRT call before the draft Change of Registrant Policy goes out for public comment. The draft policy is attached; a briefing document, describing two outstanding issues, is also attached. If you would like to distribute the documents to your colleagues, or other interested parties, please do so before the the call on Thursday, 11 December 2014. Comments on the policy or the briefing document should be delivered to me prior to the call on Thursday, 11 December. Details for 11 December Call The next Inter-Registrar Transfer Policy (IRTP) Part C Implementation Review Team teleconference is scheduled for Thursday 11 December 2014 at 17:00 UTC. 09:00 PST, 12:00 EST, 17:00 London, 17:00 CET, 03:00 (+1 day) Sydney. Link to Adobe Connect (with audio enabled): https://icann.adobeconnect.com/irtppartc/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=6458688446&num=1-719-… Participant Passcode: 6458688446 Please let me know if you have any questions. Kind regards, Caitlin

2 2

PLEASE RSVP Monthly GNSO WG Newcomer Open House Session
by Nathalie Peregrine Dec. 9, 2014

Dec. 9, 2014

Reminder: Monthly GNSO WG Newcomer Open House Session These ongoing monthly sessions are for new GNSO WG participants to come together and discuss any questions they may have about GNSO Working Groups, procedures and/or processes. We know there is a lot of information to digest when you join a GNSO Working Group and these monthly meetings are an opportunity for newcomers and more experienced participants to meet in an informal setting without the pressure of "real work" that needs be done. The agenda is flexible. The presenters will be ready with a standard set of materials if people would like to discuss them. Feel free to submit questions, either in advance or at the beginning of the meeting, if there is a topic that you would like to explore in more depth . Providing useful answers to a wide range of questions is part of the reason why these meetings are Thursday 23 October at 12.00 UTC (new date) Thursday 6 November at 20.00 UTC Thursday 4 December at 12.00 UTC To convert to your local time zone, please see http://www.timeanddate.com/worldclock/converter.html If you are interested to join the next meeting on 23 October or any of the future meetings, please let the GNSO Secretariat know ( <mailto:gnso-secs@icann.org> gnso-secs(a)icann.org) and we will send you the call details. If there are any specific questions you already have, or any overviews or introductions you think would be helpful (e.g. GNSO Policy Development Process or GNSO Working Group guidelines), please let us know in advance and we will prepare materials accordingly. Feel free to share this invitation with others that you think may be interested. We look forward to welcoming you at the next meeting! Nathalie Peregrine GNSO Secretariat

2 3