[Gnso-epdp-team] Input on Appendix A - Input due by Sunday 16 September

[Kurt Pritz]

Hi Marc: 

I accept your advice. 

I have some your same concerns but thought the proposed course was acceptable and necessary because: 
We have had substantive discussion on Appendix A during the triage section. The slides and the issues listed therein were based on that. Now we are looking for suggested solutions to the issues raised in the triage discussion.
Given the triage discussion and the fact that we would have a kickoff discussion describing them with the small group, we felt that the participants would be sufficiently informed by the sense of the full group
Participation is open so no one interested in participating directly would be excluded
The whole time is of the you-know-what thing, I was looking for a way to have some proposals on the table for Appendix A for the LA meeting. 

I will continue to consider ways to start discussion of Appendix A offline as a prep to a meeting discussion. Milton had suggested a poll that listed each redacted datum and asked if the group agreed with each or not. Even though we haven’t finished the data element discussion yet, it might be beneficial to undertake that. 

Marc (and others) if you have thoughts on how to move the appendix A discussion forward, pleas get them out.

Best regards,

Kurt

> On Sep 14, 2018, at 9:46 AM, Anderson, Marc <mcanderson at verisign.com> wrote:
> 
> Marika, thank you for the clarification, however I believe my point still stands.  Volunteers should not start working on proposed recommendations / modifications after input has been received, rather they should do so after a level of agreement on what those recommendations / modifications should be has been achieved by the working group.
>  
> Best,
> Marc
>  
>  
>  
>  
> From: Marika Konings <marika.konings at icann.org> 
> Sent: Friday, September 14, 2018 10:34 AM
> To: Anderson, Marc <mcanderson at verisign.com>; Kurt Pritz <kurt at kjpritz.com>; gnso-epdp-team at icann.org
> Subject: [EXTERNAL] Re: [Gnso-epdp-team] Input on Appendix A - Input due by Sunday 16 September
>  
> Marc, apologies if there is confusion around the ask for volunteers, but the idea is that the volunteers would only start working on proposed recommendations / modifications AFTER input has been received on the issues and questions as outlined in the Google Doc. Having those volunteers identified early on could help in asking further clarifying questions based on input that is provided, but it is not the intention that these volunteers would start working on Appendix A without any guidance from the EPDP Team. I hope this clarifies. Having said that, please take a moment to review the google doc and provide your feedback on the questions identified.
>  
> Best regards,
>  
> Marika
>  
> From: Gnso-epdp-team <gnso-epdp-team-bounces at icann.org <mailto:gnso-epdp-team-bounces at icann.org>> on behalf of "Anderson, Marc via Gnso-epdp-team" <gnso-epdp-team at icann.org <mailto:gnso-epdp-team at icann.org>>
> Reply-To: "Anderson, Marc" <mcanderson at verisign.com <mailto:mcanderson at verisign.com>>
> Date: Friday, September 14, 2018 at 08:27
> To: Kurt Pritz <kurt at kjpritz.com <mailto:kurt at kjpritz.com>>, "gnso-epdp-team at icann.org <mailto:gnso-epdp-team at icann.org>" <gnso-epdp-team at icann.org <mailto:gnso-epdp-team at icann.org>>
> Subject: Re: [Gnso-epdp-team] Input on Appendix A - Input due by Sunday 16 September
>  
> Kurt and ePDP leadership team,
>  
> I would like to ask you to reconsider asking for volunteers at this stage to propose recommendations/modification (redlining) appendix A.  The working group has yet to deliberate on appendix A in any meaningful way and at a minimum should have some high level agreement on what aspects of appendix A are good and should be kept and what aspects are problematic and need to be changed, added to or removed.  I fear asking for working group members to work on redlines now will lead to the group debating the redlines rather than focusing on the substance of Appendix A and working towards consensus policy recommendations.
>  
> I understand that not getting to appendix A deliberations during Thursday’s call puts us behind scheduled and appreciate the desire to catch up.  That said, appendix A contains many of the critical components of the temporary specification.  We as a working group need to come to some level of agreement before drafting redlines or otherwise making policy recommendation on appendix A.
>  
> Best,
> Marc
>  
>  
>  
> From: Gnso-epdp-team <gnso-epdp-team-bounces at icann.org <mailto:gnso-epdp-team-bounces at icann.org>> On Behalf Of Marika Konings
> Sent: Thursday, September 13, 2018 11:31 AM
> To: gnso-epdp-team at icann.org <mailto:gnso-epdp-team at icann.org>
> Subject: [EXTERNAL] [Gnso-epdp-team] Input on Appendix A - Input due by Sunday 16 September
>  
> Dear All,
>  
> As discussed during the call today, please provide your input on the Appendix A related issues through this document:https://docs.google.com/document/d/1M2XdbXZsvfYfsxdR1xG2qT7XZ07AopJubRH8ZX1Qt3s/edit?usp=sharing <https://docs.google.com/document/d/1M2XdbXZsvfYfsxdR1xG2qT7XZ07AopJubRH8ZX1Qt3s/edit?usp=sharing>. Also, if there are volunteers to work on reviewing the input received and translating these into proposed recommendations / modifications for Appendix A, share your interest with the mailing list.
>  
> Thanks,
>  
> Caitlin, Berry and Marika
>  
> Marika Konings
> Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) 
> Email: marika.konings at icann.org <mailto:marika.konings at icann.org>  
>  
> Follow the GNSO via Twitter @ICANN_GNSO
> Find out more about the GNSO by taking our interactive courses <http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages <http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers>. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-epdp-team/attachments/20180914/dedd22f9/attachment.html>