This document specifies the Interactive Connectivity Establishment (ICE) 2.0 Bandwidth Management Extensions. This protocol consists of a set of proprietary extensions to the Interactive Connectivity Establishment (ICE) Extensions 2.0, as described in [MS-ICE2].
The protocol described in [MS-ICE2] specifies how to set up Real-Time Transport Protocol (RTP) streams in a way that allows the streams to traverse network address translation (NAT) and firewalls. The protocol described in [MS-ICE2] is agnostic to bandwidth or other policy constraints and attempts to find the highest priority path for the media session.
This protocol specifies how to determine and enforce bandwidth policy constraints by communicating with a bandwidth policy aware server.
This protocol facilitates:
Communication with a server based on the protocol described in [MS-TURNBWM] that supports network bandwidth utilization management and access control. The server is known as a bandwidth policy server. The bandwidth policy server uses this protocol to determine any policy constraints that necessitate avoiding viable media paths that could potentially be used for media flow.
Enforces bandwidth policy constraints and ensures that policy restricted paths are not used for media flow.
Periodically reports to the bandwidth policy server the path and the bandwidth being utilized by the media session.
Sections 1.8, 2, and 3 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in RFC 2119. Sections 1.5 and 1.9 are also normative but cannot contain those terms. All other sections and examples in this specification are informative.