Re: [payload] WGLC for draft-ietf-payload-rtp-ancillary-08

John Fletcher <John.Fletcher@bbc.co.uk> Thu, 20 April 2017 10:22 UTC

Return-Path: <John.Fletcher@bbc.co.uk>
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 96B23129555 for <payload@ietfa.amsl.com>; Thu, 20 Apr 2017 03:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6UoE4crznmj for <payload@ietfa.amsl.com>; Thu, 20 Apr 2017 03:22:51 -0700 (PDT)
Received: from mailout1.cwwtf.bbc.co.uk (mailout1.cwwtf.bbc.co.uk [132.185.160.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5B6C1294B3 for <payload@ietf.org>; Thu, 20 Apr 2017 03:22:50 -0700 (PDT)
Received: from BGB01XI1002.national.core.bbc.co.uk ([10.184.50.52]) by mailout1.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id v3KAMmcY007559; Thu, 20 Apr 2017 11:22:48 +0100 (BST)
Received: from BGB01XUD1011.national.core.bbc.co.uk ([10.161.14.9]) by BGB01XI1002.national.core.bbc.co.uk ([10.184.50.52]) with mapi id 14.03.0319.002; Thu, 20 Apr 2017 11:22:48 +0100
From: John Fletcher <John.Fletcher@bbc.co.uk>
To: "Ali C. Begen" <ali.begen@networked.media>, "payload@ietf.org" <payload@ietf.org>
Thread-Topic: [payload] WGLC for draft-ietf-payload-rtp-ancillary-08
Thread-Index: AQHSrVK4tLxZKOBdQEqw2cWzz9Q2fKHOEj1H
Date: Thu, 20 Apr 2017 10:22:47 +0000
Message-ID: <B1D49063AD5FBD4688F3EEDEC68B2017C380A3D9@bgb01xud1011>
References: <CAA4Mczu95KgfV+uWgcEvnqHUYGDOptF7_yfD950Z7SZZ+YNuxg@mail.gmail.com>
In-Reply-To: <CAA4Mczu95KgfV+uWgcEvnqHUYGDOptF7_yfD950Z7SZZ+YNuxg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.212]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-11.0.0.4179-8.100.1062-23018.006
x-tm-as-result: No--14.750500-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_B1D49063AD5FBD4688F3EEDEC68B2017C380A3D9bgb01xud1011_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/-O1HG9oBa0TLy9xWv0wmhZiN1v4>
Subject: Re: [payload] WGLC for draft-ietf-payload-rtp-ancillary-08
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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 Apr 2017 10:22:52 -0000

Apologies for slightly late comments but ...

In section 2.1, definition of "C" bit, HD signals are mentioned but not UHD.  I think the definition really depends on whether the SDI interface uses separate data channels for luma and color-diff, so perhaps the specification could be re-worded along those lines.  At the very least, say "HD and UHD signals".

Specifications about RTP timestamp clock rate appear in section 3.1 as part of the media format parameters but I think these should be in section 2 as part of the timestamp definition.  Section 3.1 should just say that the Rate parameter is required.

Section 1, Introduction, uses normative word "should" in "It should be noted that".  I suggest changing to "Note that".

In section 3.1, the normative word "may" is used in "implementers may care" and "may not care".  It's not appropriate to give implementers permission or to forbid them from caring.  I suggest changing to "might".

In section 3.1, "those that must interoperate with", I suggest deleting "must".

In section 4, "the ancillary data stream may potentially contain", suggest changing to "might" to indicate possibility rather than permission.

In section 4.1, the normative word "may" is used in "implementers may wish to".  It's not appropriate to give implementers permission to wish.  I suggest deleting "to wish".

In section 5, again we have "may with", I think meant to be "may wish".  I suggest changing to "might wish" in this case.  Other uses of "may" in this section seem fine but should be capitalised.

In section 7, "It may still be a good idea", suggest changing "may" to "might".

In section 7, "receivers should take care to", I suggest deleting "take care to".

Some uses of "required" in the memo are not specifying normative requirements, suggest re-wording or changing to "needed".

Several occurrences of "may", "must", "should", "required" and "optional" are not capitalised.

Regards,
John

________________________________
From: payload [payload-bounces@ietf.org] on behalf of Ali C. Begen [ali.begen@networked.media]
Sent: 04 April 2017 15:49
To: payload@ietf.org
Subject: [payload] WGLC for draft-ietf-payload-rtp-ancillary-08

WG,

We will run another WGLC on this draft as there have been some significant changes since we ran the WGLC earlier.

Please have a look at the draft (at least to the diff) and send your comments to the list by April 19th.

https://datatracker.ietf.org/doc/html/draft-ietf-payload-rtp-ancillary-08

Thanks.
-acbegen (co-chair)



----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------