RFC 5410

Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST 1.0

📅 published January 2009, from ietf

RFC 5410: Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST 1.0 💖

okay bestie, let's start with the title block 🎀

Network Working Group, Request for Comments: 5410, dated January 2009 🌸

Authors: A. Jerichow, Ed. from Nokia Siemens Networks, and L. Piron from Nagravision S.A. 🫶

Category: Informational ✨

Obsoletes: 4909. This RFC replaces RFC 4909, so if you see that one floating around, this is the newer version 💅

Status of This Memo

This memo gives information to the Internet community. It is not a standard of any kind 📖 Distribution of this memo is unlimited, so share it with everyone 🦋

Copyright Notice

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, because they describe your rights and restrictions with respect to this document 👑

Abstract

This document specifies a new Multimedia Internet KEYing (MIKEY) General Extension payload 🎀 It carries the short-term key message (STKM) and long-term key message (LTKM) payloads, plus the management data LTKM reporting message and parental control message payloads. All of these are defined in the Open Mobile Alliance's (OMA) Broadcast (BCAST) group's Service and Content protection specification 🌈

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.  MIKEY General Extension for OMA BCAST Usage . . . . . . . . . . 3
4.  Interoperability Considerations . . . . . . . . . . . . . . . . 4
5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7.  Changes since RFC 4909  . . . . . . . . . . . . . . . . . . . . 5
8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
  9.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
  9.2.  Informative References  . . . . . . . . . . . . . . . . . . 6

1. Introduction ✨

okay so the MIKEY protocol spec (RFC 3830 [RFC3830]) has a General Extension payload 🧚 It lets people add extensions to MIKEY without having to grab a whole new payload type. The General Extension payload can show up in any MIKEY message, and it's part of the authenticated/signed data part. There's an 8-bit type field in that payload. The type codes are IANA-managed, and RFC 3830 requires IETF consensus for assignments from the public range of 0-240 💅

The OMA BCAST group's Service and Content Protection specification [SPCP] describes a short-term key message (STKM), a long-term key message (LTKM), an LTKM reporting message, and a parental control message. These carry attributes for Service and Content protection 🔐 Any keys tied to those attributes, like the Parental Control Pincode if there is one, live in the MIKEY KEMAC payload. Important detail, bestie 🙈

This document defines how the General Extension payload of MIKEY carries those messages above. It also covers protecting the credentials using mechanisms that MIKEY supports, with the modifications in [RFC3830] 🦋

RFC 3830 [RFC3830], the MIKEY General Extension payload from RFC 4563 [RFC4563], and the 3rd Generation Partnership Project (3GPP)'s Multimedia Broadcast/ Multicast Service (MBMS) document [3GPP.33.246] all describe how MIKEY messages travel over unicast or broadcast. The OMA BCAST specs use either one to transport MIKEY messages 🌸

2. Terminology 💜

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 [RFC2119] 📚

OMA BCAST MIKEY General Extension: we call the General Extension type, which is 5, the OMA BCAST MIKEY General Extension 🎀

3. MIKEY General Extension for OMA BCAST Usage 🌈

The OMA BCAST Type (Type 5) formats the MIKEY General Extension payload like this:

                    1                   2                   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! Next Payload !      Type     !            Length            !
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
!       OMA BCAST Data Subtype  (variable length)             ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Figure 1: OMA BCAST MIKEY General Extension 🍓

Next Payload and Length are defined in Section 6.15 of [RFC3830] 👑

Type (8 bits): this identifies the type of the General Extension Payload (see Section 6.15 of [RFC3830]). This document adds a new type. It specifies Type 5 for OMA BCAST Service and Content Protection using the Smartcard Profile 🔥

Type        | Value | Comments
------------------------------------------------------------------
OMA BCAST   |     5 | information on type and identity of messages

Figure 2: Definition of the OMA BCAST MIKEY General Extension Payload 🎀

OMA BCAST Data Subtype (variable length): this defines a variable length Data field 🦋 It's built out of subtype-payloads, and the contents of the variable length OMA BCAST Data Subtype field are defined below 🌸

                    1                   2                   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
!   Subtype     ! Subtype Specific Data (variable length)     ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Figure 3: STKM/LTKM/LTKM Reporting/Parental Control Subtype Payload ✨

