Opsdir telechat review of draft-ietf-iasa2-trust-update-00

Tianran Zhou <zhoutianran@huawei.com> Tue, 25 September 2018 02:37 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tianran Zhou <zhoutianran@huawei.com>
To: ops-dir@ietf.org
Cc: draft-ietf-iasa2-trust-update.all@ietf.org, iasa20@ietf.org, ietf@ietf.org
Subject: Opsdir telechat review of draft-ietf-iasa2-trust-update-00
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153784303680.31238.12996319367450332210@ietfa.amsl.com>
Date: Mon, 24 Sep 2018 19:37:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nyYN8CAGFuHTSeuXHVYreVrigU4>

Reviewer: Tianran Zhou
Review result: Has Issues

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.

Document reviewed: draft-ietf-iasa2-trust-update-00

This document is well written. I do not find any major issue from the OPS point
of view. I also read the related docuement draft-ietf-iasa2-trust-rationale-00.
I do not have strong opinion but I am curious why seperating these two
docuements.

Issues:
I think the seperation of draft-ietf-iasa2-trust-rationale-00 and
draft-ietf-iasa2-trust-update-00 makes both incomplete. I suggest to
incorporate draft-ietf-iasa2-trust-rationale-00 into
draft-ietf-iasa2-trust-update-00 as one BCP for publication. I am fine if this
is a decision from the community discussion.

Nits:
Section 2.   s/miminize/minimize/

Regards,
Tianran

Opsdir telechat review of draft-ietf-iasa2-trust-… Tianran Zhou