Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] Fwd: update on policy Afrinic service Guide Lines policy proposal

Andrew Alston Andrew.Alston at liquidtelecom.com
Fri Nov 21 14:16:01 UTC 2014


Hi Karmann,

(Again speaking from a personal perspective and not as a member of the board)

I’d argue that if you wanted to bar the board from any particular thing, which you would be free to do, such restrictions on the actions of the board are not in the ambit of the PdP.  The mandate of the board (or the revocation of the mandate of the board) needs to be done through a change in the bylaws.

The procedures to change the bylaws are clearly spelled out in the bylaws themselves as well.  Write a resolution, table it for discussion/voting at an AGMM within the specified time frames, and then get it passed by a 75 percent majority of voting members.

Keep in mind, board authority and the authority of various others (including the CoE for example), as well as their mandates and their constituency is specifically laid out in the bylaws, and it is only through a change in the bylaws that this can be done.  I do not think the PdP (or even the board themselves for that matter) can change those bylaws outside of that process without contravening the current bylaws and the various legal frameworks in place.

I refer you to section 7.6.vi of the bylaws which reads:
(vi) consider and approve by Special Resolution, if appropriate, proposals for the revocation, amendment or replacement of this Constitution;

Where Special resolution is defined as

A resolution approved by a majority of 75 per cent of the votes of those members entitled to vote and voting on the question.

With regards to who can vote in terms of such a modification, see section 12.11.

Section 12.14 spells out how to go about tabling a special resolution.

Thanks

Andrew Alston
Group Head of IP Strategy
[cid:6E87CB5D-EC2C-401E-BE28-041A1C2E9956]
Sameer business Park, Block A, Mombasa Road. Nairobi, Kenya
T: +254 205000000 -  M: +254 733 2222 04 - E: andrew.alston at liquidtelecom.com

From: Karmann Olumomo <karmann.olumomo at gmail.com<mailto:karmann.olumomo at gmail.com>>
Date: Friday, November 21, 2014 at 10:43 AM
To: Andrew Alston <andrew.alston at liquidtelecom.com<mailto:andrew.alston at liquidtelecom.com>>
Cc: "rpd at afrinic.net<mailto:rpd at afrinic.net>" <rpd at afrinic.net<mailto:rpd at afrinic.net>>
Subject: Re: [rpd] Fwd: update on policy Afrinic service Guide Lines policy proposal

Hi Andrew:

I am saying "resource allocation process", not policy development process.

resource allocation process is an internal process of Afrinic hostmaster team.

On Fri, Nov 21, 2014 at 2:23 PM, Andrew Alston <Andrew.Alston at liquidtelecom.com<mailto:Andrew.Alston at liquidtelecom.com>> wrote:
Hi Karmann,

(Speaking personally and not with my board hat on).

I strongly object to the clause that says board members can have no involvement in the policy development process.

Keep in mind, every board member is elected from within the community.  That means that many board members also have their own job functions which relate to IP addressing within their respective organisations.  I agree that a board member who is also involved in the PdP should NOT necessarily be doing it with their board hat on, but you cannot exclude the individuals themselves from the process.  To do so would be to ensure that any person who is active in policy can never run for board, else they risk being alienated from the policy process.  This would damage not only the PdP but also the potential to get quality board members who have a good understanding of policy and the process by which it is formulated.

Hence, I will not support any policy that states that.

Andrew Alston
Group Head of IP Strategy
[cid:5EA326DF-FC4F-40D6-A62C-546B18EDA6A5]
Sameer business Park, Block A, Mombasa Road. Nairobi, Kenya
T: +254 205000000<tel:%2B254%20205000000> -  M: +254 733 2222 04 - E: andrew.alston at liquidtelecom.com<mailto:andrew.alston at liquidtelecom.com>

From: Karmann Olumomo <karmann.olumomo at gmail.com<mailto:karmann.olumomo at gmail.com>>
Date: Friday, November 21, 2014 at 8:10 AM
To: "rpd at afrinic.net<mailto:rpd at afrinic.net>" <rpd at afrinic.net<mailto:rpd at afrinic.net>>
Subject: [rpd] Fwd: update on policy Afrinic service Guide Lines policy proposal




HI

After taking the community feed back, I'd like to update my proposal to the following:

1) Summary of the Problem Being Addressed by this Policy Proposal
Some member are experiencing extreme long wait for their additional allocation request to get passed, some members are experiencing none technical information requested from Afrinic(customer data, marketing channel etc), in order to improve overall service quality of Afrinic, here is the policy.

2) Summary of How this Proposal Addresses the Problem
To improve overall service quality and transparency of Afrinic’s number resource services by documenting roles and responsibilities of AFRINIC.
3) Proposal
1.Afrinic should make decision on subsequent allocation requests based on Afrinic   policy, and conclude a request no longer than the 20% of the total period AFRNIC approves the resources for. (E.g. If Afrinic is issuing resources to its member to meet its 12 months needs, the longest waiting time for Afrinic allocation process should not be longer than 20%*12month, to cope with 80% utilization requirement for additional allocation). If Afrinic was not able to make decision on a certain request within this period, for each additional month beyond this period, the requesting member should receive percentage of the requested period of the total request until such decision has been made, in order to protect member from smooth running of its business.

2.Afrinic should publish standardized base information request for each typical type of resource allocation.


3.Afrinic should not store, request any marketing or business related none-technical information from its member, for example, customer data, marketing channel, and marketing budget.


4.Afrinic allocations should be solely made based on current policy, no other factor other than policy should infer with afrinic’s decision on processing allocation requests.


5.Afrinic board should never being involved in any form of resource allocation process.


6.For the interest of overall policy development process, other RIR staff as well as it's governing body personnel(advisor or board member, for example) should not be involve in Afrinic policy development process.


7.Afrinic policy working group chair election should be conducted independent from Afrinic board nomination committee, candidates should be free of any requirement.


The main updated point is point 5:

5.Afrinic board should never being involved in any form of resource allocation process.

Thanks very much and please update the proposal accordingly.



________________________________
DISCLAIMER: This email contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient, you must not use, disclose, copy, print, or rely on this email. We cannot accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of this company or one of its agents.



________________________________
DISCLAIMER: This email contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient, you must not use, disclose, copy, print, or rely on this email. We cannot accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of this company or one of its agents.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20141121/a433f84a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1D7357BF-29F7-4C26-9D6A-6EFCA78201B1.png
Type: image/png
Size: 13157 bytes
Desc: 1D7357BF-29F7-4C26-9D6A-6EFCA78201B1.png
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20141121/a433f84a/attachment.png>


More information about the RPD mailing list