<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">+1 to "Obfuscatia."</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 29, 2016 at 2:16 PM, avri doria <span dir="ltr"><<a href="mailto:avri@apc.org" target="_blank">avri@apc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi,<br>
<br>
In answer to Andrews question, I do not believe a PDP can replace a<br>
Review. Reviews are done by a full community group and PDPs are done by<br>
one SO. Though each their processes may be open to anyone and everyone,<br>
PDPs may allow for much broader group membership. They have different<br>
processes and different goals. Another point, the output of a Review is<br>
often input to a PDP as well as other processes. There may be<br>
dependencies between an ongoing review and a ongoing PDP, but I do not<br>
think the bylaws need to discuss that.<br>
<br>
Milton, one good thing about having it in the bylaws is that bylaws are<br>
mutable.<br>
<br>
As for the reviews coincident with the transition, I think we should<br>
just do them. A level setting for the transition would be a good thing<br>
to have.<br>
<br>
<br>
signed:<br>
Obfuscatia<br>
<div><div class="h5"><br>
On 29-Apr-16 12:02, Mueller, Milton L wrote:<br>
> Andrew:<br>
> You've hit a nail on a head, and can expect some obfuscation to follow.<br>
><br>
> The original Affirmation of Commitments essentially contained a promise - extracted out of the USG by one stakeholder group and imposed on the rest of us without any participation - that ICANN would never change its basic Whois policy. This is one reason why I've never been thrilled about incorporating the AoC into the accountability reform process. The AoC contained good accountability and transparency language but also got attached to it a bunch of commitments that essentially circumvented the actual bottom up policy process.<br>
><br>
> For that reason I would strongly support your suggestion that a review of Whois/RDS not duplicate a PDP.<br>
><br>
> --MM<br>
><br>
>> -----Original Message-----<br>
>> From: <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><br>
>> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>] On Behalf Of<br>
>> Andrew Sullivan<br>
>> Sent: Thursday, April 28, 2016 9:13 AM<br>
>> To: <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><br>
>> Subject: [CCWG-ACCT] The whois/RDS-RT bylaw vs. current activities<br>
>><br>
>> Hi,<br>
>><br>
>> In thinking about the way the bylaws require the regular RTs and how those<br>
>> might interact with other processes, I'm wondering whether we think it would<br>
>> be consistent with the report to say that, if a PDP is going on about any topic<br>
>> that is subject to regular RT, then the PDP can be counted as fulfilling the<br>
>> purposes of the RT?<br>
>><br>
>> It seems to me that this is consistent with the point of the regular RT<br>
>> requirement (i.e. ensuring that the review happens in a timely way) without<br>
>> entailing that we waste time, money, and energy in multiple, potentially<br>
>> conflicting efforts on the same topic.<br>
>><br>
>> Have I missed something?<br>
>><br>
>> Best regards,<br>
>><br>
>> A<br>
>><br>
>> --<br>
>> Andrew Sullivan<br>
>> <a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
>> _______________________________________________<br>
>> Accountability-Cross-Community mailing list Accountability-Cross-<br>
>> <a href="mailto:Community@icann.org">Community@icann.org</a><br>
>> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
> _______________________________________________<br>
> Accountability-Cross-Community mailing list<br>
> <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
><br>
<br>
<br>
<br>
</div></div>---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antivirus</a><br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</div></div></blockquote></div><br></div>