May 2020 - AFRI-Discuss - lists.icann.org

Call for Topics: Joint AFRALO-AfrICANN meeting - ICANN68 (Virtual)
by Sarah Kiden June 5, 2020

June 5, 2020

Dear Colleagues, I hope this email finds you well. The ICANN68 Meeting is scheduled for 22-25 June 2020. This meeting will be virtual. As with previous ICANN meetings, we plan to hold the Joint AFRALO-AfrICANN meeting. We would like to invite you to submit topics for this session. Our previous statements have focused on issues like: Domain Name System (DNS) Abuse, evolving the ICANN Multistakeholder model, New gTLD Subsequent Procedures, enhancing ICANN accountability, etc. Please see our previous statements here <https://community.icann.org/display/AFRALO/Joint+AFRALO-AfrICANN+Statements…> . Please see our proposed timeline: Call for topics and drafting team: 15 - 22 May 2020 Drafting of Statement: 23 May - 6 June 2020 Send Statement to Staff for translation: 7 June 2020 Please send your suggested topics by Friday, 22 May 2020, after which the drafting team will be constituted to prepare a draft statement that will be shared with the rest of the members. If you would like to join the drafting team, kindly notify us offlist. Looking forward to your contributions. Kind regards, Sarah Kiden AFRALO Secretariat

1 1

Re: [AFRI-Discuss] [AFRALO-Newsletter] Invitation: AFRALO Newsletter: Submission of quarterly contributions/... @ Monthly on day 16 (afralo-newsletter@icann.org)
by Sarah Kiden June 3, 2020

June 3, 2020

Hello all, Thank you for joining the just concluded AFRALO Newsletter team call. As agreed during the call, we are sending a reminder for you to send us your articles for volume 3 of the newsletter. This volume will cover articles and reports for the months of April, May and June. If you have organised webinars during this period, please share brief reports and links. Content can be submitted in both English and French. We have extended the deadline by a week so please send your articles by 3 June 2020. Regards, Sarah On Fri, May 15, 2020 at 4:17 PM <remmyn(a)gmail.com> wrote: > *You have been invited to the following event.* > AFRALO Newsletter: Submission of quarterly contributions/articles > > *When* > Monthly on day 16 > *Calendar* > afralo-newsletter(a)icann.org > *Who* > • > remmyn(a)gmail.com - organizer > • > hilaliaziz(a)yahoo.fr > • > olivierkouami(a)gmail.com > • > afralo-newsletter(a)icann.org > • > seun.ojedeji(a)gmail.com > • > afri-discuss(a)atlarge-lists.icann.org > more details » > <https://www.google.com/calendar/event?action=VIEW&eid=MGMzbzFwa3E2YnFscnQyc…> > Kindly be reminded that deadline for submission of contributions/articles > for the forthcoming quarterly AFRALO Newsletter are as follows: > > April 10, 2020 – Call for submission of content by allcontributors (chair, > secretariat and editorial team) > > May 10 – Collation of materials > > May 24 – First draft out for comments > > June 7 – Corrections and Update > > June 14 – Second draft out for submission to ICANN Staff > > > Do well to send yours today. > > You are always appreciated. > > Remmy Nweke > Group Executive Editor > DigitalSENSE Business News > remmyn(a)gmail.com > editor_ls(a)digitalsenseafrica.com.ng > 08023122558 > > Going (afralo-newsletter(a)icann.org)? All events in this series: *Yes > <https://www.google.com/calendar/event?action=RESPOND&eid=MGMzbzFwa3E2YnFscn…> > - Maybe > <https://www.google.com/calendar/event?action=RESPOND&eid=MGMzbzFwa3E2YnFscn…> > - No > <https://www.google.com/calendar/event?action=RESPOND&eid=MGMzbzFwa3E2YnFscn…>* > more options » > <https://www.google.com/calendar/event?action=VIEW&eid=MGMzbzFwa3E2YnFscnQyc…> > > Invitation from Google Calendar <https://www.google.com/calendar/> > > You are receiving this courtesy email at the account > afralo-newsletter(a)icann.org because you are an attendee of this event. > > To stop receiving future updates for this event, decline this event. > Alternatively you can sign up for a Google account at > https://www.google.com/calendar/ and control your notification settings > for your entire calendar. > > Forwarding this invitation could allow any recipient to send a response to > the organizer and be added to the guest list, or invite others regardless > of their own invitation status, or to modify your RSVP. Learn More > <https://support.google.com/calendar/answer/37135#forwarding>. > _______________________________________________ > AFRALO-Newsletter mailing list > AFRALO-Newsletter(a)icann.org > https://mm.icann.org/mailman/listinfo/afralo-newsletter > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on.

7 7

Call for Comments by 26 May 23:59 UTC: AFRALO Statement on ICANN Africa Regional Plan for Fiscal Years 2021-2025
by Evin Erdogdu May 25, 2020

May 25, 2020

