[payload] Pos-Dir last call review for draft-ietf-payload-rtp-vc2hq-05
Nevil Brownlee <n.brownlee@auckland.ac.nz> Sat, 12 May 2018 02:55 UTC
Return-Path: <n.brownlee@auckland.ac.nz>
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 D1D0112E042; Fri, 11 May 2018 19:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
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 MZm_5vg44a1a; Fri, 11 May 2018 19:55:04 -0700 (PDT)
Received: from mx3-int.auckland.ac.nz (mx3-int.auckland.ac.nz [130.216.125.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A4CA12D7F2; Fri, 11 May 2018 19:55:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1526093704; x=1557629704; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=gnrjBHKfwv7sLki9AqU9eCTFifC4tMl17F231f7b1t0=; b=cRmEhdDJrFYyJrgEYw4r4HZ6rhapSqnvmKBsK0Sps2gd5Xx31fZE45Sb 0lJzQJdD4iReCxuRrm1DGyiFxYnHRJ4F/QvOG3CtY7xYkuYKgt5VlOTZm mVjUnH58qPuPNZ9r++65vfry6PgfPGC4a/xg11utKopdLQY3tqcg0RpJI hYB+bZLj0xatbTajBpWGmSMVKfF5hAbceW3lozjigicavWzAZYH7tqLFQ oftcAiV5TjUYXJC9SDACRrfzcYqusRfCPobVnwrnaUeTxSKZfFjNLUC1n WcpSR5kMkF1kyCsPVbdkvsSPN4P6KzYqrIpiU7g0LBhNeD7dJOy7uoSUA g==;
X-IronPort-AV: E=Sophos;i="5.49,390,1520852400"; d="scan'208";a="25811106"
X-Ironport-HAT: None - $RELAY-AUTH
X-Ironport-Source: 121.98.244.177 - Outgoing - Outgoing-SSL
Received: from dynamic-cpe-pool.orcon.net.nz (HELO [192.168.20.4]) ([121.98.244.177]) by mx3-int.auckland.ac.nz with ESMTP; 12 May 2018 14:54:59 +1200
To: "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-payload-rtp-vc2hq.all@ietf.org, payload@ietf.org
From: Nevil Brownlee <n.brownlee@auckland.ac.nz>
Message-ID: <88bea593-3697-9626-4f20-953f8f428f41@auckland.ac.nz>
Date: Sat, 12 May 2018 14:54:34 +1200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/uGSBKJ-jd7-V8VQ86v8qfImbbpU>
Subject: [payload] Pos-Dir last call review for draft-ietf-payload-rtp-vc2hq-05
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: Sat, 12 May 2018 02:55:10 -0000
Reviewer: Nevil Brownlee Review Result: Ready I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. "This memo describes an RTP Payload format for the High Quality (HQ) profile of SMPTE Standard ST 2042-1 known as VC-2. This document describes the transport of HQ Profile VC-2 in RTP packets and has applications for low-complexity, high-bandwidth streaming of both lossless and lossy compressed video." This draft simply describes in detail the way in which a stream of VC-2 information must be carried ina stream of RTP packets. It's well-written, with sufficient detail to allow for inter-operating implementations. It's Security Considerations are clear. As with all documents of this kind, operators will need to be sure that the implementations of this kind of RTP stream do conform to this draft's eventual RFC. I noticed a few slightly puzzling things: Section 4.1 Payload Type says that the PT is "A dynamically allocated payload type field that designates the payload as VC-2 coded video." Given that it's dynamically allocated, how does a VC-2 receiver know what value has been allocated for PT? Section 4.4 has two lists of acceptable Parse Code values. but those sentences end with 'and'. Should that really be 'or', indicating that any of the listed values of allowed? Cheers, Nevil -- -------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand
- [payload] Pos-Dir last call review for draft-ietf… Nevil Brownlee
- Re: [payload] Pos-Dir last call review for draft-… Roni Even