From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp08.mail.tnz.yahoo.co.jp ([203.216.226.136]:20886 "HELO smtp08.mail.tnz.yahoo.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S933310AbZHEC7F (ORCPT ); Tue, 4 Aug 2009 22:59:05 -0400 Message-ID: <4A78F3E6.2090708@yahoo.co.jp> Date: Wed, 05 Aug 2009 11:52:22 +0900 From: Akihiro TSUKADA MIME-Version: 1.0 To: Patrick Boettcher CC: Linux Media Mailing List , olgrenie@dibcom.fr Subject: Re: RFC: adding ISDB-T/ISDB-Tsb to DVB-API 5 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Hi Patrick, Thank you for your effort to add support for ISDB-T/S. I've skimmed through the ARIB standard before, but it is too complicated for me to understand well enough. So this is not a comment for the API extension itself, but for the document part. Some of the parameters are currently (and probably will stay) fixed or not used according to the "operational guidelines". For example, DQPSK is not used at all (if I read correctly). These guidelines are defined in ARIB TR-B14 for ISDB-T and in ARIB TR-B15 for ISDB-S respectively. So, including these two TRs (in additino to ARIB STD-B31) as a reference in the document may help readers. --------- Akihiro TSUKADA -------------------------------------- Power up the Internet with Yahoo! Toolbar. http://pr.mail.yahoo.co.jp/toolbar/