[payload] Errata proposal for RFC4733

Xavier Marjou <xavier.marjou@orange.com> Mon, 07 January 2013 15:05 UTC

Return-Path: <xavier.marjou@gmail.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5831421F88B5 for <payload@ietfa.amsl.com>; Mon, 7 Jan 2013 07:05:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 GVuKbLq3ujnW for <payload@ietfa.amsl.com>; Mon, 7 Jan 2013 07:05:28 -0800 (PST)
Received: from mail-qc0-f171.google.com (mail-qc0-f171.google.com [209.85.216.171]) by ietfa.amsl.com (Postfix) with ESMTP id C403021F88CA for <payload@ietf.org>; Mon, 7 Jan 2013 07:05:28 -0800 (PST)
Received: by mail-qc0-f171.google.com with SMTP id d1so12494826qca.16 for <payload@ietf.org>; Mon, 07 Jan 2013 07:05:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=kBPGRJEOjyDkti6loB1wZx0gtSrqPTShAsTAuqGtx1w=; b=mkpG6aqaQxkznyGyjE8NQ+ZSBPo2UL27GjpMWPT2XcUVOIfuJKWydOWjUczbX2q/ux B1E//lSvzbBTVVmh+4TFkcln9m41vqEERM19tksn4FO7qq39/xv21E90THHyELwOn15R lJyDzdSP/jac1wR3JwfXrJLC1bwux8Vq4Jh4YmdYVfHMVsAPIesxOcEVfykyTX/3iJ6q u6VoES010f3i2EuMRJjPhOm0FcnAfHcP+VKqp0QsPVBkPxdqZL2H7YJCFTj+gNs2LbmK 6W5TnS+RMX6m7OLoVYGVRA+oGa0RSYDNpMtHa7ElRbgGCe5ptQXgEFnGD2oOoD0FigBv UoAQ==
MIME-Version: 1.0
Received: by 10.224.223.17 with SMTP id ii17mr43219880qab.13.1357571128327; Mon, 07 Jan 2013 07:05:28 -0800 (PST)
Sender: xavier.marjou@gmail.com
Received: by 10.49.63.227 with HTTP; Mon, 7 Jan 2013 07:05:28 -0800 (PST)
Date: Mon, 07 Jan 2013 16:05:28 +0100
X-Google-Sender-Auth: iBw_1PFJN1zH3SGV_MhoJm8pinc
Message-ID: <CAErhfryedEu5m9zBWC0utrVeGYvCwnTCzxPQ-Rrsd1Kox4kMtQ@mail.gmail.com>
From: Xavier Marjou <xavier.marjou@orange.com>
To: payload@ietf.org
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: [payload] Errata proposal for RFC4733
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 15:05:29 -0000

Hi,

During the last AVTEXT meeting (c.f.
http://tools.ietf.org/wg/avtext/minutes?item=minutes-85-avtext.html),
we discussed one ambiguity in RFC4733 (RTP Payload for DTMF Digits)
when using DTMF and WB audio codecs.

Here is an errata proposal to clarify this ambiguity. What do you think ?

CURRENT TEXT:

2.  RTP Payload Format for Named Telephone Events
2.1.  Introduction
…
   Named telephone events are carried as part of the audio stream and
   MUST use the same sequence number and timestamp base as the regular
   audio channel to simplify the generation of audio waveforms at a
   gateway.


NEW PROPOSED TEXT:

2.  RTP Payload Format for Named Telephone Events
2.1.  Introduction
…
  Named telephone events are carried as part of the audio stream and
  MUST use the same SSRC (therefore the same timing and sequence
  number space) and the same timestamp clock rate as the regular
  audio channel to simplify the generation of audio waveforms at a
  gateway.

Cheers,
Xavier