<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div style="font-family:Calibri,sans-serif; font-size:11pt">This seems to be okay, but we may need to reconsider the clause in 3.1 a ". All communication with AFRINIC must be in English." for the sake of our francophone colleagues. I think this clause should
be made less heavy to enhance their participation Thanks <br>
<br>
Sent from my Windows Phone<br>
</div>
</div>
<hr>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">From:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">rpd-request@afrinic.net</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Sent:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">26-Sep-14 5:18 PM</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">To:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">rpd@afrinic.net</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Subject:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">rpd Digest, Vol 96, Issue 37</span><br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Send rpd mailing list submissions to<br>
rpd@afrinic.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a><br>
or, via email, send a message with subject or body 'help' to<br>
rpd-request@afrinic.net<br>
<br>
You can reach the person managing the list at<br>
rpd-owner@afrinic.net<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. New proposal - "Mandatory requirements for registering<br>
assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01)<br>
(Seun Ojedeji)<br>
2. Re: New proposal - "Mandatory requirements for registering<br>
assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01) (McTim)<br>
3. Re: New proposal - "Mandatory requirements for registering<br>
assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01)<br>
(Dr Paulos Nyirenda)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 26 Sep 2014 15:43:53 +0100<br>
From: Seun Ojedeji <seun.ojedeji@gmail.com><br>
Subject: [rpd] New proposal - "Mandatory requirements for registering<br>
assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01)<br>
To: rpd <rpd@afrinic.net><br>
Message-ID:<br>
<CAD_dc6heXfOgAjH8vGf7nmw58yJWUt-2Dgo0+qL=7czseKNyBw@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear members,<br>
<br>
We have received a new policy Proposal - "Mandatory requirements for<br>
registering assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01)<br>
<br>
Draft Policy name: Mandatory requirements for registering assignments and<br>
sub-allocations<br>
Unique identifier: AFPUB-2014-GEN-003-DRAFT-01<br>
Status: New<br>
Submission Date: September 22, 2014<br>
Author: Jean Robert Hountomey<br>
URL:<br>
<a href="http://www.afrinic.net/en/community/policy-development/policy-proposals/1215-mandatory-requirements-for-registering-assignments-and-sub-allocations">http://www.afrinic.net/en/community/policy-development/policy-proposals/1215-mandatory-requirements-for-registering-assignments-and-sub-allocations</a><br>
Short url: <a href="http://goo.gl/vOJIrN">http://goo.gl/vOJIrN</a><br>
<br>
Text Below:<br>
<br>
1.Summary of the Problem Being Addressed by this Policy Proposal<br>
<br>
The AFRINIC IPv4 Allocation policy - AFPUB-2005-v4-001 (1) guides the<br>
responsible management of unique IPv4 address space in the AFRINIC region.<br>
The document was implemented in May 17, 2006.<br>
<br>
In a document called “Creating Customer Assignments” (2) last Updated on<br>
Monday, 02 September 2013, AFRINIC has detailed the process of registering<br>
LIR network infrastructure and customer IP address assignments in the<br>
AFRINIC whois database. While the two documents are still applicable, the<br>
AFRINIC community has questioned at several occasions AFRINIC’s<br>
allocations. In addition few, AFRINIC Resource Members (3) have not<br>
registered their assignments in the AFRINIC database.<br>
<br>
2.Summary of How this Proposal Addresses the Problem<br>
<br>
This document merges the AFRINIC IPv4 Allocation policy and Creating<br>
Customer Assignments by introducing a section (section 9.7) into AFRINIC<br>
IPV4 Allocation Policy. In addition, the document makes mandatory the<br>
registration of all allocations and assignments in the AFRINIC database.<br>
Furthermore, the document gives the authority to AFRINIC staff to conduct<br>
any process after approbation by the community to reclaim resources from<br>
unregistered assignments / allocations / sub-allocation since they are<br>
considered invalid.<br>
3. Proposal<br>
<br>
3.1. Modification of section (8b) of the AFRINIC IPV4 Allocation policy by<br>
replacing “will be” by “must be".<br>
<br>
a. All communication with AFRINIC must be in English.<br>
b. All allocations and assignments must be registered in an AFRINIC<br>
database. Any unregistered assignments / allocations / sub-allocation will<br>
be considered invalid.<br>
<br>
The registration data (name, IP block/range, contacts, status, etc..) must<br>
be correct at all times. This is necessary to support network operations.<br>
<br>
3.2 The proposal adds section (9.7) – “Mandatory Requirement for<br>
registering assignments” to AFRINIC IPV4 Allocation Policy.<br>
<br>
Assignment registration is important for several reasons:<br>
<br>
-To inform the Internet community which organization is using the IPv4<br>
address space, including the point of contact in case of operation<br>
problems, security<br>
<br>
-To ensure that the Resource Member has completed or is close to completing<br>
address space allocation such that the allocation of additional space is<br>
justified<br>
<br>
-Assignment Registration also helps AFRINIC in analyzing additional IPV4<br>
block request made by a Resource Member in an open transparent process<br>
<br>
-Assignments must include the following mandatory attributes regarding the<br>
assignee: inetnum, net name, descr, country, admin-c, tech-c, org<br>
<br>
and any other mandatory information required as defined by an AFRINIC<br>
policy.<br>
<br>
3.2.1 Size of block and timeframe<br>
<br>
All IP block assignments equal or larger than a /29 made by an AFRINIC<br>
Resource Member for its own network or customer must be registered and<br>
documented in AFRINIC Whois database no later than seven (7) business days<br>
after the assignment.<br>
<br>
3.2.2 Residential Customers<br>
<br>
When the assignment is for residential customers, the address blocks that<br>
are being used by equipment or customer service areas, by service must be<br>
registered (dialup access server, DSLAM/DSL access Server, WIFI Access<br>
Point, WIMAX Cell, Cloud infrastructure etc..) The Resource Member must<br>
specify in the AFRINIC whois database that the block is used for<br>
Residential Customers (netname, desc)<br>
<br>
3.3.3 Confidentiality.<br>
<br>
It is understandable that for business requirement and customer information<br>
protection the Resource Member might be reluctant to provide these<br>
information in the public database. The information must be provided to<br>
AFRINIC for audit purpose under confidential agreement.<br>
<br>
The Resources assigned must still be registered in AFRINIC Whois database<br>
with the following exception:<br>
<br>
-netname and descr must describe the usage of the block<br>
-all other information can be the same as the Ressource Member's<br>
information with the understanding that he is liable for any issue related<br>
to the IP Block.<br>
<br>
4.References:<br>
<br>
(1) IPv4 Allocation Policy (Assignment Policies and Guidelines)<br>
<a href="http://AFRINIC.net/en/library/policies/126-policy-ipv4-address-allocation-policies">http://AFRINIC.net/en/library/policies/126-policy-ipv4-address-allocation-policies</a><br>
<br>
(2) Creating Customer Assignments<br>
<a href="http://www.AFRINIC.net/en/library/membership-documents/214-creating-customer-assignments">http://www.AFRINIC.net/en/library/membership-documents/214-creating-customer-assignments</a><br>
<br>
(3) Definition of AFRINIC Resource Member<br>
<a href="http://www.AFRINIC.net/en/services/rs">http://www.AFRINIC.net/en/services/rs</a><br>
<br>
*Useful urls:*<br>
Policy under discussion:<br>
<a href="http://www.afrinic.net/en/community/policy-development/policy-proposals">http://www.afrinic.net/en/community/policy-development/policy-proposals</a><br>
Policy proposals:<br>
<a href="http://www.afrinic.net/en/community/policy-development/policy-proposals">http://www.afrinic.net/en/community/policy-development/policy-proposals</a><br>
About the policy development process:<br>
<a href="http://www.afrinic.net/en/community/policy-development/pdwg">http://www.afrinic.net/en/community/policy-development/pdwg</a><br>
<br>
Regards<br>
---<br>
Seun Ojedeji & Adam Nelson<br>
PDWG Co-Chairs<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20140926/6c7760b6/attachment-0001.htm">
https://lists.afrinic.net/pipermail/rpd/attachments/20140926/6c7760b6/attachment-0001.htm</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 26 Sep 2014 09:58:31 -0500<br>
From: McTim <dogwallah@gmail.com><br>
Subject: Re: [rpd] New proposal - "Mandatory requirements for<br>
registering assignments and sub-allocations"<br>
(AFPUB-2014-GEN-003-DRAFT-01)<br>
To: Seun Ojedeji <seun.ojedeji@gmail.com><br>
Cc: rpd <rpd@afrinic.net><br>
Message-ID:<br>
<CACAaNxgfs83f+QSOH4NBOrmUCcfvr=Rw=mSXtHDup9gkvBj6Vw@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
I support this proposal.<br>
<br>
On Fri, Sep 26, 2014 at 9:43 AM, Seun Ojedeji <seun.ojedeji@gmail.com> wrote:<br>
> Dear members,<br>
><br>
> We have received a new policy Proposal - "Mandatory requirements for<br>
> registering assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01)<br>
><br>
> Draft Policy name: Mandatory requirements for registering assignments and<br>
> sub-allocations<br>
> Unique identifier: AFPUB-2014-GEN-003-DRAFT-01<br>
> Status: New<br>
> Submission Date: September 22, 2014<br>
> Author: Jean Robert Hountomey<br>
> URL:<br>
> <a href="http://www.afrinic.net/en/community/policy-development/policy-proposals/1215-mandatory-requirements-for-registering-assignments-and-sub-allocations">
http://www.afrinic.net/en/community/policy-development/policy-proposals/1215-mandatory-requirements-for-registering-assignments-and-sub-allocations</a><br>
> Short url: <a href="http://goo.gl/vOJIrN">http://goo.gl/vOJIrN</a><br>
><br>
> Text Below:<br>
><br>
> 1.Summary of the Problem Being Addressed by this Policy Proposal<br>
><br>
> The AFRINIC IPv4 Allocation policy - AFPUB-2005-v4-001 (1) guides the<br>
> responsible management of unique IPv4 address space in the AFRINIC region.<br>
> The document was implemented in May 17, 2006.<br>
><br>
> In a document called “Creating Customer Assignments” (2) last Updated on<br>
> Monday, 02 September 2013, AFRINIC has detailed the process of registering<br>
> LIR network infrastructure and customer IP address assignments in the<br>
> AFRINIC whois database. While the two documents are still applicable, the<br>
> AFRINIC community has questioned at several occasions AFRINIC’s allocations.<br>
> In addition few, AFRINIC Resource Members (3) have not registered their<br>
> assignments in the AFRINIC database.<br>
><br>
> 2.Summary of How this Proposal Addresses the Problem<br>
><br>
> This document merges the AFRINIC IPv4 Allocation policy and Creating<br>
> Customer Assignments by introducing a section (section 9.7) into AFRINIC<br>
> IPV4 Allocation Policy. In addition, the document makes mandatory the<br>
> registration of all allocations and assignments in the AFRINIC database.<br>
> Furthermore, the document gives the authority to AFRINIC staff to conduct<br>
> any process after approbation by the community to reclaim resources from<br>
> unregistered assignments / allocations / sub-allocation since they are<br>
> considered invalid.<br>
> 3. Proposal<br>
><br>
> 3.1. Modification of section (8b) of the AFRINIC IPV4 Allocation policy by<br>
> replacing “will be” by “must be".<br>
><br>
> a. All communication with AFRINIC must be in English.<br>
> b. All allocations and assignments must be registered in an AFRINIC<br>
> database. Any unregistered assignments / allocations / sub-allocation will<br>
> be considered invalid.<br>
><br>
> The registration data (name, IP block/range, contacts, status, etc..) must<br>
> be correct at all times. This is necessary to support network operations.<br>
><br>
> 3.2 The proposal adds section (9.7) – “Mandatory Requirement for registering<br>
> assignments” to AFRINIC IPV4 Allocation Policy.<br>
><br>
> Assignment registration is important for several reasons:<br>
><br>
> -To inform the Internet community which organization is using the IPv4<br>
> address space, including the point of contact in case of operation problems,<br>
> security<br>
><br>
> -To ensure that the Resource Member has completed or is close to completing<br>
> address space allocation such that the allocation of additional space is<br>
> justified<br>
><br>
> -Assignment Registration also helps AFRINIC in analyzing additional IPV4<br>
> block request made by a Resource Member in an open transparent process<br>
><br>
> -Assignments must include the following mandatory attributes regarding the<br>
> assignee: inetnum, net name, descr, country, admin-c, tech-c, org<br>
><br>
> and any other mandatory information required as defined by an AFRINIC<br>
> policy.<br>
><br>
> 3.2.1 Size of block and timeframe<br>
><br>
> All IP block assignments equal or larger than a /29 made by an AFRINIC<br>
> Resource Member for its own network or customer must be registered and<br>
> documented in AFRINIC Whois database no later than seven (7) business days<br>
> after the assignment.<br>
><br>
> 3.2.2 Residential Customers<br>
><br>
> When the assignment is for residential customers, the address blocks that<br>
> are being used by equipment or customer service areas, by service must be<br>
> registered (dialup access server, DSLAM/DSL access Server, WIFI Access<br>
> Point, WIMAX Cell, Cloud infrastructure etc..) The Resource Member must<br>
> specify in the AFRINIC whois database that the block is used for Residential<br>
> Customers (netname, desc)<br>
><br>
> 3.3.3 Confidentiality.<br>
><br>
> It is understandable that for business requirement and customer information<br>
> protection the Resource Member might be reluctant to provide these<br>
> information in the public database. The information must be provided to<br>
> AFRINIC for audit purpose under confidential agreement.<br>
><br>
> The Resources assigned must still be registered in AFRINIC Whois database<br>
> with the following exception:<br>
><br>
> -netname and descr must describe the usage of the block<br>
> -all other information can be the same as the Ressource Member's information<br>
> with the understanding that he is liable for any issue related to the IP<br>
> Block.<br>
><br>
> 4.References:<br>
><br>
> (1) IPv4 Allocation Policy (Assignment Policies and Guidelines)<br>
> <a href="http://AFRINIC.net/en/library/policies/126-policy-ipv4-address-allocation-policies">
http://AFRINIC.net/en/library/policies/126-policy-ipv4-address-allocation-policies</a><br>
><br>
> (2) Creating Customer Assignments<br>
> <a href="http://www.AFRINIC.net/en/library/membership-documents/214-creating-customer-assignments">
http://www.AFRINIC.net/en/library/membership-documents/214-creating-customer-assignments</a><br>
><br>
> (3) Definition of AFRINIC Resource Member<br>
> <a href="http://www.AFRINIC.net/en/services/rs">http://www.AFRINIC.net/en/services/rs</a><br>
><br>
> Useful urls:<br>
> Policy under discussion:<br>
> <a href="http://www.afrinic.net/en/community/policy-development/policy-proposals">
http://www.afrinic.net/en/community/policy-development/policy-proposals</a><br>
> Policy proposals:<br>
> <a href="http://www.afrinic.net/en/community/policy-development/policy-proposals">
http://www.afrinic.net/en/community/policy-development/policy-proposals</a><br>
> About the policy development process:<br>
> <a href="http://www.afrinic.net/en/community/policy-development/pdwg">http://www.afrinic.net/en/community/policy-development/pdwg</a><br>
><br>
> Regards<br>
> ---<br>
> Seun Ojedeji & Adam Nelson<br>
> PDWG Co-Chairs<br>
><br>
> _______________________________________________<br>
> rpd mailing list<br>
> rpd@afrinic.net<br>
> <a href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a><br>
><br>
<br>
<br>
<br>
-- <br>
Cheers,<br>
<br>
McTim<br>
"A name indicates what we seek. An address indicates where it is. A<br>
route indicates how we get there." Jon Postel<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 26 Sep 2014 18:14:56 +0200<br>
From: "Dr Paulos Nyirenda" <paulos@sdnp.org.mw><br>
Subject: Re: [rpd] New proposal - "Mandatory requirements for<br>
registering assignments and sub-allocations"<br>
(AFPUB-2014-GEN-003-DRAFT-01)<br>
To: Seun Ojedeji <seun.ojedeji@gmail.com>, rpd <rpd@afrinic.net><br>
Message-ID: <54259100.16256.1F32FCF@paulos.sdnp.org.mw><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
<br>
Seun,<br>
<br>
While I am still considering the proposal, I would like to comment on the process for this
<br>
policy proposal.<br>
<br>
Normally, a proposal that ammends a policy like this has produced a full version of the
<br>
ammended policy and not just a list of the ammendments as has been done here. The full
<br>
version of the policy then replaces the previous version or as the saying goes "obsoletes" the
<br>
previous version in a tracked histrory. This allows the ammendments to be considered in the
<br>
context of the whole policy and not just bits of it like this.<br>
<br>
So, in this case I think the way forward would be to ask the author to insert the
<br>
ammendments and to produce the full ammended version of AFPUB-2005-v4-001 which is
<br>
what should be presented to RPD for discussion.<br>
<br>
The list of ammendments can be put in the problem section of the new proposal or however
<br>
the author wants it done with the guidance of the co-chairs BUT it is the full policy that should
<br>
be discussed on RPD and not just the ammendments like this.<br>
<br>
I am open to correction on the process but at least that is the way I recall its use.<br>
<br>
Regards,<br>
<br>
Paulos<br>
======================<br>
Dr Paulos B Nyirenda<br>
NIC.MW & .mw ccTLD<br>
<a href="http://www.registrar.mw">http://www.registrar.mw</a><br>
<br>
<br>
On 26 Sep 2014 at 15:43, Seun Ojedeji <seun.ojedeji@gmail.com> wrote:<br>
<br>
> <br>
> Dear members,<br>
> <br>
> We have received a new policy Proposal - "Mandatory requirements for<br>
> registering assignments and sub-allocations"<br>
> (AFPUB-2014-GEN-003-DRAFT-01)<br>
> <br>
> Draft Policy name: Mandatory requirements for registering assignments<br>
> and sub-allocations Unique identifier: AFPUB-2014-GEN-003-DRAFT-01<br>
> Status: New Submission Date: September 22, 2014 Author: Jean Robert<br>
> Hountomey URL:<br>
> <a href="http://www.afrinic.net/en/community/policy-development/policy-proposal">
http://www.afrinic.net/en/community/policy-development/policy-proposal</a><br>
> s/1215-mandatory-require<br>
> ments-for-registering-assignments-and-sub-allocations Short url:<br>
> <a href="http://goo.gl/vOJIrN">http://goo.gl/vOJIrN</a><br>
> <br>
> Text Below:<br>
> <br>
> 1.Summary of the Problem Being Addressed by this Policy Proposal<br>
> <br>
> The AFRINIC IPv4 Allocation policy - AFPUB-2005-v4-001 (1) guides the<br>
> responsible management of unique IPv4 address space in the AFRINIC<br>
> region. The document was implemented in May 17, 2006.<br>
> <br>
> In a document called "Creating Customer Assignments" (2) last Updated<br>
> on Monday, 02 September 2013, AFRINIC has detailed the process of<br>
> registering LIR network infrastructure and customer IP address<br>
> assignments in the AFRINIC whois database. While the two documents are<br>
> still applicable, the AFRINIC community has questioned at several<br>
> occasions AFRINIC's allocations. In addition few, AFRINIC Resource<br>
> Members (3) have not registered their assignments in the AFRINIC<br>
> database.<br>
> <br>
> 2.Summary of How this Proposal Addresses the Problem<br>
> <br>
> This document merges the AFRINIC IPv4 Allocation policy and Creating<br>
> Customer Assignments by introducing a section (section 9.7) into<br>
> AFRINIC IPV4 Allocation Policy. In addition, the document makes<br>
> mandatory the registration of all allocations and assignments in the<br>
> AFRINIC database. Furthermore, the document gives the authority to<br>
> AFRINIC staff to conduct any process after approbation by the<br>
> community to reclaim resources from unregistered assignments /<br>
> allocations / sub-allocation since they are considered invalid. 3.<br>
> Proposal<br>
> <br>
> 3.1. Modification of section (8b) of the AFRINIC IPV4 Allocation<br>
> policy by replacing "will be" by "must be".<br>
> <br>
> a. All communication with AFRINIC must be in English.<br>
> b. All allocations and assignments must be registered in an AFRINIC<br>
> database. Any unregistered assignments / allocations / sub-allocation<br>
> will be considered invalid.<br>
> <br>
> The registration data (name, IP block/range, contacts, status, etc..)<br>
> must be correct at all times. This is necessary to support network<br>
> operations.<br>
> <br>
> 3.2 The proposal adds section (9.7) - "Mandatory Requirement for<br>
> registering assignments" to AFRINIC IPV4 Allocation Policy.<br>
> <br>
> Assignment registration is important for several reasons:<br>
> <br>
> -To inform the Internet community which organization is using the IPv4<br>
> address space, including the point of contact in case of operation<br>
> problems, security<br>
> <br>
> -To ensure that the Resource Member has completed or is close to<br>
> completing address space allocation such that the allocation of<br>
> additional space is justified<br>
> <br>
> -Assignment Registration also helps AFRINIC in analyzing additional<br>
> IPV4 block request made by a Resource Member in an open transparent<br>
> process<br>
> <br>
> -Assignments must include the following mandatory attributes regarding<br>
> the assignee: inetnum, net name, descr, country, admin-c, tech-c, org<br>
> <br>
> and any other mandatory information required as defined by an AFRINIC<br>
> policy.<br>
> <br>
> 3.2.1 Size of block and timeframe<br>
> <br>
> All IP block assignments equal or larger than a /29 made by an AFRINIC<br>
> Resource Member for its own network or customer must be registered and<br>
> documented in AFRINIC Whois database no later than seven (7) business<br>
> days after the assignment.<br>
> <br>
> 3.2.2 Residential Customers<br>
> <br>
> When the assignment is for residential customers, the address blocks<br>
> that are being used by equipment or customer service areas, by service<br>
> must be registered (dialup access server, DSLAM/DSL access Server,<br>
> WIFI Access Point, WIMAX Cell, Cloud infrastructure etc..) The<br>
> Resource Member must specify in the AFRINIC whois database that the<br>
> block is used for Residential Customers (netname, desc)<br>
> <br>
> 3.3.3 Confidentiality.<br>
> <br>
> It is understandable that for business requirement and customer<br>
> information protection the Resource Member might be reluctant to<br>
> provide these information in the public database. The information must<br>
> be provided to AFRINIC for audit purpose under confidential agreement.<br>
> <br>
> The Resources assigned must still be registered in AFRINIC Whois<br>
> database with the following exception:<br>
> <br>
> -netname and descr must describe the usage of the block<br>
> -all other information can be the same as the Ressource Member's<br>
> information with the understanding that he is liable for any issue<br>
> related to the IP Block.<br>
> <br>
> 4.References:<br>
> <br>
> (1) IPv4 Allocation Policy (Assignment Policies and Guidelines)<br>
> <a href="http://AFRINIC.net/en/library/policies/126-policy-ipv4-address-allocat">
http://AFRINIC.net/en/library/policies/126-policy-ipv4-address-allocat</a><br>
> ion-policies<br>
> <br>
> (2) Creating Customer Assignments<br>
> <a href="http://www.AFRINIC.net/en/library/membership-documents/214-creating-cu">
http://www.AFRINIC.net/en/library/membership-documents/214-creating-cu</a><br>
> stomer-assignments<br>
> <br>
> (3) Definition of AFRINIC Resource Member<br>
> <a href="http://www.AFRINIC.net/en/services/rs">http://www.AFRINIC.net/en/services/rs</a><br>
> <br>
> Useful urls:<br>
> Policy under discussion:<br>
> <a href="http://www.afrinic.net/en/community/policy-development/policy-proposal">
http://www.afrinic.net/en/community/policy-development/policy-proposal</a><br>
> s Policy proposals:<br>
> <a href="http://www.afrinic.net/en/community/policy-development/policy-proposal">
http://www.afrinic.net/en/community/policy-development/policy-proposal</a><br>
> s About the policy development process:<br>
> <a href="http://www.afrinic.net/en/community/policy-development/pdwg">http://www.afrinic.net/en/community/policy-development/pdwg</a><br>
> <br>
> Regards<br>
> ---<br>
> Seun Ojedeji & Adam Nelson<br>
> PDWG Co-Chairs<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20140926/61c73724/attachment.htm">
https://lists.afrinic.net/pipermail/rpd/attachments/20140926/61c73724/attachment.htm</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
rpd mailing list<br>
rpd@afrinic.net<br>
<a href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a><br>
<br>
<br>
End of rpd Digest, Vol 96, Issue 37<br>
***********************************<br>
</div>
</span></font>
</body>
</html>