[gnso-rds-pdp-wg] Next Gen RDS - Update from Leadership Team

[John Bambenek]

“You can convince some insider to carry your concern while they deliberate in private.”

That is exactly my point. You’ve excluded outsiders.

--
John Bambenek

> On Oct 11, 2018, at 04:55, Michele Neylon - Blacknight <michele at blacknight.com> wrote:
> 
> John
>  
> That isn’t true. Every SO and AC within ICANN has representation. You and anyone else can channel your concerns via your respective constituency, stakeholder group or AC.
> Also as is normal with any GNSO Working Group the interim report and final report will be open for public comment.
>  
> Regards
>  
> Michele
>  
> --
> Mr Michele Neylon
> Blacknight Solutions
> Hosting, Colocation & Domains
> https://www.blacknight.com/
> https://blacknight.blog/
> Intl. +353 (0) 59  9183072
> Direct Dial: +353 (0)59 9183090
> Personal blog: https://michele.blog/
> Some thoughts: https://ceo.hosting/
> -------------------------------
> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
> Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845
>  
> From: gnso-rds-pdp-wg <gnso-rds-pdp-wg-bounces at icann.org> on behalf of John Bambenek via gnso-rds-pdp-wg <gnso-rds-pdp-wg at icann.org>
> Reply-To: John Bambenek <jcb at bambenekconsulting.com>
> Date: Wednesday 10 October 2018 at 23:50
> To: Dotzero <dotzero at gmail.com>
> Cc: RDS PDP WG <gnso-rds-pdp-wg at icann.org>
> Subject: Re: [gnso-rds-pdp-wg] Next Gen RDS - Update from Leadership Team
>  
> I did take notice that the new EPDP specifically excludes all outsiders thus ensuring that anyone who actually uses whois will not be represented.
> 
> --
> John Bambenek
> 
> On Oct 10, 2018, at 17:28, Dotzero <dotzero at gmail.com> wrote:
> 
> The proposed termination document reflects the reality of what has occurred. I'd like to thank everyone else for their efforts. I know that we had some disagreements and the process sometimes was painful.
>  
> Michael Hammer
>  
> On Wed, Oct 10, 2018 at 9:30 AM Anderson, Marc via gnso-rds-pdp-wg <gnso-rds-pdp-wg at icann.org> wrote:
> Fellow Next Gen RDS members,
>  
> In March of this year the RDS PDP leadership team canceled working group meetings, effectively putting the group on hold.  This decision was made because we heard from ICANN org that it was considering instituting a temporary policy that would greatly impact our work.  Out of respect for members’ time it didn’t make sense to continue deliberations.
>  
> Since then, the ICANN board did approve a temporary specification (https://www.icann.org/resources/pages/gtld-registration-data-specs-en).  Subsequent to that, the GNSO council initiated an expedited PDP on that temporary specification (https://www.icann.org/news/announcement-2018-07-19-en).
>  
> Given all this, the RDS PDP leadership team feels it doesn’t make sense for the working group to continue and is recommending termination.  The GNSO PDP manual allows for termination by the working group and requires a written “Termination Summary” delivered to the GNSO council via the council liaison.  The manual provides “changing circumstances” as an example of a reason for termination which this certainly qualifies as.
>  
> Attached you will find a proposed “Termination Summary” for the RDS PDP working group.  The leadership team plans to deliver by 12 October so the GNSO council can have it on their agenda for ICANN 63.  Please let the leadership team know if you have questions or feedback.
>  
> Many thanks for your hard work on this project.
>  
> Best,
> RDS Leadership team
>  
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20181011/fe003cf2/attachment.html>