as-in/as-out

  > Jessica Yu <jyy at merit.edu> writes:
  > 
  > I assume 'origin' has the same concept as 'creator' which we defined at our
  > San Diego meeting.  Just try to be sure.

Yes. If we call it route then origin sounded better but 
we can change it to creator again if you like.

  > Does your definition above mean that one route can only have one 'origin'? 

No. See my response to elise.

  > Proxy aggregate like mentioned in your write up is not been done yet.  But 
  > it  will be very soon.  

Proxy aggregation per-se is not a problem. It gets hairy if it is done
by multiple ASes. But the registry will support that.

  > Proxy aggregate for multi-homed AS will be done when people get desperte to
  > reduce the routing table size, so does aggregation beyond AS boundary.  So
  > it is really desirable for routing registry to be designed to anticipate th
  > is
  > will happen and be able to deal with it.  If you allow one route has more t
  > han
  > one orgin, that will do it.  What is the concern of doing that? 

The concern is not with the registry but with the usefulness of the tools.

Daniel

PS: Now we make a proposal that drops one-net one AS and we still get flamed.
:-( ;-)

Daniel



-------- Logged at  Thu Apr 28 17:25:40 MET DST 1994  ---------