as-in/as-out

Have just quickly browsed thru the document. Thanks for sending it.

On the paragraph that says:
"Conceptually there can be multiple route objects with different
origins.  Representing multiple proxy aggregation which to our knowledge
is not done in the Internet yet."

The NSFNET service will be doing proxy aggregation for DISA and Westnet
real soon now (the code is ready). And it seems likely that some
multi-homed entity in the future will ask both(or more) peer ASs to
aggregate nets on their behalf.  Could the unique key be route and origin,
instead of just route? How would you propose to deal with
this case? It seems shortsighted of us if we cannot accommodate proxy
aggregation.
        --Elise 



-------- Logged at  Wed Apr 27 19:50:48 MET DST 1994  ---------