as-in/as-out

  > Jessica Yu <jyy at merit.edu> writes:
  > >What if there are different components/hols making up the two routes.
  > 
  > 	It is dangrous for two ASs make the same proxy aggregate route
  > 	with different components.  

I know. I agree.

  >     That is something should be avoided

Certainly.

  > 	and perhaps outlawed.

Internet routing and The Law. Interesting thought :-).


  > 	By using one route object for multiple origins, it is able to
  > 	ENFORCE different ASs make consistent agggregate when they proxy
  > 	for other ASs.   That is a good argument for the design. 

By the same token proxy aggregation by different ASes is dangerous
and we should ENFORCE only one route object per route.

This can and will be done if people get really desperate. 
I can think of several scenarios for it. So we better
have a possibility to register it.

  > 	Who controls? The first AS regists win.  

Difficult at best.

  >     Of course, they
  > 	have to cordinate when the second AS regist the same
  > 	route object.  If they want to update that object, they
  > 	have to coordinate and they need to coordinate with each
  > 	other if the make the proxy aggr for the a particular AS.

I agree. But we can give them a tool to warn about inconsistencies.
Same goal, less hassle. Clear divison of responsibility for registration.

Daniel



-------- Logged at  Thu Apr 28 22:35:16 MET DST 1994  ---------