Search RPD Archives
[AfriNIC-rpd] Re: rpd Digest, Vol 35, Issue 2
Douglas Onyango
ondouglas at yahoo.com
Mon Mar 9 20:15:10 UTC 2009
The policy looks good as a whole.
2.1 talks about "address space that is returned to an RIR.....", from where?? LIR? End user? or both, we need to explicitly state
5.2 "is rescinded" | With respect to the first statement "upon ratification"................this tense is not right
Regards,
Douglas onyango +256(0712)981329
If you are not part of the solution, your are part of the Problem.
--- On Thu, 3/5/09, rpd-request at afrinic.net <rpd-request at afrinic.net> wrote:
From: rpd-request at afrinic.net <rpd-request at afrinic.net>
Subject: rpd Digest, Vol 35, Issue 2
To: rpd at afrinic.net
Date: Thursday, March 5, 2009, 6:24 PM
Send rpd mailing list submissions to
rpd at afrinic.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.afrinic.net/mailman/listinfo.cgi/rpd
or, via email, send a message with subject or body 'help' to
rpd-request at afrinic.net
You can reach the person managing the list at
rpd-owner at afrinic.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of rpd digest..."
Today's Topics:
1. Re: IP address management practices/guidelines for ISPs (SM)
2. Global Policy Proposal for the Allocation of IPv4 Blocks to
Regional Internet Registries (Vincent Ngundi)
----------------------------------------------------------------------
Message: 1
Date: Wed, 04 Mar 2009 23:17:08 -0800
From: SM <sm at resistor.net>
Subject: Re: [AfriNIC-rpd] IP address management practices/guidelines
for ISPs
To: AfriNIC Resource Policy Discussion List <rpd at afrinic.net>
Message-ID: <6.2.5.6.2.20090304223604.02fba118 at resistor.net>
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 11:08 04-03-2009, David Conrad wrote:
>The price depends on the market not the operating cost. For example,
>in the US, on one particularly large consumer Internet provider, the
>price for a static IP address works out to US$7/_month_.
Right. Some ISPs in the US charge USD 10.00 per month for a static
IPv4 address. The question of charging outrageous prices does not
arise if there is only one local incumbent. If the customer wants to
complain about competition or unfair practices, the national
regulator is the place to go.
At 11:47 04-03-2009, Jean Robert Hountomey wrote:
>I know some countries in this 21 century where a /30 cost more than
>200 USD/month while we are talking about critical infrastrucutre,
>enabling access etc..
See the "price depends on the market". Consider using provider
independent (RFC 1918) IPv4 address space. :-)
>And when people decide to go to AfriNIC their unfair answer is "we
>can't route your block".
There are other considerations to be taken into account. This
problem does not happen in the AfriNIC region only.
You "can add information about such an ISP/LIR to a forum for
complaints from the community, so other customers will be able to
make more informed decisions about which ISP to use."
These guidelines are "the best AfriNIC can do". Asking for more than
that would put AfriNIC in an awkward position.
Regards,
-sm
------------------------------
Message: 2
Date: Thu, 05 Mar 2009 18:21:50 +0300
From: Vincent Ngundi <vincent at kenic.or.ke>
Subject: [AfriNIC-rpd] Global Policy Proposal for the Allocation of
IPv4 Blocks to Regional Internet Registries
To: AfriNIC RPD ML <rpd at afrinic.net>
Message-ID: <C5D5C8BE.2EFD%vincent at kenic.or.ke>
Content-Type: text/plain; charset="us-ascii"
Dear Members,
The ASO AC accepted the above as a Global Policy Proposal (GPP) in its 5th
of March 2009 meeting. In accordance with both the GPP Policy Development
Process and the AfriNIC Policy Development Process, the proposal is being
posted to the AfriNIC Resource Policy Discuss (RPD) Mailing List. The
proposal will also be placed on the AfriNIC website as a policy proposal
under discussion.
In line with the AfriNIC PDP, the AfriNIC community is now invited to review
and discuss this policy.
The AfriNIC Policy Development Process can be found at:
http://www.afrinic.net/docs/policies/afpol-pdp200707.htm
AfriNIC Mailing Lists subscription information can be found at:
http://www.afrinic.net/mailinglist.htm
Regards,
Vincent Ngundi
Chair, AfriNIC PDP-MG
####### Global Policy Proposal for the Allocation of IPv4 Blocks to Regional
Internet Registries #######
________________________________________________________________________
prop-069-v002: Global policy proposal for the allocation of IPv4 blocks
to Regional Internet Registries
________________________________________________________________________
Authors: Adiel A. Akplogan, AfriNIC
Raul Echeberria, LACNIC
Maemura Akinori, APNIC
Geoff Huston, APNIC
Axel Pawlik, RIPE NCC
Ray Plzak, ARIN
Oscar A. Robles-Garay, LACNIC
Nigel Titley, RIPE NCC
Paul Wilson, APNIC
Note: This proposal was developed by a team consisting of
persons from each of the 5 RIRs
Version: 2
Date: 3 February 2009
1. Introduction
----------------
This document is a global policy proposal governing the allocation of
IPv4 address space from the IANA to the Regional Internet Registries
(RIRs).
This document does not stipulate performance requirements in the
provision of services by the IANA to an RIR in accordance with this
proposed policy. Such requirements should be specified by appropriate
agreements among the RIRs and ICANN.
2. Definitions
--------------
2.1 Recovered address space
Recovered address space is that address space that is returned to an
RIR as a result of any activity that seeks to reclaim unused address
space or is voluntarily returned to the RIR or is reclaimed by the
RIR as a result of legal action or abuse determination. Recovered
address space does not include that address space that is reclaimed
because of non-payment of contractual fees whose reclamation date is
less than 1 year at the time of the report.
2.2 IPv4 address holdings
IPv4 address holdings are all unallocated IPv4 address space held by
an RIR to include recovered address space not yet returned less that
address space that is committed in accordance with the RIR's
reservation policy and practices.
3. Summary of current problem
------------------------------
With the depletion of the IANA free pool of IPv4 address space, the
current policy regarding the allocation of IPv4 address space to the
RIRs will become moot. The RIRs may, according to their individual
policies and procedures, recover IPv4 address space. This policy
provides a mechanism for the RIRs to retro allocate the recovered IPv4
address space to the IANA and provides the IANA the policy by which it
can allocate it back to the RIRs on a needs basis. This policy creates a
new global pool of IPv4 address space that can be allocated where it is
needed on a global basis without a transfer of address space between the
RIRs.
4. Situation in other RIRs
----------------------------
This proposal is being submitted in all RIR regions, with a view to
becoming a global policy [1].
5. Details of the proposal
----------------------------
This policy is to be implemented in two phases:
- Phase I: Recovery of IPv4 address space
- Phase II: Allocation of recovered IPv4 address space by the IANA
5.1 Phase I: Recovery of IPv4 address space
Upon ratification of this policy by the ICANN Board of Directors the
IANA shall establish a mechanism to receive IPv4 address space which
is returned to it by the RIRs, and hold that address space in a
'recovered IPv4 pool'.
Each RIR through their respective chosen policies and strategies may
recover IPv4 address space which is under their administration. Each
RIR shall at quarterly intervals return any such recovered address
space to the IANA in aggregated blocks of /24 or larger, for
inclusion in the recovered IPv4 pool.
During Phase I, no allocations will be made from the recovered IPv4
pool.
5.2 Phase II: Allocation of recovered IPv4 address space by the IANA
Upon ratification of this policy by the ICANN Board of Directors and
a declaration by the IANA that its existing free pool of unallocated
IPv4 address space is depleted; Global Addressing Policy ASO-001-2
(adopted by ICANN Board 8 April 2005) [2] is rescinded. IANA will
then commence to allocate the IPv4 address space from the recovered
IPv4 pool.
5.2.1 Allocation of IPv4 address space
a. For the purposes of this policy, an 'IPv4 allocation
period' is defined as a 6-month period following 1 March or
1 September in each year.
b. At the beginning of each IPv4 allocation period, the IANA
will determine the 'IPv4 allocation unit' for that period,
as 1/10 of its IPv4 address pool, rounded down to the next
CIDR (power-of-2) boundary.
c. In each allocation period, each RIR may issue one IPv4
request to the IANA. Providing that the RIR satisfies the
allocation criteria described section 4.2.2, the IANA will
allocate a single allocation unit, composed of the smallest
possible number of blocks available in its IPv4 address
pool.
5.2.2 IPv4 address space allocation criteria
A RIR is eligible to receive additional IPv4 address space
from the IANA when the total of its IPv4 address holdings is
less than 50% of the current IPv4 allocation unit, and
providing that it has not already received an IPv4 allocation
from the IANA during the current IPv4 allocation period.
5.2.3 Initial allocation of IPv4 address space
Each new RIR shall, at the moment of recognition, be
allocated one (1) allocation unit by the IANA. If an
allocation unit is not available, then the IANA will issue
this block as soon as one is available. This allocation will
be made regardless of the newly formed RIR's projected
utilization figures and shall be independent of the IPv4
address space that may have been transferred to the new RIR
by the already existing RIRs as part of the formal transition
process.
5.3 Reporting
a. All returned space is to be recorded in an IANA-published log of
IPv4 address space transactions, with each log entry detailing
the returned address block, the date of the return, and the
returning RIR.
b. All allocated space is also to be recorded in this IANA-published
log of IPv4 address space transactions, with each log entry
detailing the address blocks, the date of the allocation and the
recipient RIR.
c. The IANA will maintain a public registry of the current
disposition of all IPv4 address space, detailing all reservations
and current allocations and current IANA-held address space that
is unallocated.
d. The IANA may make public announcements of IPv4 address block
transactions that occur under this policy. The IANA will make
appropriate modifications to the "Internet Protocol V4 Address
Space" page of the IANA website [3] and may make announcements to
its own appropriate announcement lists. The IANA announcements
will be limited to which address ranges, the time of allocation
and to which Registry they have been allocated.
5.4 Timetable for implementation
This policy is to be implemented immediately upon ratification by
the ICANN Board of Directors according to the global policy process
described in the ASO MoU [4].
6. Advantages and disadvantages of the proposal
-------------------------------------------------
6.1 Advantages
- The policy provides a mechanism for the ongoing distribution of
IPv4 address space.
6.2 Disadvantages
- None identified.
7. Effect on APNIC members
----------------------------
This policy governs the allocation relationship between the IANA and
the RIRs. It does not imply any change to allocation relationships
between APNIC and its members.
8. Effect on NIRs
-------------------
This policy governs the allocation relationship between the IANA and
the RIRs. It does not imply any change to allocation relationships
between APNIC and NIRs.
9. References
-------------
[1] Section 5, ICANN Address Supporting Organization (ASO) MoU
http://aso.icann.org/docs/aso-mou2004.html
[2] Global Addressing Policy ASO-001-2
http://aso.icann.org/docs/aso-001-2.pdf
[3] Internet Protocol v4 Address Space
http://www.iana.org/assignments/ipv4-address-space
[4] Attachment A: Global Policy Development Process, ASO MoU
http://aso.icann.org/docs/aso-mou2004.html
####### /Global Policy Proposal for the Allocation of IPv4 Blocks to
Regional Internet Registries #######
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
https://lists.afrinic.net/pipermail/rpd/attachments/20090305/cdebd163/attachment.htm
------------------------------
_______________________________________________
rpd mailing list
rpd at afrinic.net
https://lists.afrinic.net/mailman/listinfo.cgi/rpd
End of rpd Digest, Vol 35, Issue 2
**********************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20090309/9688c314/attachment.html>
More information about the RPD
mailing list