February 2014 - Gnso-irtpd - lists.icann.org

Attendance MP3 IRTP D meeting - Monday 10 February 2014
by Nathalie Peregrine Feb. 10, 2014

Feb. 10, 2014

Dear All, The next Inter-Registrar Transfer Policy (IRTP) Part D Working Group meeting will be held on Monday 17 February 2014. Please find the MP3 recording for the IRTP Part D Working Group call held on Monday 10 February 2014 at 16:00 UTC at: http://audio.icann.org/gnso/gnso-irtp-d-20140210-en.mp3 On page: http://gnso.icann.org/en/group-activities/calendar#<http://gnso.icann.org/en/group-activities/calendar#may>feb The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/calendar/ Attendees: Graeme Bunton - RrSG Avri Doria - NCSG Mikey O'Connor - ISPCP Barbara Knight - RySG Kristina Dorrain - NAF Volker Greimann - RrSG James Bladel - RrSG Angie Graves - BC Chris Chaplow - CBUC Kevin Erdman - IPC Apologies: Paul Diaz - RySG ICANN staff: Lars Hoffmann Berry Cobb Nathalie Peregrine ** Please let me know if your name has been left off the list ** Mailing list archives: http://forum.icann.org/lists/gnso-irtpd/ Wiki page: https://community.icann.org/x/B4JwAg Thank you. Kind regards, Nathalie Peregrine Adobe Connect chat transcript for Monday 10 February 2014: Lars Hoffmann:Welcome to the IRTP Part D PDP Working Group meeting, Monday 10 February 2014 Graeme Bunton:G'mornin Berry Cobb:Lori is welcome to join the WG now Nathalie Peregrine:Angie Graves has joined the AC room Nathalie Peregrine:Kevin Erdman has joined the call Avri Doria:This is one where i think we need a footnote reminding that in the case of any registrant issues, if complaince denies having a role or whatever, the registratn still has recourse to ombudsman Bladel:Avri: Can you clarify? I don't think the Ombudsman can compel a registrar to act, but they can compel compliance to respond to a compliant against a registrar..... Berry Cobb:The Starting Sequence # schema is missing #5 Volker Greimann:Where James is even the screen is freezing Kristine Dorrain:Yes. Volker Greimann:hmmm Volker Greimann:go ahead Bladel:or NOT hear that the mic is broken. :) Volker Greimann:i am back Volker Greimann:found the error Barbara Knight:Thanks James Volker Greimann:This does open up a potential issue for the aftermarket of course... Avri Doria:i like the notion of vestigial hands. Avri Doria:James, the ombudsman cant comepell anyone to anything. The ombudsman can, however, mediate anything, convince etc, on any ICANN issue except issues having to do with employees. Avri Doria:so it is another avenue of possible redress i think should be flaged. Bladel:They can be separate/different contacts Holly Raiche:Thanks James Graeme Bunton:+1 Avri Doria:bye, thanks

1 0

Example email string
by Dorrain, Kristine Feb. 10, 2014

Feb. 10, 2014

Hey everyone: See the chain of emails from someone desperate for their registrar to file a TDRP-the registrar is refusing. I've redacted personally identifiable information and we may wish to use this example as evidence. We see this not infrequently. I copied the string so read from the bottom up. Kristine Kristine F. Dorrain, Esq. Director of Internet and IP Services National Arbitration Forum (FORUM) P.O. Box 50191 Minneapolis, MN 55405 Phone 952.516.6456 Fax 866.342.0657 Email kdorrain(a)adrforum.com domains.adrforum.com This e-mail message and any attachments are confidential and may be privileged information. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, please notify the sender immediately and destroy all copies of this message and attachments

5 12

Initial Report Update
by Lars Hoffmann Feb. 10, 2014

Feb. 10, 2014

Dear all, Please find attached an updated version of the Initial Report. I have accepted all changes made by Mikey in last week's draft since there were no objections to them on the call. I have then focused the edits on changes to WG Observations and Recommendations – based on the outcome of Monday's call. I have not yet combined the sections of Issue Description and WG Observations that was suggested by the Group but it is on the list for the next update. Best wishes, Lars

2 4

PLEASE RSVP FOR DIAL IN DETAILS: Continuation of GNSO WG Newcomer Open House Sessions
by Nathalie Peregrine Feb. 3, 2014

Feb. 3, 2014

http://gnso.icann.org/en/announcements/announcement-28jan14-en.htm Continuation of GNSO WG Newcomer Open House Sessions Following a successful GNSO WG Newcomer Open House session pilot session<http://www.ispcp.info/policy-resources/gnso-working-groups-newcomer-open-ho…> in December of last year, we would like to continue with these sessions to allow for new GNSO WG participants to come together and ask 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 would like to offer this opportunity to come together, talk and answer any questions you may have. To allow for maximum participation in these calls, the proposed schedule is as follows: Thursday 6 February at 12.00 UTC Thursday 6 March at 20.00 UTC Thursday 3 April at 12.00 UTC Thursday 1 May at 20.00 UTC Thursday 5 June at 12.00 UTC Thursday 3 July at 20.00 UTC Thursday 7 August at 12.00 UTC Thursday 4 September at 20.00 UTC Thursday 2 October at 12.00 UTC 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 6 February or any of the future meetings, please let the GNSO Secretariat know (gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>) and they 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! Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

MP3 IRTP D meeting - Monday 03 February 2014
by Nathalie Peregrine Feb. 3, 2014

Feb. 3, 2014

