Browse Prior Art Database

MIKEY: Multimedia Internet KEYing (RFC3830)

IP.com Disclosure Number: IPCOM000030800D
Original Publication Date: 2004-Aug-01
Included in the Prior Art Database: 2004-Aug-27

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Arkko: AUTHOR [+5]

Abstract

This document describes a key management scheme that can be used for real-time applications (both for peer-to-peer communication and group communication). In particular, its use to support the Secure Real- time Transport Protocol is described in detail.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group                                           J. Arkko

Request for Comments: 3830                                    E. Carrara

Category: Standards Track                                    F. Lindholm

                                                              M. Naslund

                                                              K. Norrman

                                                       Ericsson Research

                                                             August 2004

                   MIKEY: Multimedia Internet KEYing

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This document describes a key management scheme that can be used for

   real-time applications (both for peer-to-peer communication and group

   communication).  In particular, its use to support the Secure Real-

   time Transport Protocol is described in detail.

   Security protocols for real-time multimedia applications have started

   to appear.  This has brought forward the need for a key management

   solution to support these protocols.

Arkko, et al.               Standards Track                     [Page 1]

RFC 3830                         MIKEY                       August 2004

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

       1.1.  Existing Solutions . . . . . . . . . . . . . . . . . . .  4

       1.2.  Notational Conventions . . . . . . . . . . . . . . . . .  4

       1.3.  Definitions. . . . . . . . . . . . . . . . . . . . . . .  4

       1.4.  Abbreviations. . . . . . . . . . . . . . . . . . . . . .  6

       1.5.  Outline. . . . . . . . . . . . . . . . . . . . . . . . .  6

   2.  Basic Overview . . . . . . . . . . . . . . . . . . . . . . . .  7

       2.1.  Scenarios. . . . . . . . . . . . . . . . . . . . . . . .  7

       2.2.  Design Goals . . . . . . . . . . . . . . . . . . . . . .  8

       2.3.  System Overview. . . . . . . . . . . . . . . . . . . . .  8

       2.4.  Relation to GKMARCH. . . . . . . . . . . . . . . . . . . 10

   3.  Basic...