Dear AFRALO Community, This is a kind reminder to please provide final comments on the AFRALO statement regarding the ICANN Africa Regional Plan for Fiscal Years 2021-2025<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+ICA…>. The Google Doc fort he AFRALO statement (comment-only) may be found at this link: https://docs.google.com/document/d/1XhJscp3DJO9EwPvKrZYpNdq0ymxkToaqSnX_dnn… As well as on the At-Large workspace<https://community.icann.org/x/EYHsBw> for the ICANN Public Comment. Please provide your comments, if any, by Tuesday, 26 May at 23:59 UTC. Kind Regards, Evin

2 1

Happy Eid-al-Fitr
by Seun Ojedeji May 25, 2020

May 25, 2020

Dear Colleagues, While in-house holiday has become statutory for some of us due to the pandemic :-) Nevertheless, here is to wish us all a happy holiday during the Eid period and a happy Eid-al-Fitr to all our Muslim colleagues Eid Mubarak! Celebrate Safely! Regards Chair AFRALO -- ------------------------------------------------------------------------ *Seun Ojedeji, Mobile: +2348035233535* Bringing another down does not take you up - think about your action!

4 3

Happy Eid Mubarak !!!
by Alex Corenthin May 25, 2020

May 25, 2020

Dear Muslims friends, Happy Eid Mubarak! Wishing everyone happy holidays, stay safe and pray to your Almighty. I wish you the best for you and your families during this period of fight against the pandemic. May God help us to overcome this crisis. Chers amis musulmans, Joyeux Eid Mubarak! En souhaitant à tous de joyeuses fêtes, restez en sécurité et priez votre Tout-Puissant. Je vous souhaite le meilleur pour vous et vos familles en cette période de lutte contre la pandémie. Que Dieu nous aide à surmonter cette crise. Dr Alex Corenthin

3 2

Re: [AFRI-Discuss] Call for Topics: Joint AFRALO-AfrICANN meeting - ICANN68 (Virtual)
by Sarah Kiden May 25, 2020

May 25, 2020

Hello all, We have received 2 suggestions so far about the topic for the meeting. Both topics (suggested by Liz Orembo and Barrack Otieno) are about participation in ICANN during this pandemic. Barrack suggested this: Enhancing the resilience of DNS Infrastructure in the face of pandemics. Kindly let us know if this topic is okay. The deadline to submit topics is tomorrow, *22 May 2020*. We have also received some expressions of interest to join the drafting team. If you are interested, please reach out offlist. Regards, Sarah On Fri, May 15, 2020 at 11:26 AM Sarah Kiden <skiden(a)gmail.com> wrote: > Dear Colleagues, > > I hope this email finds you well. The ICANN68 Meeting is scheduled for > 22-25 June 2020. This meeting will be virtual. As with previous ICANN > meetings, we plan to hold the Joint AFRALO-AfrICANN meeting. We would like > to invite you to submit topics for this session. Our previous statements > have focused on issues like: Domain Name System (DNS) Abuse, evolving the > ICANN Multistakeholder model, New gTLD Subsequent Procedures, enhancing > ICANN accountability, etc. Please see our previous statements here > <https://community.icann.org/display/AFRALO/Joint+AFRALO-AfrICANN+Statements…> > . > > Please see our proposed timeline: > > Call for topics and drafting team: 15 - 22 May 2020 > > Drafting of Statement: 23 May - 6 June 2020 > > Send Statement to Staff for translation: 7 June 2020 > > Please send your suggested topics by Friday, 22 May 2020, after which the > drafting team will be constituted to prepare a draft statement that will be > shared with the rest of the members. If you would like to join the drafting > team, kindly notify us offlist. > > Looking forward to your contributions. > > Kind regards, > > Sarah Kiden > > AFRALO Secretariat >

9 12

VOTE ANNOUNCEMENT: 2020 AFRALO ALAC Member (RALO) Position
by ICANN At-Large Staff May 22, 2020

May 22, 2020

Dear All, The AFRALO ALS electorate has been asked the following question: Who do you support to become the AFRALO ALAC Member (RALO) for the period of two years, beginning at the end of the ICANN69 Annual General Meeting? Please select one candidate from the list below (listed in alphabetical order of the first name), or abstain. · Alex Corenthin · Sarah Kiden · Abstain Additional information: https://community.icann.org/x/-y6JBw Please note the poll will close on Friday, 05 June 23:59 UTC. Kind Regards, ICANN Policy Staff in support of the At-Large Community

1 0

VOTE ANNOUNCEMENT: 2020 AFRALO Secretariat Position
by ICANN At-Large Staff May 22, 2020

May 22, 2020

Dear All, The AFRALO ALS electorate has been asked the following question: Who do you support to become the AFRALO Secretariat for the period of two years, beginning at the end of the ICANN69 Annual General Meeting? Please select one candidate from the list below (listed in alphabetical order of the first name), or abstain. · Abdeldjalil Bachar Bong · Liz Orembo · Abstain Additional information: https://community.icann.org/x/-y6JBw Please note the poll will close on Friday, 05 June 23:59 UTC. Kind Regards, ICANN Policy Staff in support of the At-Large Community

