Simply advertising a network doesn’t mean you need the addresses or that you’re actually using them in an operational network.It just means you typed in a BGP anchor statement.OwenOn Mar 4, 2015, at 16:44 , Skeeve Stevens <skeeve at v4now dot com> wrote:How do you see needs basis going away in this wording?
...SkeeveSkeeve Stevens - Senior IP Brokerv4Now - an eintellego Networks serviceskeeve at v4now dot com ; www.v4now.comPhone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeveIP Address Brokering - Introducing sellers and buyersOn Thu, Mar 5, 2015 at 9:31 AM, Owen DeLong <owen at delong dot com> wrote:+1… I’m with Dean… Still opposed.Let’s keep needs basis in place, please. I’m all for removing the requirement to multihome, but not the requirement to actually need the addresses for an operational network.OwenOn Mar 4, 2015, at 16:09 , Dean Pemberton <dean at internetnz dot net dot nz> wrote:Just to clarify.This still looks to remove needs based allocation and shift that to an "ability to advertise".Am I missing something here?
On Thursday, 5 March 2015, Masato Yamanishi <myamanis at gmail dot com> wrote:Dear SIG membersA new version of the proposal “prop-113: Modification in the IPv4eligibility criteria" has been sent to the Policy SIG for review.Information about earlier versions is available from:You are encouraged to express your views on the proposal:- Do you support or oppose the proposal?- Is there anything in the proposal that is not clear?- What changes could be made to this proposal to make it more effective?Please find the text of the proposal below.Kind Regards,Masato--------------------------------------------------------------------------prop-113-v002: Modification in the IPv4 eligibility criteria-------------------------------------------------------------------------Proposer: Aftab SiddiquiSkeeve Stevens1. Problem statement-----------------------------The current APNIC IPv4 delegation policy defines multipleeligibility criteria and applicants must meet one criteria to beeligible to receive IPv4 resources. One of the criteria dictatesthat “an organization is eligible if it is currently multi-homedwith provider-based addresses, or demonstrates a plan to multi-homewithin one month” (section 3.3).The policy seems to imply that multi-homing is mandatory even ifthere is no use case for the applicant to be multi-homed or evenwhen there is only one upstream provider available, this has createdmuch confusion in interpreting this policy.As a result organizations have either tempted to provide incorrector fabricated multi-homing information to get the IPv4 resources orbarred themselves from applying.2. Objective of policy change--------------------------------------In order to make the policy guidelines simpler we are proposing tomodify the text of section 3.3.3. Situation in other regions------------------------------------ARIN:There is no multi-homing requirementRIPE:There is no multi-homing requirement.LACNIC:Applicant can either have multi-homing requirement or interconnect.AFRINIC:There is no multi-homing requirement.4. Proposed policy solution------------------------------------Section 3.3: Criteria for small delegationsAn organization is eligible if:- it is currently multi-homedOR,- currently utilising provider (ISP) assignment of at least a /24,AND- intends to be multi-homedOR,- intends to be multi-homedAND- advertise the prefixes within 6 months5. Advantages / Disadvantages------------------------------------------Advantages:Simplifies the process of applying for IPv4 address space for smalldelegations and delays the immediate requirement for multi-homing asdetermined to be appropriate within the timeframe as detailed inSection 3.3.Disadvantages:There is no known disadvantage of this proposal.6. Impact on resource holders-----------------------------------------No impact on existing resource holders.
--
--
Dean Pemberton
Technical Policy Advisor
InternetNZ
+64 21 920 363 (mob)
dean at internetnz dot net dot nz
To promote the Internet's benefits and uses, and protect its potential.
* sig-policy: APNIC SIG on resource management policy *
_______________________________________________
sig-policy mailing list
sig-policy at lists dot apnic dot net
http://mailman.apnic.net/mailman/listinfo/sig-policy
* sig-policy: APNIC SIG on resource management policy *
_______________________________________________
sig-policy mailing list
sig-policy at lists dot apnic dot net
http://mailman.apnic.net/mailman/listinfo/sig-policy
* sig-policy: APNIC SIG on resource management policy *
_______________________________________________
sig-policy mailing list
sig-policy at lists dot apnic dot net
http://mailman.apnic.net/mailman/listinfo/sig-policy