"option:: established" does the wrong thing on Cisco. about capirca HOT 2 CLOSED

I do realize it is a bit dumb to filter "established" on a destination port. 
But I still find the output surprising...

This is expected behavior.  For stateless filtering, the "established" option 
simply appends high-ports (1024-65535) to the destination-ports.  Therefore, in 
the example term if results in a policy allowing src->dest of ports 22 and 
1024-65535.

From: http://code.google.com/p/capirca/wiki/PolicyFormat
...
option:: [established|tcp-established|sample|intial|rst|first-fragment]
established - only permit established connections, implements tcp-established 
if protocol is tcp only, otherwise adds 1024-65535 to required 
destination-ports.