[Taps] Murray Kucherawy's No Objection on draft-ietf-taps-interface-26: (with COMMENT)

Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 18 April 2024 13:56 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C79CC14F68D; Thu, 18 Apr 2024 06:56:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-taps-interface@ietf.org, taps-chairs@ietf.org, taps@ietf.org, anna.brunstrom@kau.se
X-Test-IDTracker: no
X-IETF-IDTracker: 12.10.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <171344861142.13833.702471706340658291@ietfa.amsl.com>
Date: Thu, 18 Apr 2024 06:56:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/Bc9wMiCTktgrbVhIoV88Rd6QB_s>
Subject: [Taps] Murray Kucherawy's No Objection on draft-ietf-taps-interface-26: (with COMMENT)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2024 13:56:51 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-taps-interface-26: No Objection

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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.

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


Thanks to Robert Sparks for his dual ARTART reviews.

Kudos to the document shepherd who took the time to give a comprehensive
explanation as to why there are eight authors, saving us the investigation and

In Section 5, in the second bullet, the two SHOULDs seem redundant to each
other to me.

Various other SHOULDs in the document (Sections 6, 8, and 9 mainly) left me
wondering "Why?".  I think you might be using at least some of them to mean
"this is really good advice", while BCP 14 is meant more to constrain
implementations for interoperability reasons.  You might consider adding some
text to them that explains why they're short of a MUST, or just make them fully