IETF Logo Mail Archive

Re: [rtcweb] Which parts of RFC 4733 are required?

Randell Jesup <randell-ietf@jesup.org> Mon, 28 November 2011 07:49 UTC

Return-Path: <randell-ietf@jesup.org>
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 71E3B21F8A55 for <rtcweb@ietfa.amsl.com>; Sun, 27 Nov 2011 23:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, 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 49-g7jA5b++x for <rtcweb@ietfa.amsl.com>; Sun, 27 Nov 2011 23:49:16 -0800 (PST)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 0E10921F87FC for <rtcweb@ietf.org>; Sun, 27 Nov 2011 23:49:16 -0800 (PST)
Received: from pool-173-49-135-74.phlapa.fios.verizon.net ([173.49.135.74] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1RUvxj-0007Zl-Lj for rtcweb@ietf.org; Mon, 28 Nov 2011 01:49:15 -0600
Message-ID: <4ED33CAB.7020201@jesup.org>
Date: Mon, 28 Nov 2011 02:47:55 -0500
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <mic312r58213o9qkb9gg0ey5.1321693128138@email.android.com> <4EC89DFA.1070404@alvestrand.no> <94435311-1C14-468A-9ECF-B5CD1B8C6768@acmepacket.com> <4ED339DC.9080209@jesup.org>
In-Reply-To: <4ED339DC.9080209@jesup.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] Which parts of RFC 4733 are required?
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: Mon, 28 Nov 2011 07:49:16 -0000

On 11/28/2011 2:35 AM, Randell Jesup wrote:
>> A3-10 WebRTC MUST NOT generate audio RTP packets while
>> sending [RFC4733] DTMF event packets.
>
> I would modify A3-10:
>
> A3-10 WebRTC MUST NOT generate audio RTP packets for
> the same SSRC while
> sending [RFC4733] DTMF event packets.
>
> I.e. if you're sending two audio streams, DTMF in one doesn't block DTMF
> in the other.

Doh!  "DTMF in one doesn't block *audio* in the other"


-- 
Randell Jesup
randell-ietf@jesup.org

v2.23.0 | Report a Bug | By Email