[gnso-impl-irtpc-rt] RE: Save the Date: IRTP-C Teleconference

Mon Sep 22 14:39:16 UTC 2014

James:

Respectively, I am not of the opinion that procedure is a good reason to
communicate unclearly. 

We can delay the metrics to future discussions, however definitions would be ill
advised to fly in the face of industry standards.

Met vriendelijke groet / Kind regards,

Arthur Zonnenberg
Product Manager
Hostnet bv

tel: +31.207500834
fax: +31.207500825
mail: azonnenberg at hostnet.nl
website: https://www.hostnet.nl

> On September 22, 2014 at 4:06 PM "James M. Bladel" <jbladel at godaddy.com>
> wrote:
> 
> 
> 
> Arthur:
> 
> Respectively, the time for this discussion was pre-2012.  It is wholly
> inappropriate to re-open these issues within the context of Implementation.
> 
> J.
> 
> 
> On 9/22/14, 8:44 , "Arthur Zonnenberg" <azonnenberg at hostnet.nl> wrote:
> 
> >In response to Michele and James, although this discussion should be
> >saved for
> >the next conference:
> >- I am aware of the original report;
> >- I advise to use clear language for implementation, to avoid
> >miscommunication
> >based on wording. IRTP-C simply is not a "Change of Registrant" policy
> >anymore
> >the minute the PDP decided to include a change of e-mail address, which
> >industry
> >wide and stand is known as a "contact update" , originating from the
> >RFC5730 EPP
> >standard. 
> >
> >Although contact create and domain update are also used via EPP, most
> >registrar
> >price lists clearly distinguish a change of registrant price versus a
> >change of
> >contact information price. This distinction is in my experience also
> >regularly
> >communicated to end users.
> >
> >Since we were discussing definitions 1.b), that includes the definition
> >of the
> >name given to the policy itself. So either we forbid discussions of the
> >definitions or we change it to something that can be implemented or
> >communicated
> >clearly.
> >
> >Alternatively we can call it a "Change of Control" Policy, with the
> >burden of
> >explaining that to end users (not too dissimilar from the IRTP in
> >general). In
> >any case "Change of Registrant" or "Change of Registrant Information" is
> >incomplete since we apply it to e-mail and admin-c as well and therefore
> >confusing.
> >
> >I therefore call on the group to include change of control policy
> >metrics, for
> >example about the policy being complained about as confusing in
> >communication
> >(point above), or about changes of registrant/control being failed or
> >abandoned,
> >measuring its effectiveness (see my other comment in the document). We
> >have
> >currently have no data to check whether this policy to be implemented will
> >actually succeed in the majority of user cases in practice. If this is
> >beyond
> >the scope of IRTP-C policy, it will need to be addressed by the to be
> >accepted
> >IRTP-D policy. Or are there alternatives for checking the effect of what
> >we are
> >doing?
> >
> >Met vriendelijke groet / Kind regards,
> >
> >Arthur Zonnenberg
> >Product Manager
> >Hostnet bv
> >
> >tel: +31.207500834
> >fax: +31.207500825
> >mail: azonnenberg at hostnet.nl
> >website: https://www.hostnet.nl
> >
> >> On September 22, 2014 at 3:14 PM "James M. Bladel" <jbladel at godaddy.com>
> >> wrote:
> >> 
> >> 
> >> 
> >> Hi Folks:
> >> 
> >> The IRTP-C recommendations clearly designate a ³Change of Registrant²
> >> consensus policy.  It also refers to this as a ³change of control,²
> >>which
> >> would, IMO, include email address since that is the destination address
> >> for the FOA/AuthInfo code.
> >> 
> >> For your convenience, here is a link to the IRTP-C PDP Final Report:
> >> http://gnso.icann.org/en/issues/irtp-c-final-report-09oct12-en.pdf
> >> 
> >> Thanks--
> >> 
> >> J.
> >> 
> >> 
> >> On 9/22/14, 7:39 , "Michele Neylon - Blacknight"
> >><michele at blacknight.com>
> >> wrote:
> >> 
> >> >Arthur
> >> >
> >> >You cannot simply change it to "change of whois information"
> >> >
> >> >The entire policy is around "change of registrant"
> >> >
> >> >Regards
> >> >
> >> >Michele
> >> >
> >> >
> >> >--
> >> >Mr Michele Neylon
> >> >Blacknight Solutions
> >> >Hosting, Colocation & Domains
> >> >http://www.blacknight.host/
> >> >http://blog.blacknight.com/
> >> >http://www.technology.ie
> >> >http://www.blacknight.press for all our news & media
> >> >Intl. +353 (0) 59  9183072
> >> >Direct Dial: +353 (0)59 9183090
> >> >Social: http://mneylon.social
> >> >-------------------------------
> >> >Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business
> >> >Park,Sleaty
> >> >Road,Graiguecullen,Carlow,Ireland  Company No.: 370845
> >> >
> >> >
> >> >-----Original Message-----
> >> >From: Arthur Zonnenberg [mailto:azonnenberg at hostnet.nl]
> >> >Sent: Monday, September 22, 2014 1:32 PM
> >> >To: Caitlin Tubergen; Leticia Castillo; gnso-impl-irtpc-rt at icann.org;
> >> >Batteiger, Simonetta
> >> >Cc: Amy Bivins; Terri Agnew; Marika Konings; Mike Zupke; Michele
> >>Neylon -
> >> >Blacknight; Glen de Saint Géry; James M. Bladel; Steve Chan; Lars
> >> >Hoffmann; Nathalie Peregrine
> >> >Subject: Re: [gnso-impl-irtpc-rt] RE: Save the Date: IRTP-C
> >>Teleconference
> >> >
> >> >Hi Everyone,
> >> >
> >> >Some interesting implementation topics were raised during the call,
> >> >inspiring me to add some edits and comments to be discussed in our next
> >> >session.
> >> >
> >> >Met vriendelijke groet / Kind regards,
> >> >
> >> >Arthur Zonnenberg
> >> >Product Manager
> >> >Hostnet bv
> >> >
> >> >tel: +31.207500834
> >> >fax: +31.207500825
> >> >mail: azonnenberg at hostnet.nl
> >> >website: https://www.hostnet.nl
> >> >
> >> >> On September 18, 2014 at 7:04 PM "Batteiger, Simonetta"
> >> >> <simonetta at sedo.com>
> >> >> wrote:
> >> >> 
> >> >> 
> >> >> Hi Everyone,
> >> >> I apologize for my non working microphone on today's call.
> >> >> Please find a couple of wording suggestions attached for discussion
> >>in
> >> >> the group.
> >> >> Simonetta
> >> >> 
> >> >> -----Original Appointment-----
> >> >> From: Caitlin Tubergen [mailto:caitlin.tubergen at icann.org]
> >> >> Sent: Thursday, September 18, 2014 12:48 AM
> >> >> To: gnso-impl-irtpc-rt at icann.org; Leticia Castillo
> >> >> Cc: Amy Bivins; Steve Chan; Glen de Saint Géry; James M. Bladel; Mike
> >> >> Zupke; Arthur Zonnenberg; Lars Hoffmann; Terri Agnew; Nathalie
> >> >> Peregrine; Marika Konings; Michele Neylon - Blacknight
> >> >> Subject: [gnso-impl-irtpc-rt] Save the Date: IRTP-C Teleconference
> >> >> When: Thursday, September 18, 2014 4:00 PM-5:00 PM (UTC) Coordinated
> >> >> Universal Time.
> >> >> Where: Adigo Conference ID: 28462745
> >> >> 
> >> >> 
> >> >> Dear all,
> >> >> 
> >> >> The next Inter-Registrar Transfer Policy (IRTP) Part C Implementation
> >> >> Review Team teleconference is scheduled for Thursday 18 September
> >>2014
> >> >>at 16:00 UTC.
> >> >> 09:00 PDT, 12:00 EDT, 17:00 London, 17:00 CET, 03:00 (+1 day) Sydney.
> >> >> 
> >> >> 
> >> >> We will be discussing the draft Change of Registrant Policy, which is
> >> >> attached.
> >> >> 
> >> >> 
> >> >> Adigo Conference ID: 28462745
> >> >> 
> >> >> 
> >> >> Adigo numbers: http://adigo.com/icann/
> >> >> 
> >> >> 
> >> >> Adobe Connect with audio enabled:
> >> >> http://icann.adobeconnect.com/irtppartc/
> >> >> 
> >> >> 
> >> >> Please let me know if you have any questions.
> >> >> 
> >> >> 
> >> >> Kind regards,
> >> >> 
> >> >> 
> >> >> Caitlin Tubergen
> >> >> Registrar Relations and Contracts Manager ICANN
> >> >> 
> >> >>  << File: Draft Change of Registrant Policy.docx >>
> >> >>
> >> 
> >>
> 
>