Session Description Protocol (SDP) Attributes for OMA BCAST Service and Content Protection

The Open Mobile Alliance (OMA)'s Broadcast (BCAST) group is specifying service and content protection mechanisms for broadcast services over wireless networks. As part of that specification, several new SDP attributes are necessary to allow the broadcast server to signal the service and content protection parameters to clients. Section 8.2.4 of RFC 4566 requires that new SDP attributes are registered through IANA with name, contact information and description (and other similar parameters). A standards track specification is RECOMMENDED if the new attribute(s) will have widespread use and interoperability considerations. OMA BCAST specifications are expected to be used by 3GPP MBMS, 3GPP2 BCMCS and DVB-H based broadcast wireless systems. This document provides descriptions of the SDP attributes used in the OMA BCAST Service and Content Protection specification .

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 following new SDP attributes have been specified: a=bcastversion:<major>.<minor> a=stkmstream:<id of the stkm stream> a=SRTPAuthentication:<id for SRTP authentication algorithm value> a=SRTPROCTxRate:<ROC transmission rate> See Section 5 for details on IANA considerations.

In addition to the notes in Section 7 of RFC 4566 , the following considerations may be applicable: Some of the new SDP parameters indicate the version, type of the key management system used for service or content protection of broadcast content. Others provide references to relevant key management traffic streams so that receivers can map the media streams to key streams and retrieve the necessary keys to decrypt media. Modification of references to key streams will result in DoS attacks, but nothing more. However, if the kmsversion parameter is sent unprotected, there may be possibilities for downgrade attacks.

This document, following the guidelines of , instructs IANA to register a number of SDP attributes.

This memo provides instructions to IANA to register a number of OMA BCAST only attributes in the Session Description Protocol Parameters registry . The registration data, according to RFC 4566 follows. Note to the RFC Editor: replace "RFC XXXX" with the RFC number of this specification.

Anja Jerichow <anja.jerichow@nsn.com> +49 89 636-45868 bcastversion:<major>.<minor> BCAST version session-level This attribute is not dependent on charset. This attribute specifies the OMA BCAST version "bcastversion" Value in the format x.y. The Value field is of XML data type Decimal. RFC XXXX and OMA-TS-BCAST_SvcCntProtection, Section 10.1.1

Anja Jerichow <anja.jerichow@nsn.com> +49 89 636-45868 stkmstream:<id of the stkm stream> Short Term Key Message stream identifyer session-level or media-level attribute The attribute can be at session level, in which case it applies to all media streams, or it can be at media level, in which case it only applies to the specified media and would overwrite possible session level attribute. This attribute is not dependent on charset. The stkmstream attribute specifies mapping Short Term Key Message streams to media streams in the SDP. Each session or media stream can have multiple stkmstream attributes. Using this attribute, the terminal can lookup the corresponding STKM stream announcements and figure out which one to listen to and process. We note that this attribute is optional and hence would not be there for unencrypted media streams. This field specifies the type of keystream as a string. The valid values are "stkm" for short term key messages and "ltkm" for long term key messages. RFC XXXX and OMA-TS-BCAST_SvcCntProtection, Section 10.1.3

Anja Jerichow <anja.jerichow@nsn.com> +49 89 636-45868 SRTPAuthentication:<id for SRTP authentication algorithm value> SRTP authentication algorithm value identifyer media-level This attribute is not dependent on charset. When SRTP is used, the attribute SRTPAuthentication states which authentication algorithm to use. Based on , the identifier is a transform-independent parameter of the cryptographic context for SRTP in integer format. One of the following three integrity transforms registered for the three modes MUST be used: value "2" for RCCm1, "3" for RCCm2 and "4" for RCCm3. RFC XXXX and OMA-TS-BCAST_SvcCntProtection, Section 10.4

Anja Jerichow <anja.jerichow@nsn.com> +49 89 636-45868 SRTPROCTxRate:<ROC transmission rate> ROC transmission rate media-level This attribute is not dependent on charset. When SRTP is used, the attribute SRTPROCTxRate is used to define the ROC transmission rate, R, which is given in network byte order. R MUST be a non-zero unsigned integer between 1 and 65535 inclusive, as specified in . If the ROC transmission rate is not included in the negotiation, the default value of 1 SHALL be used. RFC XXXX and OMA-TS-BCAST_SvcCntProtection, Section 10.4

Many thanks to Charles Lo, Uwe Rauschenbach, David Castleford, Hosame Abu-Amara, and Miguel Garcia for their help and support.