Re: confederations and ASN allocation
Hi,
>With the current confederation draft, which best describes how the
>confederation may assign ASNs to members:
>
>1. one ASN only per member
>2. one ASN per independent network block (e.g. if a confederation member has
> two /19 networks allocated from the confederation, they can have two)
>3. no restriction at all, as long as they can make use of it
> (e.g. if the member has a /19 and decides to split it up into different
> pieces and route them independently, at their own risk, can the
> confederation grant the ASNs?)
4. Independent of amount of address space -- ASNs are allocated if
and only if the routing policy of a site differs from that of its
upstream providers. The only relationship between ASes and amount of
address space is that you need at least one (1) IP address to make an
ASN worthwhile. The determining factor is what routes you accept
from/announce to which of your providers. See RFC 1930 for details.
>How about ASN allocation to non-members?
Again, dependent on routing policy. Cost: US $500 per ASN one time,
US $50 maintenance fee.
Regards,
-drc
_________________________________________________________________________
| To unsubscribe: send "unsubscribe" to apnic-talk-request at apnic dot net |
+-----------------------------------------------------------------------+