[Cellar] Opsdir last call review of draft-ietf-cellar-ffv1-17

Qin Wu via Datatracker <noreply@ietf.org> Sun, 06 September 2020 08:28 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: cellar@ietf.org
Delivered-To: cellar@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C5FDD3A08AE; Sun, 6 Sep 2020 01:28:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Qin Wu via Datatracker <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: last-call@ietf.org, cellar@ietf.org, draft-ietf-cellar-ffv1.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.15.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159938093648.7188.7752393359382713628@ietfa.amsl.com>
Reply-To: Qin Wu <bill.wu@huawei.com>
Date: Sun, 06 Sep 2020 01:28:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/1HqVE4ZarLD8T7cSyYJkD-dtft4>
Subject: [Cellar] Opsdir last call review of draft-ietf-cellar-ffv1-17
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Sep 2020 08:28:57 -0000

Reviewer: Qin Wu
Review result: Ready

I have reviewed this document on behalf of the Operations and Management
Directorate. Four questions  need to be clarified: 1. why document v0,v1,v3 in
draft-ietf-cellar-ffv1 as informational and document v4 in
draft-ietf-cellar-ffv1-v4-14 as standard track? Not clear the key difference
between v04 and all other previous versions? 2. Why not specify transport, is
container sto which the ffv1 is mapped equivalent to transport? without
transport, how to provide confidentiality, integrity, and source authenticity?
3. how error_status and crc parity are used? e.g., using crc parity detect
error? can error be repaired? how? 4. Is bitstream parameters such as version,
micor-version,num_h_slices,num_v_slices sensitity information that can
disclosed? any security risk?