1 0

Fwd: [ALS-Mob-WP] Next week's meeting
by Peters Omoragbon May 22, 2020

May 22, 2020

Sorry for cross posting as I used the wrong email address Pastor Peters Omoragbon ---------- Forwarded message --------- From: Peters Omoragbon <petersomoragbon(a)gmail.com> Date: Fri, 22 May 2020, 21:37 Subject: Re: [ALS-Mob-WP] Next week's meeting To: Alan Greenberg <alan.greenberg(a)mcgill.ca> Cc: ALS-mob-wp <als-mob-wp(a)icann.org>, AfRALO internal list < afralo-internal(a)atlarge-lists.icann.org>, AFRALO ROP WG < afralo-rop(a)atlarge-lists.icann.org>, Peters Omoragbon < peters.omoragbon(a)gmail.com>, ICANN At-Large Staff <staff(a)atlarge.icann.org>, ATLAS III Participants <atlasiiiparticipants(a)icann.org>, HELEN A < helenaegbums(a)yahoo.com> Dear Colleagues, I hope you are well, good and keeping safe in this pandemic? Please, find attached and also copied and pasted into the body of the email our position as an ALS and member of the ALS mop WP on the current review of the ALSs Activities. *Please, be informed that I on May 18 2020, I put the WP on notice that we shall be sharing our position for all to see, which was not objected to. So, no one should feel we are acting outside the prescribed guidelines of WGs.* Our aim is to enlarge and increase the volume of the voices of the affected communities. This was one lesson we learnt in Montreal during our leadership training-*to increase the volume of the voice of our various constituencies in ICANN.* *Take your time to read through.* Thank you for your time. *THE POSITION OF NURSES ACROSS THE BORDERS TO THE ALAC ALS MOP WP REVIEW AS IT RELATES TO THE PROPOSED ALS ACCREDITATION PROCESS AS AN ALS TO ALAC AND MEMBER OF THE ALS MOP WP* *Introduction* Fellow members of the Empowered Community and the ICANN family. This document is our position as it concerns the above subject matter. I must remind the members of the ALS MOP WP that I am sharing this document to the MOP WP directly in their emails and the AFRALO mailing list because the issues and the proposals contained in the document for review concerns the largest and most powerful section of the ALAC community; as such, because of the far reaching proposals if not openly debated and discussed, a lot within the WP and the RALOs may be wrongly influenced to sign up to what may even hunt them in the future, when they realized they have been misled by a section of the community with an agenda. (See Section 1.2.(a)iv, ICANN Byelaws: *Employ open, transparent and bottom-up, multi-stakeholder policy development processes** that are led by the private sector (including business stakeholders, civil society, the technical community, academia, and end users), while duly taking into account the public policy advice of governments and public authorities. These processes shall (A) seek input from the public, for whose benefit * *ICANN** in all events shall act, (B) promote well-informed decisions based on expert advice, and (C) ensure that those entities most affected can assist in the policy development process;*). Secondly, not very few of the ICANN family have taken time to familiarise themselves with the ICANN Byelaws which should be the ‘bible’ of our operation within ICANN. As a result I shall rely copiously on relevant sections of the Byelaws to support our position in this document. There are TWO documents attached to this email-First, the draft ALS ACCREDITATION PROCESS PROPOSAL that was shared on Google and this very document elaborating on our comments in the former document. Permit me if you will, to ask the following questions: (*they may have been answered, we do not think we are satisfied)* 1. What informed this very review process in the first place? 2. What was working well with the process in review? 3. What is/was not working well with the process in review? 4. If some areas within the process in review did not work well, does it warrant this elaborate and expansive review that has taken the shape of an *Assizes*? 5. Why would the ALSs not be availed the opportunity to review the draft of this WP before going to ALAC for approval? 6. If ICANN is to *Employ open, transparent and bottom-up, multi-stakeholder policy development processes…** and (C) ensure that those entities most affected can assist in the policy development process;*)- See Section 1.2.(a)iv, ICANN Byelaws, why then would this review process be made a top-bottom instead of the other way round? Or better still why would the ALSs not have a say in its review before ALAC consideration of our job? These were and are still our concerns because the fervour and enthusiasm being manifested by the WP leadership on this review, even to proposing a consideration OUTSIDE of the existing policies and practice of ICANN like *allowing an application from an ALS that has no region to be admitted into ICANN* to me is worrisome. Note that, majority of the members of the WP do not belong to any ALS nor have some been members of an ALS in the past. They came into ICANN as individuals and rose to their positions. One can now see why some of the proposals being made do not have bearing on them, because they stand to lose nothing at the end whichever way the pendulum swings. *Nothing about us without us is apt in this setting.* For any meaningful achievement from this review to stand the test of time, it must include the inputs of those to be affected by the review or policy. *POINTS OF OBSERVATION IN THE PROPOSAL AS THEY RELATE TO THE ICANN BYELAWS* 1. The drafters of the ICANN Byelaws foresaw a situation like is playing out now in the WB when they laid the foundation of ICANN’s structure and activities on Section 1.2 (a) iii, iv, v under *Commitments and Core Values.* These provisions I would implore every member of the WP and other stakeholders reading this document to read and reflect on this as it relates to their decisions in reviewing the ALS activities. For ease of reference, I have copied these sections hereunder: *1.2 *(a) *Commitments: * *In performing its Mission, **ICANN** must operate in a manner consistent with these Bylaws for the benefit of the Internet community as a whole, carrying out its activities in conformity with relevant principles of international law and international conventions and applicable local law, through open and transparent processes that enable competition and open entry in Internet-related markets. Specifically, **ICANN** commits to do the following (each, a "Commitment," and collectively, the "Commitments"):* *(a) * iii, *Respect the creativity, innovation, and flow of information made possible by the Internet by limiting **ICANN**'s activities to matters that are within **ICANN**'s Mission and require or significantly benefit from global coordination;* iv, *Employ, open, transparent and bottom-up, multistakeholder policy development processes that are led by the private sector (including business stakeholders, civil society, the technical community, academia, and end users), while duly taking into account the public policy advice of governments and public authorities. These processes shall (A) seek input from the public, for whose benefit **ICANN** in all events shall act, (B) promote well-informed decisions based on expert advice, and (C) ensure that those entities most affected can assist in the policy development process;* v, *Make decisions by applying documented policies consistently, neutrally, objectively, and fairly, without singling out any particular party for discriminatory treatment (i.e., making an unjustified prejudicial distinction between or among different parties); * 1.2 (b) under *Core Values* *i, **To the extent feasible and appropriate, delegating coordination functions to or recognizing the policy role of, other responsible entities that reflect the interests of affected parties and the roles of bodies internal to **ICANN** and relevant external expert bodies;* *vi, **Introducing and promoting competition in the registration of domain names where practicable and beneficial to the public interest as identified through the bottom-up, multistakeholder policy development process;* *vii, **Striving to achieve a reasonable balance between the interests of different stakeholders, while also avoiding capture; and* *at the rate the WP is going and if the lines of proposed changes are allowed, it will negate the principle of achieving reasonable balance between interests of different stakeholders. What is staring us now is a CAPTURE MENTALITY.* Furthermore, section 1.2.(c) summarises the importance of both the commitments and core values, take specific notice of the underlined portion of this core value: *The Commitments and Core Values are intended to apply in the broadest possible range of circumstances. The Commitments reflect * *ICANN**'s fundamental compact with the global Internet community and are intended to apply consistently and comprehensively to **ICANN**'s activities. The specific way in which Core Values are applied, individually and collectively, to any given situation may depend on many factors that cannot be fully anticipated or enumerated. Situations may arise in which perfect fidelity to all Core Values simultaneously is not possible. Accordingly, in any situation where one Core Value must be balanced with another, potentially competing Core Value, the result of the balancing must serve a policy developed through the bottom-up multistakeholder process or otherwise best serve **ICANN**'s Mission*. *To what extent would the current review serve ICANN’s best interest different from what is currently operational? Where is the application of the ‘bottom-up’ process if ALSs would await ALAC decision before it can make inputs (if at all) into our current review?* Suffice to mention also, that Section 3.1 vehemently reinforced the need for transparency when it stated as follows: *ICANN and its constituent bodies shall operate to the maximum extent feasible in an open and transparent manner and consistent with procedures designed to ensure fairness, including implementing procedures to (a) provide advance notice to facilitate stakeholder engagement in policy development decision-making and cross-community deliberations, (b) maintain responsive consultation procedures that provide detailed explanations of the basis for decisions (including how comments have influenced the development of policy considerations), and (c) encourage fact-based policy development work. ICANN shall also implement procedures for the documentation and public disclosure of the rationale for decisions made by the Board and ICANN's constituent bodies (including the detailed explanations discussed above).* The above to us should form the fulcrum of any policy review. The WP as far as we are concerned by the body language of its current leaders are diametrically opposed to the above standards. For example, at the meeting of Monday May 18, 2020, the Chairman of the WP was very clear, when he stated that the *ALSs would not have the opportunity for inputs or sighting the draft of the WP before it is submitted to ALAC. *That is not bottom-up policy formulation, nor is it transparent. Let us be very clear that, most of the leaders in this WP were never members of any ALS, as stated earlier, and they have at various times benefitted from ICANN in ITS BEST OF TIMES, have remained in every leadership positions by gyrating from one committee to the other in the name of EXPERIENCE as was the response to me in Montreal during the General Assembly. *This to me is pure recycling and not experience.* This same behaviour is permeating every strata of the ICANN community in all the regions as anyone in a position of leadership after 4 years is not satisfied but would use that position to influence his/her choice for further roles. *If there must be review, it has to be on how to prevent the recycling of ICANN leaderships in its community as currently practiced. There must be tenure limits! There is no Empowered Community if we keep repeating the same thing to expect a different result. *Very soon, majority of these leaders would retire from active roles in ICANN because of the current reality as members are becoming restive. And when they leave, what legacy would they leave behind without *empowered successors instead of adopting successors based on blind loyalty?* *SPECIFICS IN THE PROPOSED DRAFT REVIEW* Flowing from the WP meeting on 18/5/2020, I raised concerns on the following proposed drafts, *Item 2*: *For Review*: the set of actions that is to be done under Due Diligence is too probing especially the item that stated:* …verifying sources of funding*… ICANN or any of its constituents cannot exercise such powers when viewed against its Byelaws in *S12.2(d)vii* as the ALSs are SELF-SUPPORTING entities. *Item 3(a):* We do not see the need for current RALO leadership to still constitute a ‘Body’ within a ‘Body’ known as “LARGER REGIONAL LEADERSHIP” made up of ex RALO leaders. *This like breeding a collection of ‘Mafia-like -group’ that pulls the strings behind the curtain like a puppet show in the RALO.* Since these ex leaders would remain as members of their various ALSs or individual members of the RALOs, they could still made their contributions like any other ordinary members. Their roles ended with their tenures. *It is practices like this that breeds the recycling of leaders and constrict offices for the other members in the community stifle the leadership growth of the ‘next-generation-Generation Gap.* *Item 7: *The role of ALAC in this regard is unnecessary. Once the At large staff has completed their DD and referred to the RALOs, and it is approved or accepted by the RALO, their recommendation should not be subjected to ALAC review for another 5 days! *The following observations were made directly inside the document and herein was/is our observations highlighted accordingly:* Decisions are made in accordance with the standard ALAC majority decision process as per ALAC RoP 12.2.1. It is very interesting that the only section of the ALAC RoP referenced by the proponents of these changes was 12.2.1. What about section 12.2 (d) (vii), (viii), ix (E)? Decisions to accredit, or refuse to accredit, an ALS shall be subject to review as provided by the ICANN Bylaws, Section 4.2 Reconsideration. Why would the proponents ONLY prefer that it is ONLY the decision of ALAC to accredit or refuse accreditation of an ALS that should be subjected to Section 4.2? That is a smokescreen, why not subject this entire review with its stringent conditions be subjected to Section 4.2? This, in fact, will be the consideration of most existing ALSs individually or collectively should ALAC go-ahead to adopt these measures being proposed as they are very draconian. The ALAC will notify the applicant of its accreditation decision, and, if applicable, provide information on requesting a review of the decision. In the case of a decision to not accredit, the ALAC, at the sole decision of the ALAC Chair, may include a rationale for the rejection. Communication of official decisions to entities within ICANN should be the duty of the ICANN Staff not ALAC. Except as provided below under ‘Suspension of an Application', the ALAC and the At-Large staff shall work concertedly to ensure that the process of reaching a decision to accredit, or not to accredit, an At-Large Structure shall normally take no longer than ninety (90) calendar days from the date at which an application is received to the date at which the applicant is notified of the decision. Should it become apparent that this norm may not be achieved, the applicant shall be notified of the situation. ALAC should not overbear on the ICANN staff in performing their paid administrative duties. It will defeat the purpose of objectivity by the ICANN staff in performing DD because of undue influence by ANY MEMBER of ALAC with a vested interest. What is wrong with the present practice by the way *Note that under decisions to accredit or refuse to accredit…S4.2 of the ICANN Byelaw was the only section referenced. That is selective ‘redress,’ capitalizing on the ignorance of ICANN Byelaws by most the ALSs and other members of both the WP and the community. We would address this later on.* Suspension of an Application An application for ALS accreditation may be suspended where: 1. The suspension is requested by the Applicant; or 2. Additional information is requested by ICANN Staff during the Due Diligence process; or 3. The RALO Secretariat of the region the applicant is based in determines that further information is required from the applicant which is essential to the evaluation of the application; or 4. Members of the ALAC believe that additional information is essential to the evaluation of the application Once, due DD has been performed and the RALO are satisfied with the applicant’s meeting its standards as contained in its MOU and recommendation for approval made, ALAC should respect that recommendation. ALAC members are elected by the RALOs and such it is high-handed for ALAC to engage in scrutiny of a decison of the RALO especially when it was adopted by the consensus of the membership of the RAOL not just its leaders but members. 5. Wherever an application is suspended under part 1 of this section, that suspension shall be lifted upon the request of the applicant. When notifying the applicant of the additional information, it shall be obligatory to also notify the applicant that the application is suspended until the information is received. An application that is suspended at the request of the applicant, or waiting for information from the applicant for more than 90 days shall be considered to be withdrawn. QUESTION TO STAFF & WP: Are there cases where we may need to suspend an application other than to request new information? e.g. to get information other than from the applicant or due to the need for further evaluation? If so, how do we constrain the time required?I would suggest the time frame should be unify across any suspension reason De-accreditation An ALS may be de-accredited at the request of the ALS or by a decision of the ALAC. 1. If an ALS voluntarily decides to give up its ALS Status, the situation should be duly documented and the ALAC informed. ALAC Members may request additional investigation to ensure that the request is voluntary on behalf of the ALAC and may request that a formal vote of the ALAC be required. A simple majority in accordance with the ALAC RoP 12.2.1 is required. 2. A RALO may request de-accreditation of one of its ALSes. The rationale would normally include non-adherance to ALS minimum criteria, but other issues may be considered. The ALS must be given adequate opportunity to correct the problem(s), generally being given no less than 6 months to do so. 3. Any RALO action(s) in relation to ALS de-accreditation should be thoroughly dicumented. A super-majority ALAC vote of the ALAC is required for such de-accreditation. 4. ALAC Members may request de-accreditation of an ALS. The RALO leadership must be consulted and given an opportunity to explain why it believes that the ALS accreditation should remain. In all other respects, the process followed for case 2 shall be followed.Why would any member of ALAC be given the power to request de-accreditation of an ALS? Which section of the ICANN Bye laws is this proposal fulfilling? Remember what absolute power does? Someone who may not belong to the region of the ALS, not even a member of that RALO leadership, may because he does not like the way Pastor Peters is outspoken would wake up one day to put before the 15 wise men in ALAC the request to de-accredit his ALS. That is exactly what we are breeding. What criteria would the ALAC member fulfil before even contemplating such request? *CONCLUSION:* Our conclusion shall be made by drawing attention to SOME very salient sections of the ICANN Byelaws that *should guide this WP and every other member when contributing to this draft below from Section 12(d) ix F-G:* *(F) Decisions to certify or decertify an At-Large Structure shall be made as decided by the ALAC in its rules of procedure, save always that any changes made to the rules of procedure in respect of an At-Large Structure applications shall be subject to review by the RALOs and by the Board.* *(G) Decisions as to whether to accredit, not to accredit, or disaccredit an At-Large Structure shall be subject to review according to procedures established by the Board.* *(H) On an ongoing basis, the ALAC may also give advice as to whether a prospective At-Large Structure meets the applicable criteria and standards.* *The underlined sections in F above further supports our position that the ALSs have greater roles in any review that attempts to promote their activities. The powers of ALAC in section H is not absolute but a POSSIBILITY. These are subject to G above. Perhaps at this juncture, it is pertinent to ask if this review was/is in line with section 4.4 (a) or rather was this review the recommendation of this section?* *(a) **The Board shall cause a periodic review of the performance and operation of each **Supporting Organization**, each **Supporting Organization** Council, each **Advisory Committee** (other than the Governmental **Advisory Committee**), and the Nominating Committee (as defined in Section 8.1) by an entity or entities independent of the organization under review. The goal of the review, to be undertaken pursuant to such criteria and standards as the Board shall direct, shall be to determine (i) whether that organization, council or committee has a continuing purpose in the **ICANN** structure, (ii) if so, whether any change in structure or operations is desirable to improve its effectiveness and (iii) whether that organization, council or committee is accountable to its constituencies, stakeholder groups, organizations and other stakeholders. * *Item 1 *in the draft proposal identifies 3 *possibilities* and a 4TH for accrediting an *ALS that will not be affiliated to any region* below; When reviewing the form, determine which questions are mandatory. Also, if we will be accepting global (non-regional) ALSes, the application may need to be adjusted. NOTE: We spent a lot of time during the last meeting discussing ALSes which do not fit into our regional structure. The three possible options going forward were: a. Change the Bylaws to allow assigning such an ALS to a region; b. Interpret the Bylaws to allow assigning such an ALS to a region; c. Reject the application. A 4th option might also be possible: a. Have an ALS not associated with any region. *Why would anyone contemplate the option in red above? ALSs according the Byelaws operate in RALOs either as a group or as individuals. It is ludicrous to begin to formulate an academic exercise in futility. That option should be deleted without ANY DEBATE.* Take notice also of S4.6 b (i): *The Board shall cause a periodic review of **ICANN**'s execution of its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency so as to ensure that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community ("Accountability and Transparency Review").* *Caution:* It is hoped that the WP and other well-meaning members of the community would take time to peruse this document and reflect using the Lion’s club Four-Way Test of the things we think, say or do: · Is it the TRUTH · Is it FAIR to all concerned · Will it build GOOD WILL and BETTER FRIENDHIPS · Will it be BENEFICIAL to all concerned? If in the event our appeal above is not convincing enough to pause and review the basis again, then we may have no choice than exercise our rights under the ICANN Byelaws in Section 4.2(G)ii, 4.3 of annexe, d, and (H), (I) and (J). 4.3 (ii), (iv) You have the assurance of our esteemed regards, always. *For Nurses Across the Borders.* *Pastor Peters OMORAGBON* *President/CEO* *Pastor Peters Osawaru OMORAGBON* *-Financial Secretary, Central Association of Nigerians in the United Kingdom-CANUK* *-Executive President/CEO-Nurses Across the Borders-An NGO in Special Consultative Status with the Economic and Social Council of the United Nations-ECOSOC* *-Designated Contact Person-United Nations Framework Convention on Climate Change-UNFCCC* *-International Liaison Officer-Nigerian Nurses Charitable Association-NNCA-UK* *-Board Member-Conference of NGOS in Special Consultative Status with the United Nations-CONGO* *-Member Steering Committee Regional Committee for Africa-CONGO* *-General Secretary, Civil Society Network of NGOs on Climate Change* *-Fellow Internet Corporation for Assigned Names and Numbers-ICANN* *-Fellow Open Society Institute-Budapest* On Wed, 20 May 2020 at 03:25, Alan Greenberg <alan.greenberg(a)mcgill.ca> wrote: > I understand that it is a US holiday on Monday next week (just as it > was a Canadian holiday this Monday). > > At this point we are behind schedule and I have asked that a meeting > be scheduled. I understand that we may be a bit thin on staff and > NARALO members, but hopefully we can still make headway and as usual, > any decisions will be reviewed the following week. I will make sure > the revised document is ready well before the end of this week, so > everyone will have a chance to review it. > > Alan > > _______________________________________________ > ALS-Mob-WP mailing list > ALS-Mob-WP(a)icann.org > https://mm.icann.org/mailman/listinfo/als-mob-wp > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. >

