[address-policy-wg] 2012-03 New Draft Document Published(Intra-RIR TransferPolicy Proposal)

> it would appear that the phrase ?Within the RIPE NCC service region,?
> is to be added at the beginning of the second paragraph in section
> 5.5.

I'm curious, why is this phrase being added? It does not seem to be
discussed in the proposal summary or rationale. It also seems redundant,
given that section 1.1 Scope in ripe-553 already says ?this document
describes the policies for the responsible management of globally unique
IPv4 Internet address space in the RIPE NCC service region?.

It appears to me that the new paragraph being added (?other than for an
additional allocation, for the purpose of determining need, a period of
24 months is used in evaluating a transferred allocation?), is on it's
own sufficient to accomplish 2012-03's stated goal of increasing the
transfer-need-period to 24 month.

--
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/

I agree with Tore.  While in the immediate term, 2012-03 will apply to
intra-RIR 
transfers within the RIPE region, the intent is to extend the needs
justification period
from 3 months to 24 months.  Now that the RIPE NCC is down to the last
/8, when an LIR is 
in need of IPv4 addresses, it is placed in the position of procuring
them from another LIR
within region.  Doing a procurement every 3 months would be onerous, and
extension is needed.

However, to Tore's point, there is no point in restricting the policy to
needs justification.  
It will be an independent decision to approve the inter-RIR policy
2012-02, but should this happen,
the needs justification period should be common for any procurement.

I think the intent of the rewording was to emphasize that it is a RIPE
NCC Policy,
but it could be misconstrued to imply that the policy is for transfers
within the RIPE NCC, and not
for any transfer to/from the RIPE NCC.

My suggestion, since it is part of the RIPE NCC Policy Manual, would be
to remove the words, as recommended
by Tore.  If 2012-02 is approved, it will make wording changes to 5.5 to
allow for inter-RIR transfers.

5.5 Transfers of Allocations

Any LIR is allowed to re-allocate complete or partial blocks of IPv4
address space that were previously allocated to them by either the RIPE
NCC or the IANA. Such address space must not contain any block that is
assigned to an End User.

Address space may only be re-allocated to another LIR that is also a
member of the RIPE NCC. The block that is to be re-allocated must not be
smaller than the minimum allocation block size at the time of
re-allocation. An LIR may only receive a transferred allocation after
their need is evaluated and approved by the RIPE NCC, following the
policies set for receiving further allocations within RIPE region (see
the Section 5.3 Additional Allocations of this document).

Other than for an additional allocation, for the purpose of determining
need, a period of 24 months is used in evaluating a transferred
allocation. 


Sandra Brown
President
IPv4 Market Group
sandrabrown at ipv4marketgroup.com
716-348-6768
www.ipv4marketgroup.com