Re: [AVT] Protocol Action: 'RTP Payload Format for BroadVoice Speech Codecs' to Proposed Standard
"Mike" <mike_dsp@hotmail.com> Tue, 07 June 2005 12:59 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfdgB-0007Md-CJ; Tue, 07 Jun 2005 08:59:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dfdg9-0007MT-36 for avt@megatron.ietf.org; Tue, 07 Jun 2005 08:59:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20486 for <avt@ietf.org>; Tue, 7 Jun 2005 08:59:33 -0400 (EDT)
Received: from bay16-dav10.bay16.hotmail.com ([65.54.186.190] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dfe16-0002On-56 for avt@ietf.org; Tue, 07 Jun 2005 09:21:20 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 7 Jun 2005 05:59:20 -0700
Message-ID: <BAY16-DAV10E1A0037F6ACC7BE79CD7FDFA0@phx.gbl>
Received: from 207.107.229.2 by BAY16-DAV10.phx.gbl with DAV; Tue, 07 Jun 2005 12:59:20 +0000
X-Originating-IP: [207.107.229.2]
X-Originating-Email: [mike_dsp@hotmail.com]
X-Sender: mike_dsp@hotmail.com
From: Mike <mike_dsp@hotmail.com>
To: avt@ietf.org
References: <E1DctQS-0002i0-J0@newodin.ietf.org>
Subject: Re: [AVT] Protocol Action: 'RTP Payload Format for BroadVoice Speech Codecs' to Proposed Standard
Date: Tue, 07 Jun 2005 08:59:18 -0400
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-OriginalArrivalTime: 07 Jun 2005 12:59:20.0620 (UTC) FILETIME=[B87D9EC0:01C56B60]
X-Spam-Score: 2.3 (++)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
Is source code for the BroadVoice Speech codec readily available? Thank you. ----- Original Message ----- From: "The IESG" <iesg-secretary@ietf.org> To: "IETF-Announce" <ietf-announce@ietf.org> Cc: "avt chair" <magnus.westerlund@ericsson.com>; "avt chair" <csp@csperkins.org>; "Internet Architecture Board" <iab@iab.org>; "avt mailing list" <avt@ietf.org>; "RFC Editor" <rfc-editor@rfc-editor.org> Sent: Monday, May 30, 2005 7:12 PM Subject: [AVT] Protocol Action: 'RTP Payload Format for BroadVoice Speech Codecs' to Proposed Standard > The IESG has approved the following document: > > - 'RTP Payload Format for BroadVoice Speech Codecs ' > <draft-ietf-avt-rtp-bv-04.txt> as a Proposed Standard > > This document is the product of the Audio/Video Transport Working Group. > > The IESG contact persons are Allison Mankin and Jon Peterson. > > Technical Summary: > > This specification describes an RTP payload format for the BroadVoice > (TM) speech codec. It is a very straight-forward payload format, with > one or more frames of coded speech data being placed into each RTP > packet with no additional framing. Definitions to allow the use of > this format with SDP and MIME are provided. > > Working Group Summary: > > The working group supported advancing this specification. > The IETF has received a request from Cablelabs to publish this > specification quickly. > > Protocol Quality: > > The BroadVoice(TM) codec is likely to see widespread use in certain > communities. The design of the codec is a very good fit with the RTP > framework, and hence this protocol is simple and of high quality. > > MIME media types review received no comments. > > > Notes to the RFC Editor > > Abstract > > OLD: > This document describes the RTP payload format for the > BroadVoice(TM) narrowband and wideband speech codecs developed by > Broadcom Corporation. > NEW: > This document describes the RTP payload format for the > BroadVoice(TM) narrowband and wideband speech codecs. > The narrowband codec, called BroadVoice16, or BV16, > has been selected by CableLabs as a mandatory codec in > PacketCable 1.5 and has a CableLabs specification. > > Section 2, first paragraph > OLD: > BroadVoice is a speech codec family developed by Broadcom for VoIP > (Voice over Internet Protocol) applications, including Voice over > Cable, Voice over DSL, and IP phone applications. > NEW: > BroadVoice is a speech codec family developed for VoIP > (Voice over Internet Protocol) applications, including Voice > over Cable, Voice over DSL, and IP phone applications. > > Section 2, second paragraph: > > OLD: > More specifically, the BV16 codec was selected as one of the > mandatory audio codecs in PacketCable (TM) 1.5 Audio/Video > Codecs Specification [4]. > > NEW: > More specifically, the BV16 codec was selected as one of the > mandatory audio codecs in PacketCable (TM) 1.5 Audio/Video > Codecs Specification [4] and has been implemented by multiple > vendors. The wideband version (BV32) has been developed by > Broadcom but has not yet appeared in > a public specification; since it is technically very similar > to BV16, its payload format is also defined in this document. > > Section 3.1, Figure 1: > > Please remove blank line under L0, L1 etc. row in the figure. > > Section 5.1, "maxptime" bullet > > OLD: > > maxptime: See RFC 2327 [5] for its definition. The maxptime > SHOULD be a multiple of the duration of a single codec data > frame (5 ms). > > NEW: > maxptime: See RFC 3267 [8] for its definition. The maxptime > SHOULD be a multiple of the duration of a single codec data > frame (5 ms). > > Section 10.1: > One new normative reference: > > NEW: > [8] Sjoberg, J., Westerlund, M., Lakaniemi, A., and Q. Xie, > "Real-Time Transport Protocol (RTP) Payload Format and File > Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive > Multi-Rate Wideband (AMR-WB) Audio Codecs", RFC 3267, June 2002. > > Section 7: First paragraph > OLD: > RTP packets using the payload format defined in this specification > are subject to the security considerations discussed in the RTP > specification [1] and any appropriate profile (for example, [7]). > This implies that confidentiality of the media streams is achieved > by encryption. Because the data compression used with this payload > format is applied end-to-end, encryption may be performed after > compression so there is no conflict between the two operations. > > NEW: > RTP packets using the payload format defined in this specification > are subject to the security considerations discussed in the RTP > specification [1] and any appropriate profile (for example, [7]). > This implies that confidentiality of the media streams is achieved > by encryption. > > Removal of the last sentence! > > Section: 9 > OLD: > > The authors would like to thank Magnus Westerlung, Colin Perkins, > Allison Mankin, and Jean-Francois Mule for their review of this > document. > > NEW > The authors would like to thank Magnus Westerlund, Colin Perkins, > > ^ > Allison Mankin, and Jean-Francois Mule for their review of this > document. > > > _______________________________________________ > Audio/Video Transport Working Group > avt@ietf.org > https://www1.ietf.org/mailman/listinfo/avt > _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Protocol Action: 'RTP Payload Format for Br… The IESG
- Re: [AVT] Protocol Action: 'RTP Payload Format fo… Mike
- RE: [AVT] Protocol Action: 'RTP Payload Format fo… Raymond (Juin-Hwey) Chen