1 0

Fwd: [Community-Discuss] Reminder: Extension of deadline for Nomination Period
by Caleb Olumuyiwa Ogundele May 22, 2020

May 22, 2020

Apologies for cross posting. However, this might be of interest to you. ---------- Forwarded message --------- From: AFRINIC Communication <comms(a)afrinic.net> Date: Wed, May 20, 2020, 11:17 AM Subject: [Community-Discuss] Reminder: Extension of deadline for Nomination Period To: <community-discuss(a)afrinic.net> Dear AFRINIC Community, NomCom2020 would like to extend the Nomination Period to Monday 25th May, 2020 at 23:59 GMT. We still do not have enough nominations for all available positions. We thus request members of the AFRINIC community to kindly use this period to nominate qualified candidates for the open seats. Please note that this is the final extension for nominations. We still welcome nominations for the following positions: 1. Co-Chair of the Policy Development Working Group (PDWG): Information on the process of filling the vacancies is available here https://www.afrinic.net/20200304-call-for-nominations-for-co-chair-of-the-p… __________________ 2. The Board of Director: Seat 3 (Indian Ocean), Seat 4 (Central Africa), Seat 8 (Non-Regional), and Seat 6 (Eastern Africa): Information on the process of filling the vacancies is available here https://www.afrinic.net/20200304-call-for-nominations-for-open-board-of-dir… _____________________ 3. NRO NC/ASO AC position: Information on the role responsibilities, criteria, and the process of filling the vacancies is available here https://www.afrinic.net/20200304-call-for-nominations-for-an-open-seat-on-t… ________________________ 4. The AFRINIC Governance Committee (GovCom): Read more on the criteria and qualifications for eligibility here https://www.afrinic.net/20200304-call-for-nominations-afrinic-governance-co… Once again, the deadline for submission of applications is Monday 25th May, 2020 at 23:59 GMT. NomCom 2020 ……………………………………………………………………………… Chère Communauté d'AFRINIC, NomCom2020 souhaite prolonger la période de nomination jusqu'au lundi 25 mai 2020 à 23:59 GMT. Nous n'avons pas encore assez de nominations pour tous les postes disponibles. Nous demandons donc aux membres de la communauté AFRINIC de bien vouloir profiter de cette période pour proposer des candidats qualifiés pour les sièges ouverts. Veuillez noter qu'il s'agit de la dernière prolongation pour les nominations. Nous acceptons toujours les candidatures pour les postes suivants : 1. Co-président du groupe de travail sur l'élaboration des politiques (PDWG) : Bien que nous pensions avoir suffisamment de candidatures pour ce siège particulier, afin de maintenir une situation équitable, ce poste n'a pas été fermé. Des informations sur le processus de pourvoi des postes vacants sont disponibles ici https://www.afrinic.net/20200304-call-for-nominations-for-co-chair-of-the-p… 2. Le conseil d'administration : Siège 3 (océan Indien), siège 4 (Afrique centrale), siège 8 (non régional) et siège 6 (Afrique de l'Est) : Des informations sur le processus de pourvoi des postes vacants sont disponibles ici https://www.afrinic.net/20200304-call-for-nominations-for-open-board-of-dir… _____________________ 3. Position du NRO NC/ASO AC : Des informations sur les responsabilités, les critères et le processus de pourvoi des postes vacants sont disponibles ici https://www.afrinic.net/20200304-call-for-nominations-for-an-open-seat-on-t… 4. Le comité de gouvernance AFRINIC (GovCom) : Pour en savoir plus sur les critères et les qualifications d'éligibilité, cliquez ici https://www.afrinic.net/20200304-call-for-nominations-afrinic-governance-co… Une fois de plus, la date limite de dépôt des candidatures est fixée au lundi 25 mai 2020 à 23h59 GMT. NomCom 2020 …………………………………………… عزيزي مجتمع أفرينك ، تود NomCom2020 تمديد فترة الترشيح حتى يوم الاثنين 25 مايو 2020 الساعة 23:59 بتوقيت جرينتش. ليس لدينا حتى الآن ما يكفي من الترشيحات لجميع المناصب المتاحة. وبالتالي نطلب من أعضاء مجتمع AFRINIC استخدام هذه الفترة لترشيح مرشحين مؤهلين للمقاعد المفتوحة. يرجى ملاحظة أن هذا هو التمديد النهائي للترشيحات. ما زلنا نرحب بالترشيحات للمناصب التالية: 1. الرئيس المشارك لمجموعة عمل تطوير السياسات (PDWG): في حين أننا نعتقد أن لدينا ما يكفي من الترشيحات لهذا المقعد المحدد ، من أجل الحفاظ على الوضع عادلًا ، لم يتم إغلاق هذا الموقف. معلومات عن عملية شغل الوظائف الشاغرة متاحة هنا https://www.afrinic.net/20200304-call-for-nominations-for-co-chair-of-the-p… __________________ 2 - مجلس الإدارة: المقعد 3 (المحيط الهندي) ، المقعد 4 (وسط أفريقيا) ، المقعد 8 (غير الإقليمي) ، المقعد 6 (شرق أفريقيا): معلومات عن عملية شغل الوظائف الشاغرة متاحة هنا https://www.afrinic.net/20200304-call-for-nominations-for-open-board-of-dir… _____________________ 3. موقف NRO NC / ASO AC: تتوفر معلومات حول مسؤوليات الدور والمعايير وعملية ملء الشواغر هنا https://www.afrinic.net/20200304-call-for-nominations-for-an-open-seat-on-t… ________________________ 4. لجنة الحوكمة الأفريقية (GovCom): اقرأ المزيد عن معايير ومؤهلات الأهلية هنا https://www.afrinic.net/20200304-call-for-nominations-afrinic-governance-co… مرة أخرى ، الموعد النهائي لتقديم الطلبات هو يوم الإثنين 25 مايو 2020 الساعة 23:59 بتوقيت جرينتش. NomCom 2020 ……………………………………. Cara Comunidade AFRINIC, O NomCom2020 gostaria de prolongar o período de nomeação até segunda-feira, 25 de Maio de 2020, às 23:59 GMT. Ainda não temos nomeações suficientes para todos os cargos disponíveis. Assim, solicitamos aos membros da comunidade AFRINIC que utilizem gentilmente este período para nomear candidatos qualificados para os lugares abertos. Note-se que esta é a última prorrogação para as nomeações. Continuamos a acolher favoravelmente as nomeações para os seguintes cargos: 1. Co-presidente do Grupo de Trabalho para o Desenvolvimento de Políticas (PDWG): Embora consideremos que temos nomeações suficientes para este lugar em particular, a fim de manter a situação justa, esta posição não foi encerrada. Informações sobre o processo de preenchimento das vagas estão disponíveis aqui https://www.afrinic.net/20200304-call-for-nominations-for-co-chair-of-the-p… __________________ 2. O Conselho de Administração: Lugar 3 (Oceano Índico), lugar 4 (África Central), lugar 8 (Não-Regional) e lugar 6 (África Oriental): Informações sobre o processo de preenchimento das vagas estão disponíveis aqui https://www.afrinic.net/20200304-call-for-nominations-for-open-board-of-dir… _____________________ 3. Posição NRO NC/ASO AC: Informações sobre as responsabilidades, os critérios e o processo de preenchimento das vagas estão disponíveis aqui https://www.afrinic.net/20200304-call-for-nominations-for-an-open-seat-on-t… ________________________ 4. A Comissão de Governação AFRINIC (GovCom): Leia mais sobre os critérios e qualificações de elegibilidade aqui https://www.afrinic.net/20200304-call-for-nominations-afrinic-governance-co… Mais uma vez, o prazo para a apresentação de candidaturas é segunda-feira, 25 de Maio de 2020, às 23:59 GMT. NomCom 2020 _______________________________________________ Community-Discuss mailing list Community-Discuss(a)afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss

1 0