Re: [gnso-impl-irtpc-rt] Save the Date: IRTP-C Implementation Review Team Call 11 Dec 2014

["Mike O'Connor" <mike@xxxxxxxxxx>]

i’ve been staring at 3.4 for a while…  

in [3.1 e)] we refer to Section 3.4 as the section where Prior Registrants can 
opt out of the 60 day lock

in [3.4] we’re talking about those cases where credentials don’t need to be 
exchanged

are we looking at a drafting error?  the intent of the opt-out language in 
[3.1. e)] is to provide a registrant who is in a hurry to transfer their name a 
way to avoid the 60-day lockout.  the current [3.4] language is talking about 
removing the exchange of credentials [3.2] for those cases where the registrant 
is actually changed.  

those seem like really different things — so it seems like we can look at 
either;

- change 3.4 back to opting out of the 60-day lockout (which seems like 
something we need to do in a section somewhere) or 

- use [3.4] to specify those circumstances where there doesn’t need to be an 
exchange of credentials (which would be those cases where the update of 
registration data does NOT cause a change of registrant)

just a few notes, to help me remember what i’ve been thinking about 

m


On Dec 11, 2014, at 8:04 AM, James M. Bladel <jbladel@xxxxxxxxxxx> wrote:

> 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@xxxxxxxxxxxx>
> Date: Thursday, December 11, 2014 at 6:47 
> To: Mike O'Connor <mike@xxxxxxxxxx>
> Cc: Caitlin Tubergen <caitlin.tubergen@xxxxxxxxx>, Barbara Knight 
> <BKnight@xxxxxxxxxxxx>, Leticia Castillo <leticia.castillo@xxxxxxxxx>, James 
> Bladel <jbladel@xxxxxxxxxxx>, Marika Konings <marika.konings@xxxxxxxxx>, 
> Gisella Gruber <Gisella.Gruber@xxxxxxxxx>, Arthur Zonnenberg 
> <azonnenberg@xxxxxxxxxx>, Phil Corwin <psc@xxxxxxxxxxx>, Lars Hoffmann 
> <lars.hoffmann@xxxxxxxxx>, "gnso-impl-irtpc-rt@xxxxxxxxx" 
> <gnso-impl-irtpc-rt@xxxxxxxxx>, Steve Chan <steve.chan@xxxxxxxxx>, Terri 
> Agnew <terri.agnew@xxxxxxxxx>, "Sedo :: Simonetta Batteiger" 
> <simonetta@xxxxxxxx>, Nathalie Peregrine <nathalie.peregrine@xxxxxxxxx>, Rob 
> Golding <rob.golding@xxxxxxxxxxxx>, Michele Neylon - Blacknight 
> <michele@xxxxxxxxxxxxxx>, Mike Zupke <Mike.Zupke@xxxxxxxxx>, Bob Mountain 
> <bmountain@xxxxxxxxxxx>
> 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@xxxxxxxxxxxxxxxxxxxx
> 
> 
> 
> 
> 
> Van: "Mike O'Connor" <mike@xxxxxxxxxx>
> Aan: "Caitlin Tubergen" <caitlin.tubergen@xxxxxxxxx>
> Cc: "Theo Geurts" <theo.geurts@xxxxxxxxxxxx>, "Barbara Knight" 
> <BKnight@xxxxxxxxxxxx>, "Leticia Castillo" <leticia.castillo@xxxxxxxxx>, 
> "James Bladel" <jbladel@xxxxxxxxxxx>, "Marika Konings" 
> <marika.konings@xxxxxxxxx>, "Gisella Gruber" <Gisella.Gruber@xxxxxxxxx>, 
> "Arthur Zonnenberg" <azonnenberg@xxxxxxxxxx>, "Phil Corwin" 
> <psc@xxxxxxxxxxx>, "Lars Hoffmann" <lars.hoffmann@xxxxxxxxx>, 
> gnso-impl-irtpc-rt@xxxxxxxxx, "Steve Chan" <steve.chan@xxxxxxxxx>, "Terri 
> Agnew" <terri.agnew@xxxxxxxxx>, "Sedo :: Simonetta Batteiger" 
> <simonetta@xxxxxxxx>, "Nathalie Peregrine" <nathalie.peregrine@xxxxxxxxx>, 
> "Rob Golding" <rob.golding@xxxxxxxxxxxx>, "Michele Neylon - Blacknight" 
> <michele@xxxxxxxxxxxxxx>, "Mike Zupke" <Mike.Zupke@xxxxxxxxx>, "Bob Mountain" 
> <bmountain@xxxxxxxxxxx>
> 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@xxxxxxxxx> 
> 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-457-6209
> > 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.)


PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP 
(ID for Twitter, Facebook, LinkedIn, etc.)