Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST 1.0
RFC 5410
| Document | Type |
RFC - Informational
(January 2009; No errata)
Updated by RFC 6309
Obsoletes RFC 4909
Was draft-jerichow-msec-mikey-genext-oma (individual in gen area)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5410 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Tim Polk | ||
| Send notices to | Hannes.Tschofenig@nsn.com | ||
Network Working Group A. Jerichow, Ed.
Request for Comments: 5410 Nokia Siemens Networks
Obsoletes: 4909 L. Piron
Category: Informational Nagravision S.A.
January 2009
Multimedia Internet KEYing (MIKEY) General Extension Payload
for Open Mobile Alliance BCAST 1.0
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
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, as they describe your rights
and restrictions with respect to this document.
Abstract
This document specifies a new Multimedia Internet KEYing (MIKEY)
General Extension payload to transport the short-term key message
(STKM) and long-term key message (LTKM) payloads as well as the
management data LTKM reporting message and parental control message
payloads defined in the Open Mobile Alliance's (OMA) Broadcast
(BCAST) group's Service and Content protection specification.
Jerichow & Piron Informational [Page 1]
RFC 5410 OMA BCAST MIKEY GenExt January 2009
Table of Contents
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
The Multimedia Internet KEYing (MIKEY) protocol specification (RFC
3830 [RFC3830]) 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) Broadcast (BCAST) group's Service
and Content Protection specification [SPCP] specifies the use of a
short-term key message (STKM), a long-term key message (LTKM), an
LTKM reporting message, and a parental control message that carry
attributes related to Service and Content protection. Note that any
keys associated with the attributes, such as the Parental Control
Pincode if present, are part of the MIKEY KEMAC payload.
This document specifies the use of the General Extension payload of
MIKEY to carry the messages mentioned above, as well as protection of
the credentials using mechanisms supported by MIKEY with
modifications in [RFC3830].
RFC 3830 [RFC3830], the MIKEY General Extension payload defined in
RFC 4563 [RFC4563], and the 3rd Generation Partnership Project
(3GPP)'s Multimedia Broadcast/ Multicast Service (MBMS) document
[3GPP.33.246] specify the transport of MIKEY messages via unicast or
broadcast; the OMA BCAST specifications use either for transport of
MIKEY messages.
Jerichow & Piron Informational [Page 2]
RFC 5410 OMA BCAST MIKEY GenExt January 2009
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 refer to the General Extension
type -- 5 -- as the OMA BCAST MIKEY General Extension.
Show full document text