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

[Pavlin Radoslavov]

> Sorry I missed it originally, see my last email ;-)  Obviously we both have
> strong opinions about which sign direction is "right".  If people continue
> to vote in favor of flipping the sign behavior, would you be willing to
> consider changing the behavior?

No, because all mathematicians in the world will scream at me! :)

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?

It doesn't seem we are getting anywhere closer on agreeing what the
sign direction should be.
So the only remaining (short-term) option we have so far is to try
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"


> Btw, I think the right long term answer is to use something similar to the
> Juniper syntax, which removes any potential for ambiguity.

I agree about the long-term solution. The question is what to do
about it in short and medium term time scale.

Pavlin