Re: ASN draft

[Tony Bates <[e-mail]>]

Okay picking up on one of these....

 [e-mail] (Bill Manning) writes:
  * 
  * > But seriously, I think you're in the Merrit trap.  This home AS stuff is
  * > a bunch of BS.  There's nothing really (right now) that says that I can't
  * > advertise my nets with multiple first ASs in the path... heck, the "P"
  * > service provider and the "N" service provider have been doing that for
  * > years.
  * > 
  * > Why should a prefix be tied to an AS?  That's just the way Merrit organiz
  * ed
  * > things,  but I think that was one honking mistake, looking back on it now
  * .
  * > 
  * 
  * Visions of Haley Mills as lord high routing wizzard are dancing before my
  * tired eyes.  Very Scary.   
  * I don't think this is a Merit/PRDB thing.  I got this home-as stuff from th
  * e
  * RIPE stuff.
  * 
Time to go redo your homework. You are referring to history. Check
ripe-181... A prefix can be in multiple ASes no problem...

  * To me, the AS defines an administrative bound. One that can request delegat
  * ions
  * of address space.  One those delegations are made, then there can be a mapp
  * ing
  * of route announcements.  But there does not have to be.  In that case the 
  * prefix delegation to AS map acts as an indicator of potential for new route
  * s.
  * In a routing registry and in Rwhois, the ASN is the tag used to identify
  * the scope of the administrative bound.
  * 
Umm...I think you are mixing things here, between trying to define
what an AS is today and trying to do sensible pragmatic (dear I say
"real world") allocation of ASes with a method of routing registry
identification and for that matter "ownership" ??? of NLRIs. 
The draft clearly stays away from this.

		--T