Subtype: 8 bits. This field indicates the subtype of the OMA BCAST payload. This specification defines four values: LTKM (1), STKM (2), LTKM Reporting (3), and Parental Control (4) 💖

Subtype Specific Data: variable length 🧁

OMA BCAST Data Subtype | Value | Comment
-----------------------------------------------------------
LTKM                   |     1 | Long Term Key Message
STKM                   |     2 | Short Term Key Message
LTKM Reporting         |     3 | LTKM Reporting Message
Parental Control       |     4 | Parental Control Message

Figure 4: Subtype Definitions for OMA BCAST Messages 💅

The contents of the OMA BCAST Data Subtype payload field are defined in Section 6 of the OMA BCAST Service and Content Protection specification [SPCP] 📖

4. Interoperability Considerations 🫶

This document uses MIKEY General Extension payload Type 5 with four subtype values: 1 and 2 for the LTKM and STKM payloads of OMA BCAST Service and Content protection, 3 for the LTKM Reporting payload, and 4 for the Parental Control payload 🌈 Interop spans several standards bodies, and OMA BCAST 1.0 enabler compliance is the big key. So it's up to the OMA test planning to verify interoperability and compliance of OMA BCAST 1.0 implementations 🔍 This payload type assignment doesn't change MIKEY beyond RFC 3830 [RFC3830] and RFC 4563 [RFC4563] ✨

5. Security Considerations 🔐

Okay, this section is serious, so listen up 💀 According to RFC 3830 [RFC3830], the General Extension payload can show up in any MIKEY message, and it's part of the authenticated/signed data part. The parameters that go into the OMA BCAST MIKEY General Extension payload (listed in Section 3) only need integrity protection, and MIKEY already allows that. The OMA BCAST MIKEY General Extension payload SHALL be integrity protected 🛡️ Keys or any parameters that need confidentiality MUST NOT be included in the General Extension payload. If keys or other confidential data are going to be transported via the General Extension payload, that data MUST be encrypted and encapsulated independently 🚨 Last thing: MIKEY already provides replay protection, and that protection also covers the General Extension payload 💜

6. IANA Considerations 🎀

IANA has allocated an OMA BCAST MIKEY General Extension Type --5-- from the "General Extensions payload name space" for use by OMA BCAST, as requested by RFC 4909 [RFC4909] 👑 IANA also created a name space for the OMA BCAST payload subtype values defined in [RFC4909], and assigned these subtype values from that name space: LTKM (1), STKM (2) 🌸

IANA has allocated two new subtypes from the OMA BCAST payload subtype name space. They are:

Subtype Name: LTKM Reporting

Value: 3

and

Subtype Name: Parental Control

Value: 4

7. Changes since RFC 4909 🦋

The OMA BCAST Service and Content Protection specification [SPCP] has messages that were created after RFC 4909 was written. This document only adds the assignments needed to support those new messages. No values assigned by RFC 4909 [RFC4909] are modified 🧚

8. Acknowledgments 🫶

Many thanks to the authors of RFC 4909 [RFC4909] for letting us obsolete their RFC 💖

9. References 📚

9.1. Normative References

[3GPP.33.246] 3GPP, "3G Security; Security of Multimedia Broadcast/ Multicast Service (MBMS)", 3GPP TS 33.246 6.12.0, October 2007.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3830] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K. Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830, August 2004.
[RFC4563] Carrara, E., Lehtovirta, V., and K. Norrman, "The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)", RFC 4563, June 2006.
[SPCP] Open Mobile Alliance, "Service and Content Protection for Mobile Broadcast Services", OMA-TS-BCAST_SvcCntProtection-V1_0, <http://www.openmobilealliance.org>.

9.2. Informative References

[RFC4909] Dondeti, L., Castleford, D., and F. Hartung, "Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport", RFC 4909, June 2007.

Authors' Addresses ✈️

Anja Jerichow (editor)
Nokia Siemens Networks
Martinstr. 76
81541 Munich
Germany

Phone: +49 89 636-45868
EMail: anja.jerichow@nsn.com


Laurent Piron
Nagravision S.A.
Case Postale 134
1033 Cheseaux
Switzerland

Phone: +41 21 732 05 37
EMail: laurent.piron@nagravision.com

📦 where this page comes from

ietf: rfc5410 2009-01
💖 girlified by claude-haiku-5-5 on 2026-10-17: a language model's rewrite of the original, under its terms