Re: wildcard flowid in framework PIB?

[ post by non-subscriber.  with the massive amount of spam, it is easy to
  miss and therefore delete mis-posts.  so fix subscription addresses! ]

On 08-11-2002 04:17, Brian Williams <[email protected]> wrote:

> I understood the use of setting the length to zero was for unsupported
> attributes. If the intention is to use this for wildcards, then why is
> there a distinct wildcard value indicated for the protocol and DSCP
> attributes?

Well, at first sight I would say that they are same. After all, they mean
the same: ignore this header field. In fact, the distinction between
numerical wildcards (0, -1, etc,) and NULL wildcards has confused me.

However, in draft-ietf-rap-access-bind-02.txt (and all previous versions)
implicitly assumes that you can specify both a NULL and a numberical
wildcard. They have a very different meaning:

Allow me to use an example by Walter Weiss. Take for example these two
frwkIpFilter filters, which will match all packets, regardsless of the port
number of the source address.

Filter1:
 frwkIpFilterDstL4PortMin = <null>
 frwkIpFilterDstL4PortMax = <null>

Filter1:
 frwkIpFilterDstL4PortMin = 1
 frwkIpFilterDstL4PortMax = 65535

However, the access bind PIB specifies a signaling protocol, and for the
second filter, an event will be sent each time a new unique port number is
detected. For the first filter, the port number is ignored in determining if
an event must be sent.

Regards,
Freek Dijkstra