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 :-).

Believe it or not.  We do have such 'law' or common commitment exist.  E.g.
One should not do proxy aggregate for an AS with talking to the AS.  It is
something that everyone knows that they should not do or else they will break
things.  Maybe you will have a better name for it :-)  
	

  >> 	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.

Noop, we should enforce to do coordinated proxy aggregation.
			       ~~~~~~~~~~~ 

>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.

Agree. I thought about this as well and this is very necessary.  This will partially
address my concern on this. 

In order to close on this, let me ask the following questions:

1. Concept wise, is it better to have a given route described by one and only one
   route object than to have the route described by multiple object ?

2. Implementation wise, is it easier to have route be the unique key or
   route/origin as unique key? (query, etc)

3. Which way is easier for tool writing:
	one route object, multiple origins or
	multiple route object, one origin ?

						--Jessica












	


Daniel

------- End of Forwarded Message




-------- Logged at  Fri Apr 29 17:24:44 MET DST 1994  ---------