[arin-ppml] Draft Policy 2011-5: Shared Transition Space for IPv4 Address Extension - IAB comment
On February 15th, the following update to staff assessment for Draft Policy
2011-5 was made:
> In keeping with the spirit of RFC 2860 with respect to the assignment
> of specialized address blocks, ARIN Staff will consult with the IANA and
> the IAB regarding implementation of this draft policy.
Please find attached correspondence regarding consultation with the IAB on
Draft Policy 2011-5 "Shared Transition Space for IPv4 Address Extension".
The ARIN Board will consider this response and the recommendation to adopt
2011-5 at an upcoming meeting. It is quite possible that this will result
in the policy proposal being referred to the IETF for reconsideration, and
any parties interested in this Draft Policy should note this possibility
for purposes of planning their ongoing efforts in this area.
President and CEO
Begin forwarded message:
> From: Bernard Aboba <bernard_aboba at hotmail.com>
> Date: June 23, 2011 4:37:36 AM GMT+08:00
> To: <jcurran at arin.net>
> Cc: <ndavis at arin.net>, Russ Housley <housley at vigilsec.com>
> Subject: IAB comment on ARIN 2011-05
> Dear John,
> The IAB has reviewed your request for IAB/IESG guidance regarding Draft
> Policy ARIN-2011-5. We would like to submit the following for the ARIN
> board's consideration.
> == A Procedural Issue: ARINA 2011-005 and RFC2860 section 4.3 ==
> The IAB honors and values the division of responsibilities as
> documented in RFC 2860 section 4.3. That section forms the basis for
> Unicast address allocation via ICANN through the RIR system.
> The second paragraph of that section excludes 'assignments of
> specialised address blocks (such as multicast or anycast blocks)' from
> that IANA-> RIR model, leaving such blocks as the responsibility, and
> under the authority, of the IETF.
> Policy proposal 2011-005 is not a regular proposal in the sense that
> it adheres to Unicast space. In contrast, it allows for an allocation
> of addresses for special and global use very similar to, and almost
> indistinguishable from, RFC1918 local addresses. Because of the impact
> beyond the ARIN region the management (i.e. creation
> and subsequent changes) of such reservation should be global and RFC2860
> puts the management responsibility with the IETF.
> The IAB believes that the adoption by ARIN would be in conflict with the
> provisions in RFC2860 and would set a bad precedent: Setting aside
> special addresses should be done within the existing process, i.e. by
> the IETF.
> It is our expectation that the IAB and the ARIN Board are in general
> agreement about this interpretation.
> == Re-reviewing the Operational and Technical merits in the IETF ==
> The IAB is aware that earlier variations of the proposal have been brought
> to the IETF. However, there was very little support and some strong
> opposition to them, consequently, the IETF never reached consensus to
> approve them.
> If there is consensus for 2011-005 in the ARIN region we would be
> happy to work with you to resubmit the proposal to the IETF and, as
> usual, have the IESG judge consensus. This would include our reaching
> out to other RIRs to have members of their community provide input on
> this proposal. Clear support from the various RIR communities might
> bring new insights into to the IETF, producing a level of support that
> was not present with the earlier drafts.
> Obviously the IAB cannot commit to the outcome of that process, but we
> can work with you to make sure the proposal gets maximum exposure
> within the IETF and the broader community.
> [for the IAB],
> Bernard Aboba
> IAB Chair
> From: jcurran at arin.net
> To: bernard_aboba at hotmail.com; housley at vigilsec.com
> CC: ndavis at arin.net
> Subject: Request for IAB/IESG guidance regarding Draft Policy ARIN-2011-5 (Shared Transition Space for IPv4 Address Extension)
> Date: Tue, 14 Jun 2011 06:32:10 +0000
> To: IAB Chair Bernard Aboba & IETF/IESG Chair Russ Housley
> As noted in the communication of 10 April 2011 ..., the ARIN community
> has been working on a Draft Policy (ARIN-2011-5, Shared Transition Space for
> IPv4 Address Extension) which would result in the allocation of a /10 IPv4 address
> block for facilitating transition technologies. I am writing to provide an update on
> the status of this Draft Policy and to seek guidance from the IAB & IESG regarding
> appropriate next steps.
> After significant deliberation both online and during the ARIN Public Policy meeting,
> the ARIN Advisory Council (which consists of 15 members elected by the ARIN
> community) met in late May and recommended adoption of the Draft Policy by the
> ARIN Board. I have made to the ARIN AC as well as the community at large that
> since the proposed reservation is for shared use, it arguably could be considered
> as a specialized address block in accordance section 4.3 of RFC 2860, and would
> need to made under the guidance of IAB and IESG.
> On June 10th 2011, the ARIN Board of Trustees took the recommendation to adopt
> the Draft Policy under advisement, and directed me to consult with the IAB and IESG
> regarding any issues in adopting this Draft Policy.
> I am hereby requesting that the IAB and IESG consider this matter, and provide any
> guidance regarding recommendations for moving forward as deemed appropriate.
> I am available to discuss the matter by phone at the IAB and IESG's convenience;
> please let me know via email if this is desirable at any time.
> Best wishes and thank you for your consideration,
> John Curran
> President and CEO