[IRT.RegDataPolicy] Timeline input on Critical Path Tasks

Sarah Wyld swyld at tucows.com
Fri Jan 31 14:24:54 UTC 2020


Dear Dennis and IPT,

The CPH IRT members have considered the IPT’s request at the 15 January
2020 IRT meeting to provide further detail regarding the length of time
that will be required for Contracted Parties to implement the new gTLD
Registration Data Policy, and the critical path for development work.

Regarding the duration of the implementation period, we refer back to
our IRT Actions document which is now tracked as the IRT.timeline input
<https://docs.google.com/document/d/1Q7DkOeLHhpq98ym6erIS41sYfx0sUCeOxEQCi5gz2Uk/edit#>.
We understand the IPT’s request to provide further specificity, however
as discussed on the call the CPH does not believe this can be
realistically achieved. Our proposed minimum timeline of 18 months was
arrived at based on consultation with RrSG and RySG members. We hope
that the Public Comment period will spur further discussion and comment
on this topic from Contracted Parties who will need to implement the new
Policy, and we expect that any adjustments based on feedback received
will extend rather than shorten the implementation buffer period.

The critical path for development work will be different for each party
implementing the new Policy, as different systems have different needs
and Contracted Parties have already implemented various changes which
will be part of the new Policy. As such, the IPT/IRT should not require
that the new Policy be implemented in any specific order. We do note
that there are several dependencies, including modification of which
data elements are transferred from registrar to registry and deprecation
of the Admin contact. These areas (among others) will require the
registry changes to be in place before registrar changes can be
completed. That said, we remain confident in the 18 month minimum
timeframe.


Thank you,

The CPH IRT team.




-- 
Sarah Wyld
Domains Product Team
Tucows
+1.416 535 0123 Ext. 1392

 

On 1/10/2020 12:59 PM, Dennis Chang wrote:
>
> Dear IRT,
>
>  
>
> The link to the Timeline sheet I provided in the task assignment may
> not be working correctly. (thanks Sarah for alerting me)
>
> So I’ve reformatted the assignment to use the document Sarah+CPH have
> submitted before to collect your input (thanks again Sarah)
>
>  
>
> 83
>
> 	
>
> _Provide critical path timeline input
> <https://docs.google.com/document/d/1Q7DkOeLHhpq98ym6erIS41sYfx0sUCeOxEQCi5gz2Uk/edit#heading=h.1n8kxtu8050v>_
>
> 	
>
> 20220113
>
>  
>
> This is format allows you to have a free space to enter your inputs.
>
> Using your input I will put together a version on the Timeline sheet
> to facilitate easy of review.
>
>  
>
> Thanks
>
> Dennis Chang
>
>  
>
> *From: *"IRT.RegDataPolicy" <irt.regdatapolicy-bounces at icann.org> on
> behalf of Dennis Chang <dennis.chang at icann.org>
> *Date: *Thursday, January 9, 2020 at 07:50
> *To: *"irt.regdatapolicy at icann.org" <irt.regdatapolicy at icann.org>
> *Subject: *[IRT.RegDataPolicy] Timeline input on Critical Path Tasks
>
>  
>
> Dear IRT,
>
>  
>
> A head of our meeting next week, I am adding a task to remind the IRT
> of the inputs needed for the Implementation Time Duration.
>
> At our last discussion, we heard ranges from 12 months to 15 months
> (also 18 months.)
>
>  
>
> Thanks for the initial assessment and now we need to document the
> basis for that duration to set our implementation schedule.
>
> 83
>
> 	
>
> _Provide inputs to the Implementation Time Duration critical path for
> more than the default 6 months <#gid=1416489980>_
>
> 	
>
> 20220113
>
> 	
>
> _Sarah-CPH input 20191216
> <https://docs.google.com/document/d/1Q7DkOeLHhpq98ym6erIS41sYfx0sUCeOxEQCi5gz2Uk/edit#heading=h.1n8kxtu8050v>_
>
>  
>
> So far, the inputs have been scope of work (size of task)
>
> and we need the schedule of the work (time duration) for those tasks
> that are in the Critical Path.
>
>  
>
> Please note that we need this timeline to establish our target policy
> effective date and procced to Public Comment for feedback.
>
>  
>
> We appreciate the IRT’s expertise supporting the Implementation plan
> to come up with the realistic schedule for the community to respond to.
>
>  
>
> -- 
>
> Kind Regards,
>
> Dennis S. Chang
>
> GDD Programs Director
>
> Phone: +1 213 293 7889
>
> Sykpe: dennisSchang
>
> www.icann.org <http://www.icann.org> One World – One Internet
>
>
> _______________________________________________
> IRT.RegDataPolicy mailing list
> IRT.RegDataPolicy at icann.org
> https://mm.icann.org/mailman/listinfo/irt.regdatapolicy
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20200131/bb486ccd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20200131/bb486ccd/signature.asc>


More information about the IRT.RegDataPolicy mailing list