[Idr] Benjamin Kaduk's Yes on draft-ietf-idr-rfc8203bis-07: (with COMMENT)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Fri, 02 October 2020 22:43 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A9D3A1713; Fri, 2 Oct 2020 15:43:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-idr-rfc8203bis@ietf.org, idr-chairs@ietf.org, idr@ietf.org, Susan Hares <shares@ndzh.com>, shares@ndzh.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.18.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <160167858667.12038.11954901865232213251@ietfa.amsl.com>
Date: Fri, 02 Oct 2020 15:43:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/z09GbnTRFqQ6sTVGIvJY1Y7QPAk>
Subject: [Idr] Benjamin Kaduk's Yes on draft-ietf-idr-rfc8203bis-07: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2020 22:43:07 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-idr-rfc8203bis-07: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


Thank you for this clear and well-written document.  Just a couple minor comments;
no reply necessary.

Section 4

   If a Shutdown Communication with an invalid UTF-8 sequence is
   received, a message indicating this event SHOULD be logged for the

Could we say "invalid or non-shortest-form-encoded UTF-8 sequence"?
I had started a comment on section 2 about the error handling, but then
I saw that there was already an error handling section!

Section 7.2

Some die-hards might argue that the "SHOULD include methods such as
syslog" promotes RFC 5424 to a normative reference, but I won't make a
big deal about it.