[Gnso-impl-thickwhois-rt] Thick Transition policy draft v5 for IRT review

[Dennis Chang]

First on Marc’s suggested changes.
I see the point of your clarification and thanks to your team for catching it.

Question: does the alternative bulk transfer mechanism require OT&E phase also?
If so, may I suggest,

By 1 August, Registry Operator MUST deploy an EPP mechanism and an alternative bulk transfer mechanism in relevant Operating
Test Environments (OT&E) for registrars to test the migration of registration data for Existing Domain Names (i.e., transition from Thin to Thick).
If you agree, I’ll make this change as part of our version 6 which we are targeting as the final version.

Second on Theo’s question on edge cases that IRT has not considered;
I’d like to remind ourselves of the current work scope time to time.
We are working on a policy to start a public comment.
As such, we need to keep our focus on what we need to start the public comment.
This is why we review the public comment readiness chart at each meeting.

I welcome the team to bring up all and every issues we can think of so we can quickly categorize them in their right place for work.
It could be a procedure item that we can work on as a part of implementation for example.

Thanks
Dennis Chang

On 10/6/16, 12:56 PM, "gtheo" <gtheo at xs4all.nl> wrote:

    I am good with this Marc (like you need my blessing, lol).
    
    Slightly different, this gives like 90 days of testing more or less. 
    This is under normal circumstances enough. However, we might be dealing 
    with some other ICANN-related stuff. So this 90 day period is going to 
    be short actually.
    This itself is no issue I suspect. But we are dealing with some rather 
    old data, far older then .ORG ever faced.
    
    When we migrated data over several new backends we had a plan B and C. 
    Does Verisign have a plan B? Plan B in the sense we hit issues with on 
    OTE that the IRT never anticipated.
    As an IRT I think we covered a ton of stuff here, but there always edge 
    cases and it is not up to us to discuss them or have solutions. But what 
    are we gonna do with the edge cases and what if we do encounter a major 
    problem the IRT did not anticipate?
    
    Thanks!
    
    Theo
    
    
    
    
    
    
    Anderson, Marc schreef op 2016-10-06 08:30 PM:
    > Dennis,
    > 
    > I have some additional feedback on the thick transition policy
    > document.  Section 2.3 in this version reads:
    > 
    > 2.3   By 1 May 2017, Registry Operator MUST provide to applicable
    > Registrars and ICANN, documentation reflecting the system changes
    > necessary to support the requirements of Sections 2.1 concerning
    > relevant Operating Test Environments (OT&E) available to Registrars
    > and by 1 August 2017 for Section 2.2.
    > 
    > I believe one of the intents of this section is to require Registries
    > to have the OT&E environment ready for Registrars to begin testing
    > with contacts starting 1 May 2017.  This is what we’ve discussed on
    > IRT calls and what is represented in the timeline chart.  It has been
    > pointed out to me that reading this section it is not clear that
    > Registries are required to start supporting contact operations in OT&E
    > on 1 May 2017.
    > 
    > I suggest splitting this out into two sections one for the
    > documentation requirement, and one for the OT&E requirement.  How
    > about something along these lines:
    > 
    > _By 1 May 2017, Registry Operator MUST provide to applicable
    > Registrars and ICANN, documentation reflecting the system changes
    > necessary to support the requirements of Sections 2.1_
    > 
    > _ _
    > 
    > and
    > 
    > Registry Operator MUST deploy an EPP mechanism in relevant Operating
    > Test Environments (OT&E) by 1 May 2017 for registrars to test the
    > migration of registration data for Existing Domain Names (i.e.,
    > transition from Thin to Thick).
    > 
    > I think that makes it a little clearer what is required and when.
    > 
    > Thank you,
    > 
    > Marc
    > 
    > FROM: gnso-impl-thickwhois-rt-bounces at icann.org
    > [mailto:gnso-impl-thickwhois-rt-bounces at icann.org] ON BEHALF OF Dennis
    > Chang
    > SENT: Saturday, October 01, 2016 12:58 PM
    > TO: gnso-impl-thickwhois-rt at icann.org
    > SUBJECT: [Gnso-impl-thickwhois-rt] Thick Transition policy draft v5
    > for IRT review
    > 
    > Dear Thick Whois IRT,
    > 
    > Attached is the draft transition policy document for IRT review.
    > 
    > Now version 5 both clean and redlined.
    > 
    > As before, please provide your comments prior to the meeting if
    > possible.
    > 
    > —
    > 
    > Kind Regards,
    > 
    > Dennis S. Chang
    > 
    > GDD Services & Engagement Program Director
    > 
    > +1 213 293 7889
    > 
    > Skype: dennisSchang
    > 
    > www.icann.org [1]   "One World, One Internet"
    > 
    > 
    > 
    > Links:
    > ------
    > [1] https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DQIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=dqLP1wJqBvDSYLKrSEaAkCi_Kv0Mk5D_d32n29DHCN8&m=zDHPXWMyYHVpPH1lLXDfsqWegJYO6dB__kF5BmJCvxI&s=IcT2gB_sryEFQEbSk2v2uxXDDz4CnFV4FZbEdA2BCL8&e= 
    > _______________________________________________
    > Gnso-impl-thickwhois-rt mailing list
    > Gnso-impl-thickwhois-rt at icann.org
    > https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt