RFC 4909: Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5410, RFC 6309.
Current document in this lineage: RFC 5410 — Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST 1.0; RFC 6309 — IANA Rules for MIKEY (Multimedia Internet KEYing)
In plain English — editorial summary, not part of the RFC
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. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4909
- Published
- June 2007
- Authors
- L. Dondeti; D. Castleford; F. Hartung
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 4909 (2007)
- RFC 5410 (2009)
- RFC 6309 (2011) ✓
Read the full history of IANA Rules for MIKEY (Multimedia Internet KEYing) →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4964The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over CellularUpdated
September 2007
- RFC 5174A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU)Current
May 2008
- RFC 5224Diameter Policy Processing ApplicationCurrent
March 2008
- RFC 4563The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)Updated
June 2006
- RFC 5309Point-to-Point Operation over LAN in Link State Routing ProtocolsCurrent
October 2008
- RFC 5318The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)Updated
December 2008
- RFC 4354A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) ServiceCurrent
January 2006
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?