Re: [rtcweb] use cases, F20 and encryption, SCTP - comments on draft-ietf-rtcweb-use-cases-and-requirements-07
"Timothy B. Terriberry" <tterriberry@mozilla.com> Fri, 27 April 2012 16:58 UTC
Return-Path: <tterriberry@mozilla.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 5001E21F8714 for <rtcweb@ietfa.amsl.com>; Fri, 27 Apr 2012 09:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.307
X-Spam-Level:
X-Spam-Status: No, score=-5.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
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 Yj0rACIph4Gj for <rtcweb@ietfa.amsl.com>; Fri, 27 Apr 2012 09:58:00 -0700 (PDT)
Received: from dm-mail03.mozilla.org (dm-mail03.mozilla.org [63.245.208.213]) by ietfa.amsl.com (Postfix) with ESMTP id E854421F86DB for <rtcweb@ietf.org>; Fri, 27 Apr 2012 09:58:00 -0700 (PDT)
Received: from [172.17.0.5] (c-69-181-137-38.hsd1.ca.comcast.net [69.181.137.38]) (Authenticated sender: tterriberry@mozilla.com) by dm-mail03.mozilla.org (Postfix) with ESMTP id 7CACC4AED9F; Fri, 27 Apr 2012 09:58:00 -0700 (PDT)
Message-ID: <4F9AD018.8060708@mozilla.com>
Date: Fri, 27 Apr 2012 09:58:00 -0700
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20120113 SeaMonkey/2.4.1
MIME-Version: 1.0
References: <0fc001cd2495$a3985950$eac90bf0$@com>
In-Reply-To: <0fc001cd2495$a3985950$eac90bf0$@com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org, draft-ietf-rtcweb-use-cases-and-requirements@tools.ietf.org
Subject: Re: [rtcweb] use cases, F20 and encryption, SCTP - comments on draft-ietf-rtcweb-use-cases-and-requirements-07
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: Fri, 27 Apr 2012 16:58:01 -0000
Dan Wing wrote: > is a critical requirement. I suggest adding "The browser MUST support a > baseline SRTP keying mechanism." We have not reached consensus on that > keying mechanism, but the requirement is real. On the contrary, the conclusion of the consensus call in http://www.ietf.org/mail-archive/web/rtcweb/current/msg04125.html said: "...no one objected against making DTLS-SRTP a mandatory to implement and the default keying mechanism." Regardless of the debate over SDES, that sounds like we have _a_ baseline SRTP keying mechanism.
- [rtcweb] use cases, F20 and encryption, SCTP - co… Dan Wing
- Re: [rtcweb] use cases, F20 and encryption, SCTP … Timothy B. Terriberry
- Re: [rtcweb] use cases, F20 and encryption, SCTP … Harald Alvestrand
- Re: [rtcweb] use cases, F20 and encryption, SCTP … Randell Jesup
- Re: [rtcweb] use cases, F20 and encryption, SCTP … Martin Thomson
- Re: [rtcweb] use cases, F20 and encryption, SCTP … Magnus Westerlund
- Re: [rtcweb] use cases, F20 and encryption, SCTP … Stefan Hakansson LK