[RDS-WHOIS2-RT] Replacement and Removal of Members
Alan Greenberg
alan.greenberg at mcgill.ca
Mon Aug 28 15:25:23 UTC 2017
Stephanie, Volker, Lili and all,
I patterned this after rules I have seen
elsewhere. I don't think it is possible to
definitively define "disruptive", but presume if
it was agreed to by a large majority in any
specific case, that was sufficient.
I cannot really imagine that we would ever
exercise such a clause, and am happy to remove it
completely. In a simpler time when we were less
focused on process, we would not even have
written such a rule and just dealt with replacing
(or removing!) someone as the situation arose.
Alan
At 28/08/2017 11:00 AM, Stephanie Perrin wrote:
>I do think that we should define
>"disruptive". I have been a minority viewpoint
>on many committees here now, largely because I
>remind people of how data protection law is
>drafted, implemented and further defined in
>policy. Given the contentious nature of the
>WHOIS debates, that has been a very lonely
>position, but since I appear to have been the
>only person with any actual experience in these
>matters on several of those committees, I am
>quite unrepentant. ICANN has a long history of
>ignoring the privacy perspective. It would not
>be hard to find 50% of people who would like to
>get rid of me, just to speed things up and not
>be bothered with the facts/alternate view. I
>think if we don't define "disruptive", we at
>least need to make it a larger majority of
>members, so I support Erika's suggestion of 70%.
>
>Stephanie Perrin
>
>On 2017-08-27 19:43, SUN Lili wrote:
>>
>>
>>Dear Alan,
>>Thanks for sharing the proposed text.
>>I'm fine with the first paragraph. For the
>>second paragraph, I believe the disputing part
>>will be how to define "disruptive", a 50% team
>>member's request for removal will be
>>persuasive. I was just wondering the meaning
>>that "the member fails to resign", would it be
>>better to change it to "the member refuses to resign"?
>>For your and other team member's consideration.
>>Thanks and regards,
>>Lili
>>
>>-----Original Message-----
>>From:
>><mailto:rds-whois2-rt-bounces at icann.org>rds-whois2-rt-bounces at icann.org
>>[mailto:rds-whois2-rt-bounces at icann.org] On Behalf Of Alan Greenberg
>>Sent: Sunday, 27 August, 2017 10:52 AM
>>To: RDS-WHOIS2-RT <mailto:rds-whois2-rt at icann.org><rds-whois2-rt at icann.org>
>>Subject: [RDS-WHOIS2-RT] Replacement and Removal of Members
>>
>>I was asked to propose wording for the section
>>of the Terms of Reference on Replacement and Removal of Members
>>
>>I would like to propose the following wording
>>for the consideration of the RT.
>>
>>Alan
>>
>>=======
>>
>>If a Review Team member is no longer able or
>>willing to serve, or if an SO/AC withdraws its
>>endorsement of the member, the SO/AC making the
>>original endorsement will be requested to
>>refill the position with a replacement member.
>>The SO/AC will make the selection according to
>>their own processes and will not be bound to
>>consider only those candidates who originally
>>applied requesting their endorsement.
>>
>>If a Review Team member is sufficiently
>>inactive or disruptive as to cause at least 50%
>>of Review Team members (excluding the member in
>>question) to request their removal, the member
>>will be asked to resign. If the member fails to
>>resign, the SO/AC that endorsed the member will
>>be requested to withdraw their endorsement and
>>replace the member. Should the SO/AC not take
>>action, the member can be removed by a 2/3
>>majority vote of the remaining Review Team members.
>>In all cases, the balloting will be carried out
>>in such a way as to not reveal how individual members voted.
>>
>>_______________________________________________
>>RDS-WHOIS2-RT mailing list
>><mailto:RDS-WHOIS2-RT at icann.org>RDS-WHOIS2-RT at icann.org
>>https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>>
>>***************************************************************************************************
>>This message, and any attachment contained, are
>>confidential and subject of legal privilege. It
>>may be used solely for the designated
>>police/justice purpose and by the individual or
>>entity to whom it is addressed. The information
>>is not to be disseminated to another agency or
>>third party without the authorâs consent, and
>>must not be retained longer than is necessary
>>for the fulfilment of the purpose for which the
>>information is to be used. All practicable
>>steps shall be taken by the recipients to
>>ensure that information is protected against
>>unauthorised access or processing. INTERPOL
>>reserves the right to enquire about the use of the information provided.
>>If you are not the intended recipient, be
>>advised that you have received this message in
>>error. In such a case, you should not print it,
>>copy it, make any use of it or disclose it, but
>>please notify us immediately and delete the message from any computer.
>>*************************************************************************************************
>>_______________________________________________
>>RDS-WHOIS2-RT mailing list
>><mailto:RDS-WHOIS2-RT at icann.org>RDS-WHOIS2-RT at icann.org
>>https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
>Content-Type: text/plain; charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>X-Microsoft-Exchange-Diagnostics:
>
>1;DM5PR03MB2714;27:Ttcvlt6OhgspplyWCJnDw5kVt6JuRql5pHW/wKKUAjfa7+7PNyqISww30ehOMuAo4vtZrK5VNBM6ozb4OD3rAp5g0roDa80tXEgbuSIo9TfoDZ5C/EL2L0GKUPzM3mvN
>X-Microsoft-Antispam-Mailbox-Delivery:
>
>ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160513016)(750103)(520002050)(701014)(400001001223)(400125100095)(61617095)(400001002128)(400125200095);
>
>_______________________________________________
>RDS-WHOIS2-RT mailing list
>RDS-WHOIS2-RT at icann.org
>https://mm.icann.org/mailman/listinfo/rds-whois2-rt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20170828/b7aa5daf/attachment-0001.html>
More information about the RDS-WHOIS2-RT
mailing list