<div dir="auto"><div dir="auto">Dear Owen</div><div dir="auto"><br></div><div dir="auto">You may not see a correlation but to make sure of the postponement of the Co-Chair election, this can be done. Besides, not all have access to make use of internet resources to log on for the online meeting.</div><div dir="auto"><br></div><div dir="auto">Thank you.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 21, 2020, 12:20 PM <<a href="mailto:rpd-request@afrinic.net">rpd-request@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send RPD mailing list submissions to<br>
<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of RPD digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: RPD Digest, Vol 166, Issue 78 (Owen DeLong)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 21 Jul 2020 09:19:57 -0700<br>
From: Owen DeLong <<a href="mailto:owen@delong.com" target="_blank" rel="noreferrer">owen@delong.com</a>><br>
To: Paclab <<a href="mailto:ezekielj20@gmail.com" target="_blank" rel="noreferrer">ezekielj20@gmail.com</a>><br>
Cc: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Subject: Re: [rpd] RPD Digest, Vol 166, Issue 78<br>
Message-ID: <<a href="mailto:A29D0311-4D0D-4E13-83B7-91451DF27137@delong.com" target="_blank" rel="noreferrer">A29D0311-4D0D-4E13-83B7-91451DF27137@delong.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I don?t see the correlation. This is a small debate over how exactly to address the issues while staying as close<br>
to the procedures in the CPM as possible. It?s not a big deal or anything sufficient to justify cancelling the online<br>
meeting or delaying it for an unknown period of time.<br>
<br>
Owen<br>
<br>
<br>
> On Jul 21, 2020, at 07:19 , Paclab <<a href="mailto:ezekielj20@gmail.com" target="_blank" rel="noreferrer">ezekielj20@gmail.com</a>> wrote:<br>
> <br>
> I forsaw this happening, that's why I was insisting on the cancellation on online meeting till the pandemic is over<br>
> <br>
> On Tue, Jul 21, 2020 at 6:59 AM <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>>> wrote:<br>
> Send RPD mailing list submissions to<br>
> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
> <br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <mailto:<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>><br>
> <br>
> You can reach the person managing the list at<br>
> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a> <mailto:<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>><br>
> <br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of RPD digest..."<br>
> <br>
> <br>
> Today's Topics:<br>
> <br>
> 1. Re: Co-Chair Election Process (Fernando Frediani)<br>
> <br>
> <br>
> ----------------------------------------------------------------------<br>
> <br>
> Message: 1<br>
> Date: Tue, 21 Jul 2020 09:58:31 -0300<br>
> From: Fernando Frediani <<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a>>><br>
> To: "rpd >> AfriNIC Resource Policy" <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>>><br>
> Subject: Re: [rpd] Co-Chair Election Process<br>
> Message-ID: <<a href="mailto:2606ca05-56e7-38d3-7168-819f7db79b09@gmail.com" target="_blank" rel="noreferrer">2606ca05-56e7-38d3-7168-819f7db79b09@gmail.com</a> <mailto:<a href="mailto:2606ca05-56e7-38d3-7168-819f7db79b09@gmail.com" target="_blank" rel="noreferrer">2606ca05-56e7-38d3-7168-819f7db79b09@gmail.com</a>>><br>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
> <br>
> On 21/07/2020 02:06, Owen DeLong wrote:<br>
> > Yes, but that proposal could be to vary the chair election process <br>
> > just as much as to vary anything else in the document.<br>
> <br>
> Yes, as long it is conducted under a policy proposal discussion <br>
> following 3.6 no problem at all.<br>
> <br>
> Now the main problem I guess is to reach consensus on something as many <br>
> people seem too afraid of anything. So why I suggested something <br>
> strictly simple that resolves the current scenario, even temporarily <br>
> until we can have a proper proposal discussed later that resolves it <br>
> long term.<br>
> <br>
> However some people keep suggesting to extend the Co-Chair term without <br>
> willing to go through a simple show of hands in a remote event as the <br>
> PDP says. So how we suppose to do this? Regardless the type of job the <br>
> person is doing there is not other way to extend his term other than the <br>
> process outlined in the PDP.<br>
> <br>
> I don't see any other ways out of it.<br>
> <br>
> Fernando<br>
> <br>
> ><br>
> > Owen<br>
> ><br>
> >> Fernando<br>
> >><br>
> >> On 21/07/2020 00:05, Owen DeLong wrote:<br>
> >>><br>
> >>><br>
> >>>> On Jul 20, 2020, at 6:22 PM, Fernando Frediani <br>
> >>>> <<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a>> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a>>>> wrote:<br>
> >>>><br>
> >>>> Hi Owen. Sorry I don't really read the 3.6 the same way as you. 3.6 <br>
> >>>> in my view wasn't thought for situation like this. It's being glued <br>
> >>>> for the occasion that's not the case. 3.6 is about how the <br>
> >>>> proposals are conducted, reviewed and passed within this forum in a <br>
> >>>> exceptional situation (pretty much where we are). All points <br>
> >>>> mentioned there have to do with proposals. We are not discussing or <br>
> >>>> advancing a proposal right now.<br>
> >>>><br>
> >>><br>
> >>> That?s your special interpretation. It?s not what a plain english <br>
> >>> reading of the language says.<br>
> >>><br>
> >>> 1.The PDP is in the document containing 3.6. The PDP is a process.<br>
> >>> 2.The co-chair election process is in the document containing 3.6. <br>
> >>> The co-chair election process is a process.<br>
> >>> 3.3.6 says ?The process outlined in this document??.<br>
> >>><br>
> >>>><br>
> >>>> What CAN actually be done within 3.6 is someone to properly present <br>
> >>>> a proposal to amend the PDP and fix the issues we are discussing <br>
> >>>> here and then have this proposal treated under 3.6 (with no less <br>
> >>>> than 4 weeks including the Last Call - which coincides with your <br>
> >>>> point number 3 below).<br>
> >>>><br>
> >>> I suppose that could also work, though it?s rather indirect and adds <br>
> >>> (unnecessary IMHO) complexity.<br>
> >>>><br>
> >>>> In my opinion proposal AFPUB-2019-GEN-007-DRAFT01 is ready for it, <br>
> >>>> but I guess that may not reach consensus. So a much shorter <br>
> >>>> proposal with just the essential we need to resolve this situation <br>
> >>>> is the way to go under 3.6. Would that match with what you are <br>
> >>>> trying to put ?<br>
> >>>><br>
> >>><br>
> >>> IMHO, AFPUB-2019-GEN-007-DRAFT01 is a fatally flawed proposal and I <br>
> >>> would not support it as currently written.<br>
> >>><br>
> >>> I think a much more direct proposal to clarify an expanded scope of <br>
> >>> 3.6 (closer to my interpretation instead of your rather narrow <br>
> >>> interpretation) would be the most likely to gain consensus, frankly. <br>
> >>> I think such is unnecessary, but _IF_ you insist on the (oddly) <br>
> >>> narrow interpretation of 3.6 you have put forth, then?<br>
> >>><br>
> >>> Owen<br>
> >>><br>
> >>>><br>
> >>>> Fernando<br>
> >>>><br>
> >>>> On 20/07/2020 21:52, Owen DeLong wrote:<br>
> >>>>><br>
> >>>>><br>
> >>>>>> On Jul 20, 2020, at 10:00 AM, Fernando Frediani <br>
> >>>>>> <<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a>> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a>>>> wrote:<br>
> >>>>>><br>
> >>>>>> On 20/07/2020 13:39, Owen DeLong wrote:<br>
> >>>>>>><br>
> >>>>>>> <clip><br>
> >>>>>>><br>
> >>>>>>> This is an absurd claim. The standard (as you mention below) is <br>
> >>>>>>> a ?raise of hands? vote. This mechanism even in person does not <br>
> >>>>>>> allow people to verify that their vote was cast correctly, nor <br>
> >>>>>>> is it fully auditable (indeed, it has no audit trail and is not <br>
> >>>>>>> at all audible).<br>
> >>>>>>><br>
> >>>>>>> Placing more stringent requirements than exist on the current <br>
> >>>>>>> system as an acceptance criteria for a system deployed urgently <br>
> >>>>>>> in a time of crisis makes little sense to me.<br>
> >>>>>> You are not making the things easier given the circumstances and <br>
> >>>>>> all has been been discussed here.<br>
> >>>>>> What is being said is analogous to raise of hand and is also a <br>
> >>>>>> indisputable way to eliminate most possible fraud that have been <br>
> >>>>>> pointed.<br>
> >>>>><br>
> >>>>> It is not my goal to make things easier for you or even <br>
> >>>>> necessarily easier in general.<br>
> >>>>><br>
> >>>>> It is my goal to achieve the best possible outcome through a <br>
> >>>>> mechanism that comes as close to applying the PDP rules as possible.<br>
> >>>>><br>
> >>>>>>>> 4 - In order to either choose another Co-Chair or to extend the <br>
> >>>>>>>> current one term there must be a vote with raise of hands. <br>
> >>>>>>>> There is no other way out of the PDP this can be done.<br>
> >>>>>>>><br>
> >>>>>>><br>
> >>>>>>> This statement ignores CPM section 3.6:<br>
> >>>>>>><br>
> >>>>>>><br>
> >>>>>>> 3.6??Varying the Process<br>
> >>>>>>><br>
> >>>>>>> The process outlined in this document may vary in the case<br>
> >>>>>>> of an emergency. Variance is for use when a one-time waiving<br>
> >>>>>>> of some provision of this document is required.<br>
> >>>>>>><br>
> >>>>>>> 1. The decision to vary the process is taken by a Working<br>
> >>>>>>> Group Chair.<br>
> >>>>>>> 2. There must be an explanation about why the variance is<br>
> >>>>>>> needed.<br>
> >>>>>>> 3. The review period, including the Last Call, shall not be<br>
> >>>>>>> less than four weeks.<br>
> >>>>>>> 4. If there is consensus, the policy is approved and it<br>
> >>>>>>> must be presented at the next Public Policy Meeting.<br>
> >>>>>>><br>
> >>>>>>><br>
> >>>>>>> Clearly this is the kind of exceptional circumstance in which <br>
> >>>>>>> some variance could be justified.<br>
> >>>>>> Sorry I don't see 3.6 applying to this situation on *any* of <br>
> >>>>>> points mentioned. This section is about how the policies <br>
> >>>>>> discussion, review, last call, etc work? 1) As I understand this <br>
> >>>>>> decision is not up to the Chairs to take 2)Yes, we are working on <br>
> >>>>>> the explanation, but who will give it ? Normally is whoever take <br>
> >>>>>> the decision. 3) Nothing to do with elections 4) Nothing to do <br>
> >>>>>> with the current scenario. There is no proper policy under <br>
> >>>>>> discussion to be approved, only a discussion of what to do about <br>
> >>>>>> the next elections.<br>
> >>>>><br>
> >>>>> It applies to all of the CPM ("The process outlined in this <br>
> >>>>> document may vary??).<br>
> >>>>> 1. If not the co-chairs, then who?<br>
> >>>>> 2. I think the explanation is well understood? ?Because in person <br>
> >>>>> meeting during the COVID crisis is impossible.?<br>
> >>>>> 3. I?m not so sure about this. Whatever election process we decide <br>
> >>>>> on should be put to a final community comment<br>
> >>>>> period of some form. I see no reason that should be less than 4 weeks.<br>
> >>>>> 4. So you?re saying that the determination of how to (or whether <br>
> >>>>> to) conduct co-chair elections should be made<br>
> >>>>> by some other method than community consensus and should not be <br>
> >>>>> considered policy at least for this meeting?<br>
> >>>>><br>
> >>>>> How does that work?<br>
> >>>>><br>
> >>>>><br>
> >>>>>>><br>
> >>>>>>> I still say that a (virtual) raising of hands using the <br>
> >>>>>>> mechanisms available in nearly every conferencing system capable <br>
> >>>>>>> of supporting<br>
> >>>>>>> this meeting has the following advantages:<br>
> >>>>>>> q<br>
> >>>>>>> 1.Only meeting attendees may vote.<br>
> >>>>>>> 2.Botting your meeting attendance would be reasonably difficult, <br>
> >>>>>>> so it would be difficult for a person to stuff the ballot box.<br>
> >>>>>>> 3.It does meet the literal requirements of the existing PDP.<br>
> >>>>>>> 4.If we place reasonable bounds on meeting registration, we can <br>
> >>>>>>> avoid the so-called ?sleeper cell? effect that some have<br>
> >>>>>>> put forth as a concern. (Personally, I think this is less likely <br>
> >>>>>>> in a virtual meeting anyway).<br>
> >>>>>>> 5.If we place reasonable bounds on meeting registration, we also <br>
> >>>>>>> manage to prevent (2) from being a concern.<br>
> >>>>>>> 6.By ?reasonable bounds?, I mean pick a date certain in the past <br>
> >>>>>>> by which one must have been subscribed to RPD.<br>
> >>>>>>> Each email subscribed to RPD is entitled to one corresponding <br>
> >>>>>>> meeting registration if they choose to. No subscribed<br>
> >>>>>>> email, no registration for the meeting.<br>
> >>>>>> I quiet like this idea, and that is exactly which is under <br>
> >>>>>> discussion in one of the policies that should advance, but this <br>
> >>>>>> is not backed in any part of PDP as far as I know as the moment. <br>
> >>>>>> Who will determine what date is this ?<br>
> >>>>><br>
> >>>>> This would most certainly be a variation of the PDP to meet the <br>
> >>>>> emergency as it exists which would be permitted under 3.6, so, yes,<br>
> >>>>> my argument here depends on my argument above which you have <br>
> >>>>> claimed you are not buying. However, hopefully with my expansions on<br>
> >>>>> the topic above, I can perhaps convince you to change your mind <br>
> >>>>> and recognize that without something like that, we literally box<br>
> >>>>> ourselves into a situation with no way forward until such time as <br>
> >>>>> we can arrange an in-person meeting. Personally, I think that?s<br>
> >>>>> far from the best outcome.<br>
> >>>>><br>
> >>>>>>> 7.My suggestions for the date certain would be the first day of <br>
> >>>>>>> the originally scheduled in person AIS 2020 (May 31) or<br>
> >>>>>>> the originally scheduled first day of the public policy meeting <br>
> >>>>>>> (June 8 IIRC).<br>
> >>>>>><br>
> >>>>>> This would make sense if there was basis for it, but currently <br>
> >>>>>> there is AFAIK.<br>
> >>>>>><br>
> >>>>> The basis for it is 3.6. Read the CPM carefully read 3.6. It?s not <br>
> >>>>> rocket science. The CPM describes all of the policies, the PDP, <br>
> >>>>> and the co-chair election process within the one document. Section <br>
> >>>>> 3.6 provides for variance of the process[sic] should be processes <br>
> >>>>> within<br>
> >>>>> the document. That includes the co-chair election process unless <br>
> >>>>> you can show me why it does not.<br>
> >>>>><br>
> >>>>> Owen<br>
> >>>>><br>
> >>>>>> Fernando<br>
> >>>>>><br>
> >>>>>>><br>
> >>>>>>> If anyone has a reason they don?t think this is viable, please <br>
> >>>>>>> express it. So far, I?ve seen lots of calls for other solutions, <br>
> >>>>>>> but this<br>
> >>>>>>> seems to be the approach with the fewest drawbacks and which can <br>
> >>>>>>> easily be implemented in time.<br>
> >>>>>>><br>
> >>>>>>> Owen<br>
> >>>>>>><br>
> >>>>>>>><br>
> >>>>>>>> Regards<br>
> >>>>>>>> Fernando<br>
> >>>>>>>><br>
> >>>>>>>> On 20/07/2020 03:06, Daniel Yakmut wrote:<br>
> >>>>>>>>> Dear All,<br>
> >>>>>>>>><br>
> >>>>>>>>> We arrive at the airport and I will be turning the simple <br>
> >>>>>>>>> matter placed on the table into a circus. The simple matter was:<br>
> >>>>>>>>><br>
> >>>>>>>>> 1. We will have AIS 2020 online and in September.<br>
> >>>>>>>>> 2. A Co-chair's ?tenure has already ended. So an electronic <br>
> >>>>>>>>> election is being proposed as part of the AIS 2020 Agenda. The <br>
> >>>>>>>>> question is, is this possible?<br>
> >>>>>>>>> 3. It is a fact that the Co-chair is currently serving within <br>
> >>>>>>>>> an extended period.<br>
> >>>>>>>>> 4. We now agree that the introduction of e-voting is <br>
> >>>>>>>>> inevitable, as demonstrated by the pandemic.<br>
> >>>>>>>>><br>
> >>>>>>>>> However it is clear that<br>
> >>>>>>>>> 1. We are going to have an online meeting , as nobody has <br>
> >>>>>>>>> disagreed to that.<br>
> >>>>>>>>> 2. There is a strong advocacy, for a process to include <br>
> >>>>>>>>> e-voting in the Region, but the timing is short. Therefore we <br>
> >>>>>>>>> need to commence the plan of creating an enabling atmosphere <br>
> >>>>>>>>> to integrate e-voting.<br>
> >>>>>>>>> 3. We need to ratify the extended period for a co-chair <br>
> >>>>>>>>> tentatively for 12months. Which he has spent a month or so <br>
> >>>>>>>>> already.<br>
> >>>>>>>>> 4. Ensure we have an acceptable e-voting system ready for the <br>
> >>>>>>>>> next date of election.<br>
> >>>>>>>>> 5. Let agreed clearly on this simple issue and prepare for the <br>
> >>>>>>>>> coming meeting.<br>
> >>>>>>>>><br>
> >>>>>>>>> Simply<br>
> >>>>>>>>> Daniel<br>
> >>>>>>>>><br>
> >>>>>>>>> On Jul 19, 2020 11:20 PM, "Fernando Frediani" <br>
> >>>>>>>>> <<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a>> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a> <mailto:<a href="mailto:fhfrediani@gmail.com" target="_blank" rel="noreferrer">fhfrediani@gmail.com</a>>>> wrote:<br>
> >>>>>>>>><br>
> >>>>>>>>> I have read this message and several questions come to<br>
> >>>>>>>>> mind as for example:<br>
> >>>>>>>>><br>
> >>>>>>>>> - What basis was used to say "it was overwhelmingly"<br>
> >>>>>>>>> rejected ?<br>
> >>>>>>>>><br>
> >>>>>>>>> - Who actuallty represents the "current" community to<br>
> >>>>>>>>> state it was "totally rejected" ?<br>
> >>>>>>>>><br>
> >>>>>>>>> - Whats basis was used to say that it would not work in<br>
> >>>>>>>>> the region if that works in several other places and RIRs<br>
> >>>>>>>>> including, with auditable systems ?<br>
> >>>>>>>>><br>
> >>>>>>>>> - Whats basis is used to say rhe community that voted for<br>
> >>>>>>>>> the current Co-Chair in Kampla has the same confidence in<br>
> >>>>>>>>> him and that he would win ? It seems more a personal wish<br>
> >>>>>>>>> than anything based on fact or logic.<br>
> >>>>>>>>><br>
> >>>>>>>>> - Even in order to extend the current Co-Chair term the<br>
> >>>>>>>>> PDP MUST be followed and there are no other ways written<br>
> >>>>>>>>> there other than another vote. Otherwise how can this be<br>
> >>>>>>>>> done ?<br>
> >>>>>>>>><br>
> >>>>>>>>> Fernando<br>
> >>>>>>>>><br>
> >>>>>>>>><br>
> >>>>>>>>> On Sun, 19 Jul 2020, 18:08 Emem William,<br>
> >>>>>>>>> <<a href="mailto:dwizard65@gmail.com" target="_blank" rel="noreferrer">dwizard65@gmail.com</a> <mailto:<a href="mailto:dwizard65@gmail.com" target="_blank" rel="noreferrer">dwizard65@gmail.com</a>> <mailto:<a href="mailto:dwizard65@gmail.com" target="_blank" rel="noreferrer">dwizard65@gmail.com</a> <mailto:<a href="mailto:dwizard65@gmail.com" target="_blank" rel="noreferrer">dwizard65@gmail.com</a>>>> wrote:<br>
> >>>>>>>>><br>
> >>>>>>>>> Dear All,<br>
> >>>>>>>>><br>
> >>>>>>>>> I can? recollect that a similar proposal was proposed<br>
> >>>>>>>>> as a policy and it was overwhelmingly rejected in<br>
> >>>>>>>>> Angola. The current community totally rejected the<br>
> >>>>>>>>> policy no one except the authors supported the idea<br>
> >>>>>>>>> because we know it can't work in this region. Using<br>
> >>>>>>>>> online voting now would be like passing the policy<br>
> >>>>>>>>> using the backdoor. Am sure Jordie would like this<br>
> >>>>>>>>> idea and hence his enthusiasm. However my candid<br>
> >>>>>>>>> opinion is that we can't do this. The most appropriate<br>
> >>>>>>>>> way forward is to allow the Co chair who has been<br>
> >>>>>>>>> doing a fantastic job to continue for another 12<br>
> >>>>>>>>> months or till the next face to face meeting. The<br>
> >>>>>>>>> community that voted him in Kampala still have<br>
> >>>>>>>>> confidence in him. In any case even with an online<br>
> >>>>>>>>> election he would still likely win but I don't want<br>
> >>>>>>>>> polices to be passed through the back door. Therefore<br>
> >>>>>>>>> I think the most appropriate way for this has been<br>
> >>>>>>>>> suggested as an extension for the co-chair who's seat<br>
> >>>>>>>>> would have been contested.<br>
> >>>>>>>>><br>
> >>>>>>>>> Cheers.<br>
> >>>>>>>>><br>
> >>>>>>>>> Emem E. William<br>
> >>>>>>>>><br>
> >>>>>>>>> _______________________________________________<br>
> >>>>>>>>> RPD mailing list<br>
> >>>>>>>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >>>>>>>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
> >>>>>>>>> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>>><br>
> >>>>>>>>><br>
> >>>>>>>>><br>
> >>>>>>>>> _______________________________________________<br>
> >>>>>>>>> RPD mailing list<br>
> >>>>>>>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >>>>>>>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
> >>>>>>>>> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>>><br>
> >>>>>>>>><br>
> >>>>>>>> _______________________________________________<br>
> >>>>>>>> RPD mailing list<br>
> >>>>>>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >>>>>>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
> >>>>>>><br>
> >>>>>> _______________________________________________<br>
> >>>>>> RPD mailing list<br>
> >>>>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >>>>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
> >>>>><br>
> >>>> _______________________________________________<br>
> >>>> RPD mailing list<br>
> >>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
> >>><br>
> >> _______________________________________________<br>
> >> RPD mailing list<br>
> >> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>>><br>
> >> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
> ><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20200721/5d88410b/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20200721/5d88410b/attachment.html</a> <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20200721/5d88410b/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20200721/5d88410b/attachment.html</a>>><br>
> <br>
> ------------------------------<br>
> <br>
> Subject: Digest Footer<br>
> <br>
> _______________________________________________<br>
> RPD mailing list<br>
> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a> <<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a>><br>
> <br>
> <br>
> ------------------------------<br>
> <br>
> End of RPD Digest, Vol 166, Issue 78<br>
> ************************************<br>
> _______________________________________________<br>
> RPD mailing list<br>
> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20200721/099c5892/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20200721/099c5892/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br>
<br>
------------------------------<br>
<br>
End of RPD Digest, Vol 166, Issue 83<br>
************************************<br>
</blockquote></div>