[AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-09.txt

internet-drafts@ietf.org Mon, 16 July 2012 15:16 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 402B921F8672; Mon, 16 Jul 2012 08:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level:
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j7Tn+zisqgfd; Mon, 16 Jul 2012 08:16:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83EA121F8680; Mon, 16 Jul 2012 08:16:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120716151638.1813.47649.idtracker@ietfa.amsl.com>
Date: Mon, 16 Jul 2012 08:16:38 -0700
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-09.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 15:16:40 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF.

	Title           : Why RTP Does Not Mandate a Single Security Mechanism
	Author(s)       : Colin Perkins
                          Magnus Westerlund
	Filename        : draft-ietf-avt-srtp-not-mandatory-09.txt
	Pages           : 9
	Date            : 2012-07-16

Abstract:
   This memo discusses the problem of securing real-time multimedia
   sessions, and explains why the Real-time Transport Protocol (RTP),
   and the associated RTP control protocol (RTCP), do not mandate a
   single media security mechanism.  Guidelines for designers and
   reviewers of future RTP extensions are provided, to ensure that
   appropriate security mechanisms are mandated, and that any such
   mechanisms are specified in a manner that conforms with the RTP
   architecture.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-avt-srtp-not-mandatory-09

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-avt-srtp-not-mandatory-09


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/