Cisco Cisco Packet Data Interworking Function (PDIF)
Diameter Dictionaries and Attribute Definitions
Diameter Attributes ▀
AAA Interface Administration and Reference, StarOS Release 17 ▄
57
Table 5. QoSFilterRule Field Description
Field
Description
action
This field can be set to one of the following:
tag — Mark packet with a specific DSCP [DIFFSERV]. The DSCP option MUST be included.
meter — Meter traffic. The metering options MUST be included.
dir
The format is as described under IPFilterRule.
proto
The format is as described under IPFilterRule.
src and
dst
dst
The format is as described under IPFilterRule.
options
The following options are available in addition to the ones described under IPFilterRule:
DSCP <color> — Color values as defined in [DIFFSERV]. Exact matching of DSCP values is required (no
masks or ranges).
masks or ranges).
metering <rate> <color_under> <color_over> — The metering option provides Assured Forwarding, as
defined in [DIFFSERVAF], and MUST be present if the action is set to meter. The rate option is the
throughput, in bits per second, which is used by the access device to mark packets. Traffic above the rate is
marked with the color_over codepoint, while traffic under the rate is marked with the color_under codepoint.
The color_under and color_over options contain the drop preferences, and MUST conform to the
recommended codepoint keywords described in [DIFFSERVAF] (e.g. AF13).
defined in [DIFFSERVAF], and MUST be present if the action is set to meter. The rate option is the
throughput, in bits per second, which is used by the access device to mark packets. Traffic above the rate is
marked with the color_over codepoint, while traffic under the rate is marked with the color_under codepoint.
The color_under and color_over options contain the drop preferences, and MUST conform to the
recommended codepoint keywords described in [DIFFSERVAF] (e.g. AF13).
The metering option also supports the strict limit on traffic required by Expedited Forwarding, as defined in
[DIFFSERVEF]. The color_over option may contain the keyword "drop" to prevent forwarding of traffic that
exceeds the rate parameter.
[DIFFSERVEF]. The color_over option may contain the keyword "drop" to prevent forwarding of traffic that
exceeds the rate parameter.
Grouped AVP Values
The Diameter protocol allows AVP values of type 'Grouped.' This implies that the Data field is actually a sequence of
AVPs. It is possible to include an AVP with a Grouped type within a Grouped type, that is, to nest them. AVPs within
an AVP of type Grouped have the same padding requirements as non-Grouped AVPs.
AVPs. It is possible to include an AVP with a Grouped type within a Grouped type, that is, to nest them. AVPs within
an AVP of type Grouped have the same padding requirements as non-Grouped AVPs.
The AVP Code numbering space of all AVPs included in a Grouped AVP is the same as for non-grouped AVPs.
Further, if any of the AVPs encapsulated within a Grouped AVP has the 'M' (mandatory) bit set, the Grouped AVP itself
MUST also include the 'M' bit set.
Further, if any of the AVPs encapsulated within a Grouped AVP has the 'M' (mandatory) bit set, the Grouped AVP itself
MUST also include the 'M' bit set.
Every Grouped AVP defined MUST include a corresponding grammar, using ABNF (with modifications), as defined
below.
below.
grouped-avp-def = name "::=" avp
name-fmt = ALPHA *(ALPHA / DIGIT / "-")
name = name-fmt
avp = header [ *fixed] [ *required] [ *optional] [ *fixed]
header = "<" "AVP-Header:" avpcode [vendor] ">"