Re: [payload] [Payload] Last Call: <draft-ietf-payload-rfc3189bis-02.txt> (RTP Payload Format for DV (IEC 61834) Video)) to Proposed Standard
Kazuhiro Mishima <three@sfc.wide.ad.jp> Thu, 20 October 2011 07:55 UTC
Return-Path: <kaz.mishima@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 564B921F8BA4; Thu, 20 Oct 2011 00:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.077
X-Spam-Level:
X-Spam-Status: No, score=-0.077 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_14=0.6, MANGLED_GOOD=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s60vtc-QqVrZ; Thu, 20 Oct 2011 00:55:01 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 68CE921F8BA0; Thu, 20 Oct 2011 00:55:01 -0700 (PDT)
Received: by ggnv1 with SMTP id v1so3021861ggn.31 for <multiple recipients>; Thu, 20 Oct 2011 00:55:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5NiKXAnbS2IAkI2vEpyG0lJmeyn3UVTX8jhiB5ecvkA=; b=QSdO1iVqxtY2AVM0Rv0Z+yN81DZh3sjED+E+Md7XzX+haIQyJlNixk5Fslqm8zs6zc WI+/six9UX9kH1fW9Z8RfUnYFD9NPx+eJD9wLyFZyCKXMhDet5AoeQqBnpCJEZjuR+EF DxZ2FnesAOz2p1bs7r1JzWvZohYnGuB+QpfeQ=
MIME-Version: 1.0
Received: by 10.236.187.36 with SMTP id x24mr13888507yhm.74.1319097300950; Thu, 20 Oct 2011 00:55:00 -0700 (PDT)
Sender: kaz.mishima@gmail.com
Received: by 10.147.169.2 with HTTP; Thu, 20 Oct 2011 00:55:00 -0700 (PDT)
In-Reply-To: <086901cc7c7d$8fa14990$aee3dcb0$%roni@huawei.com>
References: <17D448F688A3446180420DCC3AE3F66A@china.huawei.com> <086901cc7c7d$8fa14990$aee3dcb0$%roni@huawei.com>
Date: Thu, 20 Oct 2011 16:55:00 +0900
X-Google-Sender-Auth: YxHufTdzcXWmRXTXOa6l8PJufM0
Message-ID: <CAE61ZqRh8G615Mk-ziaPrqq5n3b3+jw1pE7WbbCW8C=yYkFzRA@mail.gmail.com>
From: Kazuhiro Mishima <three@sfc.wide.ad.jp>
To: Roni Even <Even.roni@huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: ikob@riken.jp, Stephen Casner <casner@acm.org>, payload@ietf.org, ietf@ietf.org
Subject: Re: [payload] [Payload] Last Call: <draft-ietf-payload-rfc3189bis-02.txt> (RTP Payload Format for DV (IEC 61834) Video)) to Proposed Standard
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, 20 Oct 2011 07:55:02 -0000
Hi Qin, Roni, Thank you for comments. I've just updated our draft as draft-ietf-payload-rfc3189bis-03. See comments in-line please. > 1. Section 1: > > [Qin]: It looks this version extends RFC3189 to support some new features. > However I can not see any dependency to RFC3189 in the introduction section > until > I read the last section in this document, is it more straigtforward and > clear to merge the section 7,8 > to the introduction section and clarify how this document is different from > RFC3189. > > Roni: This document does not extend but obsolete RFC3189, so it should not > reference it. As for the difference from RFC3189 I think it is better to > have a separate section. Now, I keep the section by Roni's comment. > 2. Section 3.1.1 > > [Qin]: In section 7, you claim you have removed SMPTE 306M, since it is > covered by SMPTE 314M format. > However in section 3.1.2, the value for SMPTE 306M is still kept in the > encode list. So the question is > where do you remove SMPTE 306M in this document? Why SMPTE 306M in the media > type registration is still kept? > Does this conflict with what you said in the section 7? > > Roni: Maybe change the first bullet of section 7 > > " Removed SMPTE 306M, since it is covered by SMPTE 314M format" > > To > > "support for SMPTE 306M is only for backward interoperability, since it is > covered by SMPTE 314M format" I changed the sentence in 1st bullet of sec.7. > 3. Section 3.1.1 > > [Qin]: Is it real that there is no interoperability consideration since > Interoperability with Previous Implementations is discussed in the section 8 > of this document? > > Roni: Go od, add of this RFC I added the "Interoperability Consideration" which refers to sec.8. > 4. Section 3.2.1 > > [Qin]: I believe it is not appropriate to spell this note out when this > document is published but you may put > it as errata or in the section 7. > > Roni: good point. Maybe discuss it in section 8, since this may be an > interoperability issue This discussion moved to sec.8. > Also not that the syntax " < > span lan > 0pt;font-family:"Courier New"'>a=fmtp:<payload type> encode=<DV-video > encoding> audio=<audio > > bundled>" > > Does not have ";" before the audio while the examples have, I think that ";" > should separate between the parameters. I fixed the syntax. > 5. Section 3.2.1 > > Roni: I do not see this as a major issue. It can stay from my point of view. > > 6. Section 3.2.1 > > [Qin]: s/ a format specifc parameter/ a format of specific parameter > > Roni: the current text is OK > > 7. Section 3.2.1 > > [Qin] s/one of the following/one of the following value. > One question is: > How do you distinguish between required parameter or optional parameter in > the a=fmtp line? > > 8. Section 3.2.2 > > [Qin]: When you are talking about encode, you are using "encoding > type","DV-video encoding", "type of DV format" in the section 3.2, > and using "encode type" in section 3.2.2, should they be the same thing? why > not use the same terminology for consistency? > > Roni: The only issue I see is in > > "The required parameter <DV-video encoding>" which should be "The required > parameter "encode"" I changed it. > 9. Section 3.2.2" > > [Qin]: Does it worth a exmaple to expain how SDP Grouping Framework can be > used to correlate audio with video data in the section 3.3.1? > > Roni: I think that there is example in RFC 5888, so I will leave it to the > authors. I mentioned about this example. > 10. Section 3.3.1 > > [Qin]: What do you mean "when this is done"? It is not clear to me from the > context. > > Roni: to me it looks like if what is said in the previous sentence. I changed it as more clearly.
- Re: [payload] [Payload] Last Call: <draft-ietf-pa… Qin Wu
- Re: [payload] [Payload] Last Call: <draft-ietf-pa… Roni Even
- Re: [payload] [Payload] Last Call: <draft-ietf-pa… Qin Wu
- Re: [payload] [Payload] Last Call: <draft-ietf-pa… Kazuhiro Mishima
- Re: [payload] [Payload] Last Call: <draft-ietf-pa… Kazuhiro Mishima