[Gen-art] Genart last call review of draft-ietf-ntp-bcp-07

Robert Sparks <rjsparks@nostrum.com> Wed, 03 October 2018 19:49 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 840F1129C6A; Wed, 3 Oct 2018 12:49:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: gen-art@ietf.org
Cc: ntp@ietf.org, draft-ietf-ntp-bcp.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.85.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153859614749.8950.5050763020074263402@ietfa.amsl.com>
Date: Wed, 03 Oct 2018 12:49:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/IiNF3d-DAfBR0NFmwTZfb-Umo5g>
Subject: [Gen-art] Genart last call review of draft-ietf-ntp-bcp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2018 19:49:08 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ntp-bcp-07
Reviewer: Robert Sparks
Review Date: 2018-10-03
IETF LC End Date: 2018-10-08
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as a BCP

I don't want to start another "What is a BCP" fight, but I think this document
would serve the purpose it wants to serve just as well if it were
Informational. I don't object to proceeding as BCP though.

I found the tone a little unusual (as other reviewers have commented on) as did
one of the people who operates large systems but doesn't regularly participate
in the IETF that I asked to skim this. That said, I didn't find it's lack of
precision in places to be dangerous. If there's appetite to improve it, please
do, but I think the world would be better with this document published as is
than with no document published at all.