that is in practice true for 99% of you.
the state key does not include the interface, but the direction. as long as routes do not change that is equivalent to beeing bound to the interface.
Would you agree then that the behavior of non -current pf is the equivalent of if-bound? If so, is there good reason to change the default behavior now to floating? I think most users by now have adjusted to the if-bound type behavior. I know I've seen more than one discussion on this list and other places where people compare pf and ipf's state creation mechanisms and the response is that pf binds state to the interface (even though as you point out above that's not technically true). People then write their rules and adjust their thinking accordingly.
.joel
