Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-atrac-family-11.txt

actech <actech@jp.sony.com> Fri, 11 January 2008 11:57 UTC

Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDIWF-00024a-F7; Fri, 11 Jan 2008 06:57:51 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDIWE-00024T-Hc for avt@ietf.org; Fri, 11 Jan 2008 06:57:50 -0500
Received: from mgw3.sony.co.jp ([137.153.0.15]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDIWD-0005Eu-JA for avt@ietf.org; Fri, 11 Jan 2008 06:57:50 -0500
Received: from mail7.sony.co.jp ([43.0.1.209])
Received: from mail7.sony.co.jp (localhost [127.0.0.1]) by mail7.sony.co.jp (R8/Sony) with ESMTP id m0BBvl3N013432 for <avt@ietf.org>; Fri, 11 Jan 2008 20:57:47 +0900 (JST)
Received: from jptkyxim01.jp.sony.com (jptkyxim01.jp.sony.com [43.15.17.87]) by mail7.sony.co.jp (R8/Sony) with ESMTP id m0BBvlCB013426 for <avt@ietf.org>; Fri, 11 Jan 2008 20:57:47 +0900 (JST)
Received: from jptkyxwa04.jp.sony.com ([43.15.31.4]) by jptkyxim01.jp.sony.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 11 Jan 2008 20:57:47 +0900
Received: from [43.4.150.113] ([43.4.150.113]) by jptkyxwa04.jp.sony.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 11 Jan 2008 20:57:46 +0900
Message-ID: <478759A4.7020204@jp.sony.com>
Date: Fri, 11 Jan 2008 20:57:24 +0900
From: actech <actech@jp.sony.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-atrac-family-11.txt
References: <5.1.1.11.2.20071219113010.00d506d0@pop.jp.sony.com> <A535803D-3B71-449E-8786-BA0D60D965D9@csperkins.org>
In-Reply-To: <A535803D-3B71-449E-8786-BA0D60D965D9@csperkins.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Jan 2008 11:57:46.0745 (UTC) FILETIME=[2E600690:01C85449]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: avt@ietf.org
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>
Errors-To: avt-bounces@ietf.org

Dear Mr.Perkins,

Thank you very much for your comments and advice on our 11th draft.

>> We used the terminology of "frame" for "unit of audio encoding".  
>> But we agree that the meaning of "packet" and "frame" are confused  
>> and ambigious in the section, so we changed the description here in  
>> order to clarify the meaning and the usage of "frame" and "packet".
>>     
>
> This is much better now, except for the Continuous Flag. In this case  
> it is not the packets that are fragmented, but the frame which is  
> fragmented across a series of packets. 

OK, we would like to change the description of Continuous Flag, as follows.

---
Continuous Flag (C) : 1bit

The packet which corresponds to the last part of the audio frame data
in a fragmentaion, SHALL have this bit to 0, otherwise set to 1.
---

> Finally, reference 12 probably needs to be a normative reference now,  
> since it's required to signal the layered coding.  

Reference 12 (draft-chierl-mmusic-layered-codec-04.txt) is not RFC but the
internet draft. Is it OK to put the internet draft as normative 
reference, or
do we need to put some remarks in our draft?

Regarding on other issue, we will change the draft accoding to your 
comment,
and submit the next version of the draft shortly.

Best Regards,

-------------------
Mitsuyuki Hatanaka
Jun Matsumoto

Sony Corporation

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt