Search RPD Archives
[rpd] Fwd: [sig-policy] [New Policy Proposal] prop-114: Modification in the ASN eligibility criteria
Owen DeLong
owen at delong.com
Sun Feb 8 04:01:39 UTC 2015
I will say here what I said there…
I will oppose such a proposal. I suggest as an alternative, that the requirement be “Multihome or have a unique routing policy”.
There are some situations where one needs an ASN even though one is not multihomed. Such situations involve a unique routing policy where you may not be multihomed, but you may be peering with more than one ASN or you may have additional internal peering sessions or you may be a stub network with address portability requirements that cannot be met without being able to autonomously control the announcement and withdrawl of your prefixes. Likely there are others that I have not considered.
Owen
> On Feb 7, 2015, at 19:33 , Ernest <ernest at afrinic.net> wrote:
>
> FYI - this could be of interest in our region.
>
> The proposal removes the need to multi-home as the only criteria to
> receive an ASN, replaces it with:
>
> " An organization is eligible for an ASN assignment if is planning
> to use it within next 6 months "
>
> More below.
>
>> -----------------------------------------------------------
>> prop-114-v001: Modification in the ASN eligibility criteria
>> -----------------------------------------------------------
>>
>> Proposer: Aftab Siddiqui
>> aftab.siddiqui at gmail.com
>>
>> Skeeve Stevens
>> skeeve at eintellegonetworks.com
>>
>>
>> 1. Problem statement
>> --------------------
>>
>> The current ASN assignment policy dictates two eligibility criteria
>> and both should be fulfilled in order to get 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.
>>
>>
>> 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 removing multi-homing requirement for the organization.
>>
>>
>> 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
>> 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 organization is eligible for an ASN assignment if it:
>> - Is planning to use it within next 6 months
>>
>>
>> 5. Advantages / Disadvantages
>> -----------------------------
>>
>> Advantages:
>>
>> Removing the mandatory multi-homing requirement from the policy will
>> make sure that organizations are not tempted to provide wrong
>> information in order to fulfil the criteria of eligibility.
>>
>> Disadvantages:
>>
>> No disadvantage.
>>
>>
>> 6. Impact on resource holders
>> -----------------------------
>>
>> No impact on existing resource holders.
>>
>>
>> 7. References
>> -------------
>>
>> * sig-policy: APNIC SIG on resource management policy *
>> _______________________________________________
>> sig-policy mailing list
>> sig-policy at lists.apnic.net
>> http://mailman.apnic.net/mailman/listinfo/sig-policy
> _______________________________________________
> rpd mailing list
> rpd at afrinic.net
> https://lists.afrinic.net/mailman/listinfo.cgi/rpd
More information about the RPD
mailing list