datatracker.ietf.org
Sign in
Version 5.12.0.p2, 2015-03-02
Report a bug

Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport
RFC 4909

Document type: RFC - Informational (June 2007; Errata)
Obsoleted by RFC 5410, RFC 6309
Was draft-dondeti-msec-mikey-genext-oma (individual in sec area)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4909 (Informational)
Responsible AD: Russ Housley
Send notices to: ldondeti@qualcomm.com

Network Working Group                                    L. Dondeti, Ed.
Request for Comments: 4909                                QUALCOMM, Inc.
Category: Informational                                    D. Castleford
                                                          France Telecom
                                                              F. Hartung
                                                       Ericsson Research
                                                               June 2007

      Multimedia Internet KEYing (MIKEY) General Extension Payload
           for Open Mobile Alliance BCAST LTKM/STKM Transport

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) The IETF Trust (2007).

Abstract

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
   3.  MIKEY General Extension for OMA BCAST Usage . . . . . . . . . . 3
   4.  Interoperability Considerations . . . . . . . . . . . . . . . . 3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 5

Dondeti, et al.              Informational                      [Page 1]
RFC 4909           OMA BCAST MIKEY General Extension           June 2007

1.  Introduction

   The Multimedia Internet Keying (MIKEY) protocol specification [1]
   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 [2]
   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 [1], the MIKEY General Extension payload defined in [3], and
   the 3rd Generation Partnership Project (3GPP)'s Multimedia Broadcast/
   Multicast Service (MBMS) document [4] specify the transport of MIKEY
   messages via unicast or broadcast and the OMA specifications use
   either for transport of 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 [5].

   OMA BCAST STKM/LTKM MIKEY General Extension:  We refer to the General
      Extension type -- 5 -- as the OMA BCAST STKM/LTKM MIKEY General
      Extension .

Dondeti, et al.              Informational                      [Page 2]
RFC 4909           OMA BCAST MIKEY General Extension           June 2007

3.  MIKEY General Extension for OMA BCAST Usage

                            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   !      Type     !            Length             !
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       !       OMA BCAST S/LTKM Subtype  (variable length)      ~
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                Figure 1: OMA BCAST MIKEY General Extension

[include full document text]