[Rift] Mike Bishop's No Objection on draft-ietf-rift-kv-tie-structure-and-processing-07: (with COMMENT)
Mike Bishop via Datatracker <noreply@ietf.org> Tue, 06 January 2026 15:43 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: rift@ietf.org
Delivered-To: rift@mail2.ietf.org
Received: from [10.244.9.115] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 643E0A37CBED; Tue, 6 Jan 2026 07:43:55 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Mike Bishop via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.55.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176771423532.3565126.16321396798278844042@dt-datatracker-5656579b89-p6k4r>
Date: Tue, 06 Jan 2026 07:43:55 -0800
Message-ID-Hash: DCIZABLCKVBF6FCTHUIGE6C26SGWXHOO
X-Message-ID-Hash: DCIZABLCKVBF6FCTHUIGE6C26SGWXHOO
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rift.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: christian@kuhtz.com, draft-ietf-rift-kv-tie-structure-and-processing@ietf.org, rift-chairs@ietf.org, rift@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Mike Bishop <mbishop@evequefou.be>
Subject: [Rift] Mike Bishop's No Objection on draft-ietf-rift-kv-tie-structure-and-processing-07: (with COMMENT)
List-Id: Discussion of Routing in Fat Trees <rift.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/jZPtQDceviZBeSfMexu2vsPMn74>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rift>
List-Help: <mailto:rift-request@ietf.org?subject=help>
List-Owner: <mailto:rift-owner@ietf.org>
List-Post: <mailto:rift@ietf.org>
List-Subscribe: <mailto:rift-join@ietf.org>
List-Unsubscribe: <mailto:rift-leave@ietf.org>
Mike Bishop has entered the following ballot position for draft-ietf-rift-kv-tie-structure-and-processing-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-rift-kv-tie-structure-and-processing/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for addressing my previous DISCUSS and COMMENT points. I'll retain this non-blocking comment: In Section 2.1 and 2.2, there's no need for the 2119 language (MUST/OPTIONAL) for describing "support of" the Sub-Identifier. Rather, by definition, when Key Type is Well-Known or Experimental, the Key Identifier field has this additional structure. In Section 2.4, the situation is similar. Rather than "The Key Identifier MUST...", you can simply state that the semantics of the Value field (including any vendor-administered sub-typing) are defined by the vendor whose OUI is in the Key Identifier field.
- [Rift] Mike Bishop's No Objection on draft-ietf-r… Mike Bishop via Datatracker