[AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-16.txt
internet-drafts@ietf.org Thu, 16 January 2014 10:19 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 992221AE31F; Thu, 16 Jan 2014 02:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njIuXl0Tk0Lw; Thu, 16 Jan 2014 02:19:45 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DFC51AE314; Thu, 16 Jan 2014 02:19:45 -0800 (PST)
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.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140116101945.25114.11696.idtracker@ietfa.amsl.com>
Date: Thu, 16 Jan 2014 02:19:45 -0800
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-16.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 16 Jan 2014 10:19:46 -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 : Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution Authors : Colin Perkins Magnus Westerlund Filename : draft-ietf-avt-srtp-not-mandatory-16.txt Pages : 10 Date : 2014-01-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. This is relevant for designers and reviewers of future RTP extensions, 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-16 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-avt-srtp-not-mandatory-16 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-man… internet-drafts
- Re: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not… Magnus Westerlund