]> QUALCOMM, Inc.

5775 Morehouse Dr San Diego CA USA +1 858-845-1267 ldondeti@qualcomm.com

France Telecom

4, rue du Clos Courtel 35512 Cesson Sevigne Cedex France + 33 (0)2 99 12 49 27 david.castleford@orange-ftgroup.com

Ericsson Research

Ericsson Allee 1 52134 Herzogenrath Germany +49 2407 575389 frank.hartung@ericsson.com

MIKEY General Extension Payload IANA registration OMA BCAST This document specifies a new Multimedia Internet KEYing (MIKEY) General Extension payload (RFC 3830) to transport the short-term key message (STKM) and long-term key message (LTKM) payloads defined in the Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast (BCAST) group's Service and Content protection specification.

The Multimedia Internet Keying (MIKEY) protocol specification defines a General Extension payload to allow possible extensions to MIKEY without having to allocate a new payload type. The General Extension payload can be used in any MIKEY message and is part of the authenticated/signed data part. There is an 8-bit type field in that payload. The type code assignment is IANA-managed, and RFC 3830 requires IETF consensus for assignments from the public range of 0-240. The Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast (BCAST) group's Service and Content Protection specification specifies the use of a short-term key message (STKM) and a long-term key message (LTKM) that carry attributes related to Service and Content protection. Note that any keys associated with the attributes are part of the MIKEY KEMAC payload. This document specifies the use of the General Extension payload of MIKEY to carry the LTKMs or STKMs. RFC 3830 , the MIKEY General Extension payload defined in , and the 3rd Generation Partnership Project (3GPP)'s Multimedia Broadcast/Multicast Service (MBMS) document specify the transport of MIKEY messages via unicast or broadcast and the OMA specifications use either for transport of MIKEY messages.

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 . We refer to the General Extension type -- 5 -- as the OMA BCAST STKM/LTKM MIKEY General Extension .

Section 6.1 of RFC 3830 specifies the first three fields of the General Extension Payload and defines a variable length Data field. This document specifies the use of Type 5 for OMA BCAST Service and Content Protection using the Smartcard Profile. The contents of the variable length data field are defined below. 8 bits. This field indicates the type of the OMA BCAST payload. In this specification, only two values are specified: LTKM (1), and STKM (2). Variable length. The contents of this field are defined in Section 6 of the OMA BCAST Service and Content Protection specification .

This document specifies the use of MIKEY General Extension Payload Type 5 and a couple of subtype values (1 and 2), one each for OMA BCAST Service and Content protection's STKM and LTKM payloads. Interoperability considerations span several standards bodies, with OMA BCAST 1.0 enabler compliance being the key aspect; as such, it is up to the OMA test planning to verify the interoperability and compliance of OMA BCAST 1.0 implementations. This payload type assignment does not change MIKEY beyond RFC 3830 and RFC 4563 .

According to RFC 3830, the general extension payload can be used in any MIKEY message and is part of the authenticated/signed data part. The parameters proposed to be included in the OMA BCAST MIKEY General Extension payload (listed in ) need only to be integrity protected, which is already allowed by the MIKEY specification. The OMA BCAST MIKEY General Extension Payload SHALL be integrity protected. Furthermore, keys or any parameters that require confidentiality MUST NOT be included in the General Extension Payload. If keys or other confidential data are to be transported via the General Extension Payload, such data MUST be encrypted and encapsulated independently. Finally, note that MIKEY already provides replay protection and that protection covers the General Extension Payload also.

IANA has allocated a new General Extension Type from the "General Extensions payload name spaces" in the IANA registry at http://www.iana.org/assignments/mikey-payloads for use by OMA BCAST. Furthermore, IANA maintains a list of corresponding subtypes (0-255) as follows: 0 ... Reserved 1 ... LTKM 2 ... STKM 3 ... 191 (maintained by IANA and assigned by IETF Review ) 192 ... 255 (Private use)

Many thanks to Jari Arkko, Piron Laurent, and Steffen Fries for their reviews and suggestions for improvement.

&rfc2119; &rfc3830; &keyid; Open Mobile Alliance 3GPP Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations in different implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). In order for IANA to manage a given name space prudently, it needs guidelines describing the conditions under which new values can be assigned, or when modifications to existing values can be made. If IANA is expected to play a role in the management of a name space, the IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on IANA.