Latest and hopefully last iteration of ripe-81++

  >* 2. In interas-out the <metric> is optional, please mention that in the doc.
  >*    interas-in is fine with <pref> being mandatory.
  >* 

>Okay - but I saw no mention of this in your proposal.

The proposal we sent out only clearifies the definition of <pref> in 
interas-in/out per our meeting at Ann Arbor fter the nanog.  I expect 
everything else in these two attributes are the same as in our original
paper which calls them as-in/as-out.  There you will see <metric> in
as-out is optional.  Not a big deal, just want to clarify it for point 3 
as well. 

>  * 3. In both interas-in and interas-out, <local-info> should be optional.
  >* 
>Why ? - does it harm to have it non optional - doesn't this cause problems
>for your parser ?????

>Again no mention in your original.

The reason is not mentioned there is the same as above.  The proposal was
just for pref definition not for other part of the interas-in/out component.
The other part should refer to the original Merit paper which indicates routerid
is optional.

One of the reasons to make it optional is that a lot of times, you just need
to have identify one router, say your neighbor's router .  One does not need
always list them in pairs. 

>* 4. See some misunderstanding about the pref-type and pref.  We may not writ
  >* e it
  >* clearly in our paragraph to you.  Can we discuss it face-to-face at the iet
  >* f? 
  >* 
>If you think we can reach an understanding yes.

Yes. See you there.

						--Jessica



-------- Logged at  Fri Jul 22 14:38:51 MET DST 1994  ---------