[ppml] Alternatives to 2002-3 Wording and Scope - Please Eval uate

[Leo Bicknell]

In a message written on Mon, Oct 13, 2003 at 10:55:16AM +0200, Gregory Massel wrote:
> I think the original wording was pretty good. There requirement for ASN is 
> simply a unique routing policy. Eg. If you want to interconnect at an 
> exchange / peering point, you need an ASN, but you're not technically 
> "multi-homed" because you still only have one transit provider.

I can live with the original wording.  My though was this might
help usclean up more "mess" and unify it under one general rule.
For example, exchange points have a special micro-assignment policy
today.  Since the ASN policy makes exceptions for them, if we just
go with "have an ASN" they would be covered (up to /24).

More to the point, I can't think of a single case where it would
make sense to give an entity an ASN and not IP space.  An ASN without
IP space is useless, and I find poking holes in upstream blocks
much less preferred to just giving them a /24.

> I'm a bit concerned about "ARIN assigned ASN." I'm not sure if it's possible, 
> but what are the chances of an organization applying to ARIN for address 
> space but having an ASN assigned from elsewhere? Were there historical ASN 
> assignments? Maybe ARIN can clarify if this is an issue or not.

Excellent point.  I never thought about it, but "ARIN assigned ASN"
to me really means "ARIN managed ASN", eg, all the legacy stuff as
well.  My point was simply that the IP space should be obtained
from the same place as the ASN...if we're going to make having an
ASN be a pre-requirement we should make sure we know the requirements
of the assigning entity.

-- 
       Leo Bicknell - bicknell at ufp.org - CCIE 3440
        PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - tmbg-list-request at tmbg.org, www.tmbg.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20031013/176861b1/attachment.sig>