[dnssd] Opsdir last call review of draft-ietf-dnssd-prireq-04

Tianran Zhou via Datatracker <noreply@ietf.org> Mon, 10 February 2020 08:39 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tianran Zhou via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Tianran Zhou <zhoutianran@huawei.com>
Message-ID: <158132395239.4159.4997095650392562087@ietfa.amsl.com>
Date: Mon, 10 Feb 2020 00:39:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/Src7mmNAGGSJQ8SWUTe1L0Q-3Fk>
Subject: [dnssd] Opsdir last call review of draft-ietf-dnssd-prireq-04

Reviewer: Tianran Zhou
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.

In general, this document is clear to me. I did not see any special operational
or network management related issue. The problems and requirements are well
discussed in this informational document.

There are some obvious nits. For example, the number of the items in section
4.1 and 4.2.

[dnssd] Opsdir last call review of draft-ietf-dns… Tianran Zhou via Datatracker
Re: [dnssd] Opsdir last call review of draft-ietf… Christian Huitema