Diameter Per-Flow Max Bitrates

This document provides a mechanism for the specification of per-flow maximum bit rates. Such values are used to limit individual flow rates while maintaining a higher aggregate maximum bit rate across aggregate flows. It supplements the various values defined Aggregate Maximum Bitrates such as those specified for IP Mobility .

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

The Per-Flow-Max-DL-Bit-Rate AVP (AVP Code TBD1) is of type Unsigned32. It specifies the maximum downlink bit rate that is requested/ allocated for each of the mobile node's IP flows. The measurement units are bits per second.

The Per-Flow-Max-UL-Bit-Rate AVP (AVP Code TBD1) is of type Unsigned32. It specifies the maximum uplink bit rate that is requested/ allocated for each of the mobile node's IP flows. The measurement units are bits per second.

IANA allocated AVP codes in the IANA-controlled namespace registry specified in Section 11.1.1 of for the following AVPs that are defined in this document. AVP AVP Code Section Defined Data Type Per-Flow-Max-DL-Bit-Rate TBD1 UTF8String Per-Flow-Max-UL-Bit-Rate TBD2 GROUPED

This document defines new AVPs to limit the maximum bitrate of an IP flow (5-tuple) in the mobile devices uplink or downlink. As these are further constraints on Diameter applications already specifying aggregeate maximum bit rates, they do not introduce new security concerns for an Authorized User. For an operator, access to this data may give some insight to how the associated service operates. It is RECOMMENDED that this or any Diameter communication is secured. The Security Considerations of the Diameter protocol itself have been discussed in RFC . Use of the AVPs defined in this document MUST take into consideration the security issues and requirements of the Diameter base protocol.