[Ivy] Éric Vyncke's No Objection on draft-ietf-ivy-network-inventory-yang-20: (with COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Thu, 08 October 2026 13:36 UTC
Received: by mx.ietf.org (Postfix) id 292E446; Thu, 08 Oct 2026 13:36:26 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail; t=1791466586; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=2RXX7Hi48jiqYVlXpKVaM8/jx4ezfFSAfunIk6TvU1M=; b=Li6XhokAm5d5mNzEKvwXYH5evwLN4KvahK4RiHFuJf71Rj1GPgZdRXEovA5buxrsFD1DXm nwlFSaj89tLFQ3L4Mj+0vGke3sheZFE0OWM2G31b7Sv7/RQ9s5w7Ha4HsVmD3fsOp9EZP9 T6HUgfLWrKLsrL68I5VfohaDQsKTaw4=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=noreply@ietf.org
Received: from [10.244.9.153] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id E837913A56B0D; Thu, 8 Oct 2026 06:36:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.79.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <179146658586.182384.9060337095616982182@dt-datatracker-678f7b55dd-md5qs>
Date: Thu, 08 Oct 2026 06:36:25 -0700
Message-ID-Hash: 5WDBTX6LK3GMNIHJMAJRTSSANIX32PET
X-Message-ID-Hash: 5WDBTX6LK3GMNIHJMAJRTSSANIX32PET
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-ivy-network-inventory-yang@ietf.org, haoyu.song@futurewei.com, ivy-chairs@ietf.org, ivy@ietf.org, manzoro.ietf@gmail.com
X-Mailman-Version: 3.3.10
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [Ivy] Éric Vyncke's No Objection on draft-ietf-ivy-network-inventory-yang-20: (with COMMENT)
List-Id: Network Inventory YANG Working Group <ivy.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ivy/ECilrzLBF9HYphydR49E9kjRaCA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ivy>
List-Help: <mailto:ivy-request@ietf.org?subject=help>
List-Owner: <mailto:ivy-owner@ietf.org>
List-Post: <mailto:ivy@ietf.org>
List-Subscribe: <mailto:ivy-join@ietf.org>
List-Unsubscribe: <mailto:ivy-leave@ietf.org>
Éric Vyncke has entered the following ballot position for draft-ietf-ivy-network-inventory-yang-20: 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-ivy-network-inventory-yang/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for the work done in this document (and using nice SVG graphics). Other thanks to Haoyu Song, the INT-directorate reviewer (at my request), please consider and reply to the review posted at: https://datatracker.ietf.org/doc/review-ietf-ivy-network-inventory-yang-19-intdir-telechat-song-2026-09-30/ The document seems to be only about "physical" components, not about virtual or "cloud instance" and the latter are also important, IMHO, to network operations (e.g., licensing cost, power up/down, ...). If the model is limited to physical elements, then let's be clear in the title and in the abstract. Some other comments: ### Section 2.2 Is a Wi-Fi interface to be considered as a port ? The description seems to talk mainly about physical ports.
- [Ivy] Éric Vyncke's No Objection on draft-ietf-iv… Éric Vyncke via Datatracker