route/origin

  > Elise Gerich <epg at merit.edu> writes:
  > Let me repeat what I think has been said - just to make sure I have it
  > straight.
  > 
  > 1)The route object will NOT permit multiple values for the origin attribute

Correct.

  > 2)The unique key will be route/origin, thereby permitting multiple entries
  > for the same route in the registries.

Correct.

  > 3)The Merit Routing Registry can replace the INETNUM object with the
  > ROUTE object. The ROUTE object is the "policy" relevant object. The
  > INETNUM object is the assignment/allocation relevant object.

Correct.

  > As Jessica, has mentioned, our initial preference is to permit
  > multiple values for the origin attribute.  It seems cleaner
  > to us, and would require fewer modifications to current tools (we think).

The problem with it is control.
The object is guarded by the AS guardian. What if there are many?
Also what if the components or even the description differ?



-------- Logged at  Thu Apr 28 18:08:35 MET DST 1994  ---------