[Xorp-users] [Xorp-hackers] Policy network4 operator

[Pavlin Radoslavov]

> > Seriously, though, is it only the person who originally implemented
> > this feature in XORP (Andrea and probably later updated by Marko?),
> > Atanu and me who think that comparing network addresses indeed means
> > comparing network addresses?
> 
> Maybe :-)  The operators seem reverse to the last time I implemented it,
> and the way I'm used to it in a Cisco notation.

Again, as I mentioned earlier, the Cisco notation reasoning doesn't
apply here.
In Cisco, the comparison is network address vs. prefix length.
In our case we have network address vs. network address.


This thread is getting too long, so let me repeat again my question
about the short/medium term solution.
If you can't accept the current behavior, would you like us to
invest some time trying to implement the Juniper-like keywords:

"network4 exact 10.0.0.0/8"     SAME AS "network4 == 10.0.0.0/8"
"network4 longer 10.0.0.0/8"    SAME AS "network4 < 10.0.0.0/8"
"network4 orlonger 10.0.0.0/8"  SAME AS "network4 <= 10.0.0.0/8"
"network4 shorter 10.0.0.0/8"   SAME AS "network4 > 10.0.0.0/8"
"network4 orshorter 10.0.0.0/8" SAME AS "network4 >= 10.0.0.0/8"
"network4 not 10.0.0.0/8"       SAME AS "network4 != 10.0.0.0/8"

If yes, then please indicate whether we should use the
"shorter/orshorter/not" keywords or something else.

If you prefer a different solution, now is the time to suggest it
(flipping the operator direction excluded).

If there are no replies, then probably nothing will change until the
rtrmgr is reimplemented (bug #677) and we are in the position to
implement the long-term solution.

Pavlin