MQC vs Policy-Routing use of match command

From: ccie2be (ccie2be@nyc.rr.com)
Date: Sun Mar 20 2005 - 12:28:06 GMT-3


Hi guys,
 
Until recently, I never gave much thought to this issue but now I'm
wondering.
 
When using MQC, the match command can match packets going in either
direction depending on what's being matched.
 
For example, a match command can match on most anything contained in the
header of the packet such as ip addr, ip prec, cos, etc. And, if the match
is against something contained in a field, the match can apply to packets
coming into the router or about to leave the router.
 
However, if the match is against something that isn't contained in a header
( at least not until the packet has it's layer 2 encapsulation) then the
packet can only be matched if it's going in the outbound direction.
 
For example, match fr-dlci <dlci #>. In this case, packets (frames) can
only be matched if they're incoming. True?
 
It could be useful to match on fr-dlci # for outgoing packets, but that
would require that the router do a layer 2 resolution before making the
match decision and I'm not sure if the router can that.
 
What do you guys think?
 
 
For Policy Routing, I assume the match can only be made on packets entering
the router, not packets about to leave the router. Does everyone agree?
 
TIA, Tim



This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:48 GMT-3