Dear All, The next Inter-Registrar Transfer Policy (IRTP) Part D Working Group meeting will be held on Monday 10 February 2014. Please find the MP3 recording for the IRTP Part D Working Group call held on Monday 03 February 2014 at 16:00 UTC at: http://audio.icann.org/gnso/gnso-irtp-d-20140203-en.mp3 On page: http://gnso.icann.org/en/group-activities/calendar#<http://gnso.icann.org/en/group-activities/calendar#may>feb The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/calendar/ Attendees: Graeme Bunton - RrSG Avri Doria - NCSG Mikey O'Connor - ISPCP Barbara Knight - RySG Rob Golding - RrSG Kristina Dorrain - NAF Volker Greimann - RrSG James Bladel - RrSG Angie Graves - BC Chris Chaplow - CBUC Bartlett Morgan - NCUC Kevin Erdman - IPC Apologies: Paul Diaz - RySG ICANN staff: Lars Hoffmann Berry Cobb Nathalie Peregrine ** Please let me know if your name has been left off the list ** Mailing list archives: http://forum.icann.org/lists/gnso-irtpd/ Wiki page: https://community.icann.org/x/B4JwAg Thank you. Kind regards, Nathalie Peregrine Adobe Connect chat transcript for Monday 03 February 2014: Lars Hoffmann:Welcome to the IRTP Part D PDP Working Group meeting, Monday 03 February 2014 Volker Greimann:Hi Lars, I think you just missed the operator Lars Hoffmann:how so? Volker Greimann:he was asking for the passcode, but no one responded Volker Greimann:so he hung up the line again Nathalie Peregrine:The AC room sometimes dials to the provder automatically without us having prompted it to,, hence why no one replied. I have now activated the audio, so we are all set Volker Greimann:ah, that confused me Nathalie Peregrine:Rob Golding has also joined Mike O'Connor:that's what you get when both teams come from states where marijuana is legal Nathalie Peregrine:Kristine Dorrain has joined the call Kristine Dorrain:Apologies for being tardy Nathalie Peregrine:Berry Cobb has joined the AC room Nathalie Peregrine:Chris Chaplow and Bartlett Morgan have joined the call Bartlett Morgan:Hi all. apologies for being late; Another meeting ran over Rob Golding (Astutium-1471):justification - registrars are oblliged to contact the registrant at least once per year for WDRP, so an annual contact is not unexcpected Rob Golding (Astutium-1471):wheras people largely register for 2+ years so they dont expect bills annually :) Rob Golding (Astutium-1471):i'm waiting to get through on the phone Graeme Bunton:checking our avg renewal period now.. Volker Greimann:Hi Rob, that is interesting, but only applies to the UK, I think as .co.uk worked similarly. We usually see annual registration, with just a small percentage being multi-year. Graeme Bunton:Our avg is ~1.1 years per renewal transactions Rob Golding (Astutium-1471):@volker - then they'd be expecting a bill as well, so 2 thing sto 'trigger' them to rethink about their domains :) Graeme Bunton:higher for cc's Nathalie Peregrine:Kevin Erdman has joined the AC room] Rob Golding (Astutium-1471):our average is 2.7yrs for gtlds and 2.03 for cctlds (skewed as .co.uk used to only be 2 years which as UK based means most of ours are 2 yrs) Rob Golding (Astutium-1471):most of our 1 yr gtlds reg's are those that came free with another srevice, as registrants seem to think in 2 year chunks :) Graeme Bunton:that is interestingly different Bladel:I'm back...sorry Volker Greimann:indeed Rob Golding (Astutium-1471):10.8% of our paid gtld registrations are 1 year, so 89% are 2+ (with 2 and 5 being the most common) Graeme Bunton:wow. Volker Greimann:we need to get into this market ;-) Graeme Bunton:are you looking at reg, or renewals or both? Rob Golding (Astutium-1471):i limited the query to registrations Rob Golding (Astutium-1471):it's hell on the cashflow though with it being 2 years between invoices Rob Golding (Astutium-1471):it needs to be on the internic site too Volker Greimann:Isn't ICANN fading that one out? Volker Greimann:2099: ICANN must put it on their Facebook page Rob Golding (Astutium-1471):i dont think they're phasing internic out as thet just announced chnages to it reagrding new whoi and common layout stuff Berry Cobb:The IETF runs Internic Rob Golding (Astutium-1471):it's where icann tell people to go to lookup details about their domain Bladel:iana.org Berry Cobb:All Compliance needs are run off icann.org Berry Cobb:We can ask Internic to post a message if need be. Rob Golding (Astutium-1471):operated or promoted by icann maybe ? Chris Chaplow:daylight Rob Golding (Astutium-1471):did we get a decision on how 'public' tdrp results/reporting should be ? Rob Golding (Astutium-1471):I recall .ASIA providing some data about theirs Rob Golding (Astutium-1471):having access to all those registry reports on the icann site would be good for the transparancy Mike O'Connor:we're saying "public" in the draft. there's a way for them to redact, otherwise public Mike O'Connor:agree Rob, links to these would be a good thing in the recommendation Rob Golding (Astutium-1471):thanks jame & mikey Bartlett Morgan:thanks bye

1 0

First draft on Locking Language
by Volker Greimann Feb. 3, 2014

Feb. 3, 2014

Hi folks, this is still a bit bloated, but it captures what James and I had discussed in the previous week: "When receiving a notice of a transfer complaint by the previous registrant within X months after the transfer from the losing registrar, the gaining registrar shall place the domain name under registrar lock. The registrar lock shall be removed after 30 calendar days unless the gaining registrar receives notice of the pendancy of legal proceedings between the original registrant and the current registrant, in which case the lock shall remain in place until the case is decided or dismissed. /If both the gaining and losing registrar (or, in cases involving multiple transfers, the current registrar and the registrar filing the dispute) agree, then the transfer(s) may be reversed before applying the lock. //Any fees charged for reversed transfers under this policy shall be refunded by the respective registry. No ICANN fees shall apply." / -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.

6 8