This looks good and consistent with what I mentioned before. Not sure - what are the rules when an organisation (already assigned with one public ASN) asks for another public ASN?
I suppose the rules should be a bit more strict when such request comes in...? Regards, Usman > On 5 Mar 2015, at 3:50 pm, Skeeve Stevens <[email protected]> wrote: > > In this text, the suggested guidelines have been removed to be replaced with: > > " > - you have been previous allocated provider independent address space by > APNIC AND > > - intend to multi-home in the future > " > > This policy can be reviewed on an annual basis for any impact on the number > of allocations of ASN and if there has been any detrimental effect. > > ====== > ----------------------------------------------------------- > prop-114-v003: Modification in the ASN eligibility criteria > ----------------------------------------------------------- > > Proposer: Aftab Siddiqui > [email protected] > > Skeeve Stevens > [email protected] > > > 1. Problem statement > -------------------- > > The current ASN assignment policy states two eligibility criteria and > that both criteria should be fulfilled in order to obtain an ASN. The policy > seems to imply that both requirements i.e. multi-homing and clearly defined > single routing policy must be met simultaneously, this has created much > confusion in interpreting the policy. > > As a result organizations have either provided incorrect information to > get the ASN or barred themselves from applying where they still have a valid > justification for obtaining an ASN. > > > 2. Objective of policy change > ----------------------------- > > In order to make the policy guidelines simpler we are proposing to modify > the text describing the eligibility criteria for ASN assignment by providing > alternate criteria to obtaining an ASN. > > > 3. Situation in other regions > ----------------------------- > > ARIN: > It is not mandatory but optional to be multi-homed in order get ASN > > RIPE: > Policy to remove multi-homing requirement is currently in discussion and the > current phase ends 12 February 2015 (awaiting Chair decision) > Policy - https://www.ripe.net/ripe/policies/proposals/2014-03 > > LACNIC: > Only inter-connect is mandatory not multi-homing > > AFRINIC: > It is mandatory to be multi-homed in order to get ASN. > > > 4. Proposed policy solution > --------------------------- > > An organisation is eligible for an ASN assignment if: > > - they are currently multi-homed OR > > - you have been previous allocated provider independent address space by > APNIC AND > > - intend to multi-home in the future > > > > 5. Advantages / Disadvantages > ----------------------------- > > Advantages: > > By adding the additional criteria of Guidelines managed by APNIC Secretariat, > this would enable the Secretariat to make decisions based on common or rare > use cases, but that may still be a valid request. > > > Disadvantages: > > It may be perceived that this policy would enable members to obtain ASN’s > more easily, and in return cause faster consumption of ASN’s in the region. > Given the relative ease of obtaining an ASN with ‘work around’ methods, we do > not perceive this will actually have any effect. > > > 6. Impact on resource holders > ----------------------------- > > No impact on existing resource holders. > > > 7. References > ------------- > > > ====== > > ...Skeeve > > Skeeve Stevens - Senior IP Broker > v4Now - an eintellego Networks service > [email protected] ; www.v4now.com > Phone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeve > facebook.com/v4now ; linkedin.com/in/skeeve > twitter.com/theispguy ; blog: www.theispguy.com > > IP Address Brokering - Introducing sellers and buyers > * sig-policy: APNIC SIG on resource management policy > * > _______________________________________________ > sig-policy mailing list > [email protected] > http://mailman.apnic.net/mailman/listinfo/sig-policy
* sig-policy: APNIC SIG on resource management policy * _______________________________________________ sig-policy mailing list [email protected] http://mailman.apnic.net/mailman/listinfo/sig-policy
