[IPv6]Gunter Van de Velde's No Objection on draft-ietf-6man-zone-ui-08: (with COMMENT)

Gunter Van de Velde via Datatracker <noreply@ietf.org> Mon, 14 April 2025 12:48 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from [10.244.8.129] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 755F61BB587A; Mon, 14 Apr 2025 05:48:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gunter Van de Velde via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.38.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174463490035.1140768.12197996362920331079@dt-datatracker-64c5c9b5f9-hz6qg>
Date: Mon, 14 Apr 2025 05:48:20 -0700
Message-ID-Hash: VFOEF2YY2KMXNK6YJO535Q7Q7JAYEEBS
X-Message-ID-Hash: VFOEF2YY2KMXNK6YJO535Q7Q7JAYEEBS
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-6man-zone-ui@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Gunter Van de Velde <gunter.van_de_velde@nokia.com>
Subject: [IPv6]Gunter Van de Velde's No Objection on draft-ietf-6man-zone-ui-08: (with COMMENT)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/YIeay7_v_HAQHdc1mENKibjrGgM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

Gunter Van de Velde has entered the following ballot position for
draft-ietf-6man-zone-ui-08: 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-6man-zone-ui/



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

# Gunter Van de Velde, RTG AD, comments for draft-ietf-6man-zone-ui-08

# The line numbers used are rendered from IETF idnits tool:
https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-6man-zone-ui-08.txt

# for your convenience, please find some non-blocking COMMENTS

# This document was an interesting read. Many thanks for composing this write-up

# The idnits tool spits up some observations

# comments
# ========

# 108   2.  Use Cases

GV> Lately i was involved with TWAMP/STAMP based unidirectional link delay
measurement for Segment Routing. In such use-case there may be need for using
IPv6 LL addresses in UIs and configs and state fields. Network using Segment
Routing and deploying flex-algo will most likely use such type of link delay
measurements. I did not see this use-case in the shortlist. Would it make sense
to mention this?

110        Some examples of use cases for entering an address that includes a
111        zone identifier into a UI are as follows:

GV> an alternative would be to explicitly mention that the list is not
exhaustive and that additional use-case examples exists, which are not directly
mentioned within the provided list.

Gunter Van de Velde
RTG Area Director