Re: [Idr] new revision of private use ASN reservation draft

[Jon Mitchell <[e-mail]>]

On Mon, Aug 20, 2012 at 11:22:56PM +0900, Randy Bush wrote:
> >> "If private use ASNs are used between cooperating operators, special
> >> attention should be given to ensuring uniqueness of the private use
> >> ASNs between the operators. The use of the newer, numerically higher
> >> range of private use ASNs is recommended for such cooperative use
> >> between multiple operators, its significantly larger size allows the
> >> coordination of large ranges for each cooperating operator,
> >> simplifying "
> > 
> > Although in many cases, we know that these situations are a reality,
> > I'm a bit concerned about the language here as it might encourage such
> > use or mis-use of private ASN's that both Chris and Randy were
> > concerned with, and boundary (public) ASN's or other approaches maybe
> > better approaches to solve this problem depending on the specific use
> > case.  Secondly, the above seems to imply that using the newer range
> > is preferred, when in reality many other approaches as long as they
> > were coordinated would work (one use older range, one use newer range,
> > centralized database/registry, etc...).
> 
> let's be honest here.  what is being said is that this is really a new
> public space with ad hoc assignment and recording.  we already have a
> centralized database, we should use it.
> 

Disagree, but I think we already established that.  I know of at least a
couple of use cases where private ASN usage needs to be coordinated
between different groups (typically within a company) but there is no
Internet connectivity for said ASNs.  When I said registry above, I
meant private registry run by an organization for the users of their
private ASN space, not one that is exposed to the public or Internet
(maybe wrongly used the word centralized to describe this).  That said,
I'm happy to not mention coordinated assignment in the draft at all as I
mentioned above, I actually think this is the more sane approach as
otherwise we are detailing many use cases for private asns and giving
recommendations and guidance on what should be done for each (which in
some case is definitely not to use them).  I'd prefer to stay out of
recommendations for how people use "private use" ASNs as unless they are
leaking these improperly to the Internet, it should not impact me.  :-)

Cheers,

Jon