Re: [rtcweb] Few comments on draft-ietf-rtcweb-audio-07
Colin Perkins <csp@csperkins.org> Fri, 01 May 2015 10:30 UTC
Return-Path: <csp@csperkins.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87DC31B30EC for <rtcweb@ietfa.amsl.com>; Fri, 1 May 2015 03:30:42 -0700 (PDT)
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 hiV6DeabOZDF for <rtcweb@ietfa.amsl.com>; Fri, 1 May 2015 03:30:41 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E19721B30EB for <rtcweb@ietf.org>; Fri, 1 May 2015 03:30:40 -0700 (PDT)
Received: from [81.187.2.149] (port=41568 helo=[192.168.0.18]) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1Yo8DK-0002bI-LL; Fri, 01 May 2015 11:30:39 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <5542A84D.3040006@mozilla.com>
Date: Fri, 01 May 2015 11:30:28 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <812F2D7D-F2ED-4A3E-BD70-0A785422F72A@csperkins.org>
References: <7703998F-5364-487A-84F1-1AAEE6E4C3C8@cisco.com> <5542A84D.3040006@mozilla.com>
To: Jean-Marc Valin <jmvalin@mozilla.com>
X-Mailer: Apple Mail (2.1878.6)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/VEXoLa7nV2g3loWOukJY2kByGW4>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Few comments on draft-ietf-rtcweb-audio-07
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 01 May 2015 10:30:42 -0000
On 30 Apr 2015, at 23:10, Jean-Marc Valin <jmvalin@mozilla.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Cullen, Magnus, Colin, > > Thanks for the review. I just updated the draft. As some of you > pointed out, I changed all instances of "client" to "endpoint" to > match the terminology. See below for more: ... > On 20/04/15 03:40 PM, Colin Perkins wrote: >> - Section 3 says "Clients MAY use the offer/answer mechanism to >> signal a preference for a particular mode or ptime". Is this just >> of Opus, or in general? It might be worthwhile saying something >> explicit about acceptable ptime values in general. > > There was some discussion on acceptable ptime values in the past, but > there was no consensus achieved. > >> - Security considerations ought to explicitly point to the >> security considerations of RFCs 3389, 4733, 6716, and >> draft-ietf-payload-rtp-opus. It should possibly also point to the >> draft-ietf-rtcweb-security-arch-11, and the security >> considerations for RTP use in WebRTC in >> draft-ietf-rtcweb-rtp-usage-22 > > Done. Okay, thanks. That's fine for both. -- Colin Perkins https://csperkins.org/
- [rtcweb] Few comments on draft-ietf-rtcweb-audio-… Cullen Jennings (fluffy)
- Re: [rtcweb] Few comments on draft-ietf-rtcweb-au… Jean-Marc Valin
- Re: [rtcweb] Few comments on draft-ietf-rtcweb-au… Colin Perkins