On Mar 4, 2015, at 21:27 , Gaurab Raj Upadhaya <gaurab@lahai.com> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I support this.

- -gaurab


On 3/5/15 4:50 AM, Skeeve Stevens 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

aftab.siddiqui@gmail.com <mailto:aftab.siddiqui@gmail.com>


Skeeve Stevens

skeeve@eintellegonetworks.com 
<mailto:skeeve@eintellegonetworks.com>



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 skeeve@v4now.com <mailto:skeeve@v4now.com> ;
www.v4now.com <http://www.v4now.com/>

Phone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeve

facebook.com/v4now <http://facebook.com/v4now> ;
<http://twitter.com/networkceoau>linkedin.com/in/skeeve 
<http://linkedin.com/in/skeeve>

twitter.com/theispguy <http://twitter.com/theispguy> ; blog:
www.theispguy.com <http://www.theispguy.com/>


IP Address Brokering - Introducing sellers and buyers


*              sig-policy:  APNIC SIG on resource management policy
* _______________________________________________ sig-policy
mailing list sig-policy@lists.apnic.net 
http://mailman.apnic.net/mailman/listinfo/sig-policy

- -- 

http://www.gaurab.org.np/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iEYEARECAAYFAlT36SwACgkQSo7fU26F3X2cuACglPD0tyZJ49oDuOD/Kqedsvcx
FsAAnj1U/+8Jgy8T1VEwrT60krby/puw
=rl5N
-----END PGP SIGNATURE-----
*              sig-policy:  APNIC SIG on resource management policy           *
_______________________________________________
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy