Why not parsable (was: RIPE-81++...)

	Remember... we want interas-in/out to be compatible with as-in/out
(so we need only 1 parser). This was proposed by Jesscia *and* lpj.
We could have:

interas-in: [from] <aut-num> [<local-rid> <neighbor-rid>] <preference> ...

but it's a pain to enter both neighbor-rid and local-rid when we
care about only one of the values.
		Laurent

PS: jimi, could you change your mind?

> 
> 
>  Laurent Joncheray <lpj at merit.edu> writes:
>   * 	Oh well, i've changed my mind again, this is not parsable.
>   * RIPE-81++: "from <aut-num> [<local-rid>] [<neighbor-rid>] <preference> ..."
>   * 
>   * 	<preference> is mandatory. <neighbor-rid> and <local-rid> are
>   * ip addresses. My former example was wrong. We should read:
>   * 
>   * interas-in: from AS1104 192.87.45.254/32 (pref=MED) accept AS786 AS987
>   * interas-in: from AS1104 192.87.45.253/32 (pref=MED) accept AS786 AS987
>   * 
>   * 	Obviously we cannot make a difference between neighbor-rid and
>   * local-rid. And because both are optional.
>   *
> Right and just said - this was proposed by Juesscia. Lets just make
> them mandatory and we are done.
> 
> 	--Tony.
> 
> 


-- 
Laurent Joncheray,                                 E-Mail: lpj at merit.edu
    Merit Network Inc, 1071 Beal Avenue,           Phone:  +1 (313) 936 2065
    Ann Arbor, MI 48109, USA                       Fax:    +1 (313) 747 3745
"This is the end, Beautiful friend. This is the end, My only friend, the end" JM



-------- Logged at  Tue Aug 23 16:37:57 MET DST 1994  ---------