Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id DC2B821F883F for <rtcweb@ietfa.amsl.com>;
 Thu, 29 Mar 2012 08:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,
 BAYES_00=-2.599]
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 vAzyG765nIEd for
 <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 08:19:37 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com
 (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix)
 with ESMTP id 1F51D21F8841 for <rtcweb@ietf.org>;
 Thu, 29 Mar 2012 08:19:37 -0700 (PDT)
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by
 senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 50C6C1EB84B1;
 Thu, 29 Mar 2012 17:19:36 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by
 MCHP064A.global-ad.net ([172.29.37.63]) with mapi;
 Thu, 29 Mar 2012 17:19:36 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
 "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Thu, 29 Mar 2012 17:19:34 +0200
Thread-Topic: [rtcweb] Consensus call regarding media security
Thread-Index: Ac0M8kOUeqEsZNWCSMKEFgS7iyjaIgAy90KQ
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E31296C4CC7B@MCHP058A.global-ad.net>
References: <4F732531.2030208@ericsson.com>
In-Reply-To: <4F732531.2030208@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [rtcweb] Consensus call regarding media security
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list
 <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>,
 <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>,
 <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 15:19:38 -0000

I agree that there was clear consensus on mandating the use of SRTP but it =
was not clear to me what the consensus is regarding the use of SRTP with a =
null cipher. Does the statement "there was overwhelming consensus that all =
RTP packets SHALL be protected by SRTP" mean that the null cipher will not =
be allowed?

Regards
Andy



> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Magnus Westerlund
> Sent: 28 March 2012 16:50
> To: rtcweb@ietf.org
> Subject: [rtcweb] Consensus call regarding media security
>=20
> WG,
>=20
> In todays RTCWEB WG meeting there was discussion around media security
> mechanism. In this meeting there was some clear consensus in the
> meeting which we would like to confirm on the list.
>=20
> The first was that there was overwhelming consensus that all RTP
> packets SHALL be protected by SRTP.
>=20
> Secondly that no one objected against making DTLS-SRTP a mandatory to
> implement and the default keying mechanism. Additional mechanisms are
> not precluded.
>=20
> WG participants may state their position regarding these consensus
> calls
> until 12th of April when the chairs will declare the final consensus.
> If
> you where present in the meeting room and comment on this, please
> indicate that.
>=20
> Best Regards
>=20
> Magnus Westerlund
> For the WG chairs
>=20
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
