IETF Logo Mail Archive

[rtcweb] #1: RFC 4734 citation

"rtcweb issue tracker" <trac+rtcweb@trac.tools.ietf.org> Mon, 22 October 2012 22:36 UTC

Return-Path: <trac+rtcweb@trac.tools.ietf.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 7E6DE11E808D for <rtcweb@ietfa.amsl.com>; Mon, 22 Oct 2012 15:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 sd+wa4WIuYZ9 for <rtcweb@ietfa.amsl.com>; Mon, 22 Oct 2012 15:36:30 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id E619D11E80AD for <rtcweb@ietf.org>; Mon, 22 Oct 2012 15:36:28 -0700 (PDT)
Received: from localhost ([127.0.0.1]:52941 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+rtcweb@trac.tools.ietf.org>) id 1TQQbW-00057U-F6; Tue, 23 Oct 2012 00:36:14 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: rtcweb issue tracker <trac+rtcweb@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: jmvalin@jmvalin.ca, bernard_aboba@hotmail.com
X-Trac-Project: rtcweb
Date: Mon, 22 Oct 2012 22:36:14 -0000
X-URL: http://tools.ietf.org/rtcweb/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/rtcweb/trac/ticket/1
Message-ID: <066.ee8d274029b0215df9ff464ea44b5fe7@trac.tools.ietf.org>
X-Trac-Ticket-ID: 1
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: jmvalin@jmvalin.ca, bernard_aboba@hotmail.com, rtcweb@ietf.org
X-SA-Exim-Mail-From: trac+rtcweb@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
X-Mailman-Approved-At: Tue, 23 Oct 2012 01:27:04 -0700
Cc: rtcweb@ietf.org
Subject: [rtcweb] #1: RFC 4734 citation
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2012 22:36:31 -0000

#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.

-- 
--------------------------------+------------------------
 Reporter:  bernard_aboba@…     |      Owner:  jmvalin@…
     Type:  defect              |     Status:  new
 Priority:  critical            |  Milestone:  milestone1
Component:  audio               |    Version:  1.0
 Severity:  Active WG Document  |   Keywords:
--------------------------------+------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/rtcweb/trac/ticket/1>
rtcweb <http://tools.ietf.org/rtcweb/>

v2.23.0 | Report a Bug | By Email