IETF Logo Mail Archive

Re: [rtcweb] #1: RFC 4734 citation

Randell Jesup <randell-ietf@jesup.org> Tue, 23 October 2012 13:39 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 8393B21F867A for <rtcweb@ietfa.amsl.com>; Tue, 23 Oct 2012 06:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.279
X-Spam-Level:
X-Spam-Status: No, score=-2.279 tagged_above=-999 required=5 tests=[AWL=0.320, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gw88jbr7tn+r for <rtcweb@ietfa.amsl.com>; Tue, 23 Oct 2012 06:39:36 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 1516721F8672 for <rtcweb@ietf.org>; Tue, 23 Oct 2012 06:39:35 -0700 (PDT)
Received: from pool-173-49-129-2.phlapa.fios.verizon.net ([173.49.129.2]:1976 helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <randell-ietf@jesup.org>) id 1TQehi-0005F0-Tg for rtcweb@ietf.org; Tue, 23 Oct 2012 08:39:35 -0500
Message-ID: <50869D99.50602@jesup.org>
Date: Tue, 23 Oct 2012 09:37:29 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <066.ee8d274029b0215df9ff464ea44b5fe7@trac.tools.ietf.org>
In-Reply-To: <066.ee8d274029b0215df9ff464ea44b5fe7@trac.tools.ietf.org>
Content-Type: text/plain; charset="UTF-8"; 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] #1: RFC 4734 citation
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: Tue, 23 Oct 2012 13:39:36 -0000

On 10/22/2012 6:36 PM, rtcweb issue tracker wrote:
> #1: RFC 4734 citation
>
>   Section 3 states:
>
>      WebRTC clients are REQUIRED to implement the following audio codecs.
>
>      o  Opus [RFC6716], with any ptime value up to 120 ms
>
>      o  G.711 PCMA and PCMU with one channel, a rate of 8000 Hz and a
>         ptime of 20 - see section 4.5.14 of [RFC3551]
>
>      o  Telephone Event - [RFC4734]
>
>   [BA] I believe the citation should be to "RTP Payload for DTMF Digits,
>   Telephony Tones, and Telephony Signals" [RFC4733], not to "Definition of
>   Events for Modem, Fax, and Text Telephony Signals" [RFC4734].
>
>   If the desire is in fact to mandate support for RFC 4734, please explain
>   why it is necessary for browsers to include support for digital encoding
>   of modem and fax signals.
>

I'm certain the intent was RFC 4733.

-- 
Randell Jesup
randell-ietf@jesup.org

v2.31.3 | Report a Bug | By Email | System Status