Re: [payload] WGLC on draft-ietf-avt-rtp-isac-02
Harald Alvestrand <harald@alvestrand.no> Thu, 03 January 2013 15:41 UTC
Return-Path: <harald@alvestrand.no>
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 7D06321F868B for <payload@ietfa.amsl.com>; Thu, 3 Jan 2013 07:41:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.195
X-Spam-Level:
X-Spam-Status: No, score=-110.195 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_HI=-8, 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 ABR54Sj9e7V1 for <payload@ietfa.amsl.com>; Thu, 3 Jan 2013 07:41:23 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 3306821F8C9D for <payload@ietf.org>; Thu, 3 Jan 2013 07:41:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3178339E176 for <payload@ietf.org>; Thu, 3 Jan 2013 16:41:10 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b7rE5TAWi6sO for <payload@ietf.org>; Thu, 3 Jan 2013 16:41:07 +0100 (CET)
Received: from [IPv6:2001:470:de0a:27:29c0:ec01:f309:1358] (unknown [IPv6:2001:470:de0a:27:29c0:ec01:f309:1358]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id C823F39E0CE for <payload@ietf.org>; Thu, 3 Jan 2013 16:41:06 +0100 (CET)
Message-ID: <50E5A692.6040500@alvestrand.no>
Date: Thu, 03 Jan 2013 16:41:06 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: payload@ietf.org
References: <01dd01cde366$6be0b3f0$43a21bd0$@gmail.com>
In-Reply-To: <01dd01cde366$6be0b3f0$43a21bd0$@gmail.com>
Content-Type: multipart/alternative; boundary="------------090108020303090000060407"
Subject: Re: [payload] WGLC on draft-ietf-avt-rtp-isac-02
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: Thu, 03 Jan 2013 15:41:26 -0000
We'll get you an updated draft addressing these ASAP (but it's not the most urgent thing, so it may take some days). On 12/26/2012 01:42 PM, Roni Even wrote: > > Hi, > > I reviewed the draft and have some questions and comments > > 1.In section 2 there is a mention of target bit rate. It is not clear > how is it calculated and what does average during peaks mean? How is > this parameter related to the ibitrate parameter defined in the IANA > section. > > 2.In section 2 "The available bandwidth is continuously estimated at > the receiving iSAC and signaled in-band in the iSAC bit stream". How > does it work? > I'm not sure that needs to be specified in the payload format document. There are a number of things that are not specified; those who want that information can go check out the source. > 3.In section 3 second paragraph please discuss using dynamic payload > type number maybe add "The assignment of an RTP payload type for the > format defined in this memo is outside the scope of this document. > The RTP profiles in use currently mandate binding the payload type > dynamically for this payload format." > Nice to be explicit. I thought this was what we assumed by default. > > 4.In section 3.2 what are the BEI and FL values and how many bits > each one uses. > > 5.In section 3.3 what is bandwidth probe, how does it work. Is it > specified elsewhere, in which case provide a reference. > > 6.In section 3.3 "The user can choose to lower the maximum allowed > payload length ". Who is the user(sender / receiver) and how is it done. > > 7.In section 3.4 how does a receiver know if he receives a wideband or > super-wideband payload in order to decode correctly. > > 8.In section 3.5 "signaled inband". What is inband, any reference? > > 9.Looking at figure 6 I am not clear from the text how does the > receiver know that there is padding and not payload? > The decoding process will decode until it's decoded all the samples it wants. What follows is padding. Same process as section 3.3. > 10.In section 4 change the beginning to "This RTP payload format is > identified using the media type audio/isac, which is registered in > accordance with [RFC4855 <http://tools.ietf.org/html/rfc4855>] and > uses the template of [RFC4288 <http://tools.ietf.org/html/rfc4288>]." > > 11.Please verify that the registration follows the template. Currently > the order is not correct and there are missing subscetions. > Will fix. > > 12.Since ibitrate and maxbitrate are optional parameters what are the > default values if not specified. I saw 20000 for ibitrate for channel > adaptive mode in section 2. > These are the requests from the recipient. In their absence, the sender will send what the sender wants to send. > > 13.What are the units for ibitrate and maxbitrate > I've assumed bits per second, but I'll check. > > 14. In section 4 the change controller should be the payload working > group. > > 15.In section 5 what is the clock rate in rtpmap. > > 16.Can you switch from wideband to super wideband without any > signaling using the same payload type number. Can you use a 32000 > clock rate also for the wideband. > Section 3: 3. RTP Payload Format The iSAC codec in wideband mode uses a sampling rate clock of 16 kHz, so the RTP timestamp MUST be in units of 1/16000 of a second. In super-wideband mode, the iSAC codec uses a sampling rate clock of 32 kHz, so the RTP timestamp MUST be in units of 1/32000 of a second. Is this sufficient? > 17.The document should have a congestion control section > seehttp://tools.ietf.org/html/draft-ietf-payload-rtp-howto-02 > > 18.The security section need to be expanded see for example section 10 > of RFC 5404. > OK. > > Thanks > > Roni Even > > *From:*Roni Even [mailto:ron.even.tlv@gmail.com] > *Sent:* 13 December, 2012 8:35 AM > *To:* 'payload@ietf.org' > *Cc:* 'draft-ietf-avt-rtp-isac@tools.ietf.org' > *Subject:* WGLC on draft-ietf-avt-rtp-isac-02 > > Hi, > > I would like to start a WGLC onhttp://tools.ietf.org/html/draft-ietf-avt-rtp-isac-02 ,RTP Payload Format for the iSAC Codec > > > > The WGLC will end on January 2nd, 2013 > > Please review the draft and send comments to the list. > > For the draft authors; Are you aware of any IPR that applies to > draft-ietf-avt-rtp-isac-02? If so, > > has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details)? > The above question is needed for the document write-up when sent to publication. > > > Thanks > > Roni Even > > Payload co-chair > > ------------------------------------------------------------------------ > > > _______________________________________________ > payload mailing list > payload@ietf.org > https://www.ietf.org/mailman/listinfo/payload
- [payload] WGLC on draft-ietf-avt-rtp-isac-02 Roni Even
- Re: [payload] WGLC on draft-ietf-avt-rtp-isac-02 Roni Even
- Re: [payload] WGLC on draft-ietf-avt-rtp-isac-02 Pascal Huart (phuart)
- Re: [payload] WGLC on draft-ietf-avt-rtp-isac-02 Harald Alvestrand
- Re: [payload] WGLC on draft-ietf-avt-rtp-isac-02 Roni Even