<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<pre>Dear Al,</pre>
<pre>
Thanks a lot for those who support this policy.</pre>
<pre>
Taking into consideration the comments, I would like to withdraw "Mandatory requirements for registering assignments and sub-allocations"
(AFPUB-2014-GEN-003-DRAFT-01)</pre>
<pre>Thanks again for your support.</pre>
<pre>
Regards.</pre>
<pre>
Jean Robert Hountomey.</pre>
<br>
<br>
<div class="moz-cite-prefix">On 9/26/14, 9:43 AM, Seun Ojedeji
wrote:<br>
</div>
<blockquote
cite="mid:CAD_dc6heXfOgAjH8vGf7nmw58yJWUt-2Dgo0+qL=7czseKNyBw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Dear members,<br>
<br>
We have received a new policy Proposal - "Mandatory
requirements for registering assignments and sub-allocations"
(AFPUB-2014-GEN-003-DRAFT-01)<br>
<br>
Draft Policy name: Mandatory requirements for registering
assignments and 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: <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="http://goo.gl/vOJIrN">http://goo.gl/vOJIrN</a><br>
<br>
</div>
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 responsible management of unique IPv4 address space
in the AFRINIC region. The document was implemented in May 17,
2006. <br>
<br>
In a document called “Creating Customer Assignments” (2) last
Updated on Monday, 02 September 2013, AFRINIC has detailed the
process of registering LIR network infrastructure and customer
IP address assignments in the AFRINIC whois database. While the
two documents are still applicable, the AFRINIC community has
questioned at several occasions AFRINIC’s allocations. In
addition few, AFRINIC Resource Members (3) have not 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 Customer Assignments by introducing a section (section
9.7) into AFRINIC IPV4 Allocation Policy. In addition, the
document makes mandatory the registration of all allocations and
assignments in the AFRINIC database. Furthermore, the document
gives the authority to AFRINIC staff to conduct any process
after approbation by the community to reclaim resources from
unregistered assignments / allocations / sub-allocation since
they are considered invalid. <br>
3. Proposal<br>
<br>
3.1. Modification of section (8b) of the AFRINIC IPV4 Allocation
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 database. Any unregistered assignments / allocations /
sub-allocation will be considered invalid. <br>
<br>
The registration data (name, IP block/range, contacts, status,
etc..) must 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 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 address space, including the point of contact in case
of operation problems, security <br>
<br>
-To ensure that the Resource Member has completed or is close to
completing address space allocation such that the allocation of
additional space is justified <br>
<br>
-Assignment Registration also helps AFRINIC in analyzing
additional IPV4 block request made by a Resource Member in an
open transparent process <br>
<br>
-Assignments must include the following mandatory attributes
regarding 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 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 Resource Member for its own network or customer must be
registered and documented in AFRINIC Whois database no later
than seven (7) business days after the assignment. <br>
<br>
3.2.2 Residential Customers <br>
<br>
When the assignment is for residential customers, the address
blocks that are being used by equipment or customer service
areas, by service must be registered (dialup access server,
DSLAM/DSL access Server, WIFI Access Point, WIMAX Cell, Cloud
infrastructure etc..) The Resource Member must specify in the
AFRINIC whois database that the 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
information protection the Resource Member might be reluctant to
provide these information in the public database. The
information must be provided to AFRINIC for audit purpose under
confidential agreement. <br>
<br>
The Resources assigned must still be registered in AFRINIC Whois
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
information with the understanding that he is liable for any
issue related to the IP Block. <br>
<br>
4.References:<br>
<br>
(1) IPv4 Allocation Policy (Assignment Policies and Guidelines)
<br>
<a moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="http://www.AFRINIC.net/en/services/rs">http://www.AFRINIC.net/en/services/rs</a><br>
<br>
<b>Useful urls:</b><br>
Policy under discussion: <a moz-do-not-send="true"
href="http://www.afrinic.net/en/community/policy-development/policy-proposals"
target="_blank">http://www.afrinic.net/en/community/policy-development/policy-proposals</a><br>
Policy proposals: <a moz-do-not-send="true"
href="http://www.afrinic.net/en/community/policy-development/policy-proposals"
target="_blank">http://www.afrinic.net/en/community/policy-development/policy-proposals</a><br>
About the policy development process: <a moz-do-not-send="true"
href="http://www.afrinic.net/en/community/policy-development/pdwg"
target="_blank">http://www.afrinic.net/en/community/policy-development/pdwg</a><br>
<div class="gmail_extra">
<br>
</div>
<div class="gmail_extra">Regards<br>
</div>
---<br>
<div>Seun Ojedeji & Adam Nelson</div>
<div>PDWG Co-Chairs</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rpd mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>
<a class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a>
</pre>
</blockquote>
<br>
</body>
</html>