[AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-08.txt
internet-drafts@ietf.org Mon, 31 October 2011 10:37 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 EB4F121F8D87; Mon, 31 Oct 2011 03:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level:
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 F+BRCnRMDta1; Mon, 31 Oct 2011 03:37:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E1F21F8D6C; Mon, 31 Oct 2011 03:37:52 -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: 3.62
Message-ID: <20111031103752.17672.85845.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2011 03:37:52 -0700
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-08.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, 31 Oct 2011 10:37:53 -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-08.txt
Pages : 11
Date : 2011-10-31
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. It also discusses how applications
using RTP can meet the goals of BCP 61 to have strong and mandatory
to implement security.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-srtp-not-mandatory-08.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-avt-srtp-not-mandatory-08.txt
- [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-man… internet-drafts
- Re: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not… Magnus Westerlund