[ippm] Paul Wouters' No Objection on draft-ietf-ippm-ioam-conf-state-07: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Tue, 25 October 2022 23:53 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ippm@ietf.org
Delivered-To: ippm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0476CC1522C2; Tue, 25 Oct 2022 16:53:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-ippm-ioam-conf-state@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, marcus.ihlar@ericsson.com, marcus.ihlar@ericsson.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Paul Wouters <paul.wouters@aiven.io>
Message-ID: <166674201201.46707.18104187165072867740@ietfa.amsl.com>
Date: Tue, 25 Oct 2022 16:53:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/ZATXO3xUHWmH2MsLob2Woicw2dI>
Subject: [ippm] Paul Wouters' No Objection on draft-ietf-ippm-ioam-conf-state-07: (with COMMENT)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2022 23:53:32 -0000

Paul Wouters has entered the following ballot position for
draft-ietf-ippm-ioam-conf-state-07: 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:
https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-conf-state/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks to Chris Lonvick for the SecDir review. He raised a few points that are
worth addressing:
https://datatracker.ietf.org/doc/review-ietf-ippm-ioam-conf-state-05-secdir-lc-lonvick-2022-09-30/

   Reserved field is reserved for future use and MUST be set to zero.

Can this be extended to say "and MUST be ignored when non-zero" ? There is more
than one of these.

Why is the SoP field specified as two bits from a reserved field, when it only
uses one bit? Why not just take one bit from the reserved field?