[IPv6]Mohamed Boucadair's Discuss on draft-ietf-6man-addr-assign-02: (with DISCUSS and COMMENT)

Mohamed Boucadair via Datatracker <noreply@ietf.org> Mon, 24 March 2025 15:31 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from [10.244.8.216] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 4C6AA119C991; Mon, 24 Mar 2025 08:31:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mohamed Boucadair via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174283031314.1620549.3112467496693348745@dt-datatracker-5b9b68c5b6-zxk6z>
Date: Mon, 24 Mar 2025 08:31:53 -0700
Message-ID-Hash: TTAFNWOM2RJALW2A6NPEBHW5SGEK2Y7H
X-Message-ID-Hash: TTAFNWOM2RJALW2A6NPEBHW5SGEK2Y7H
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-addr-assign@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org, bob.hinden@gmail.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Mohamed Boucadair <mohamed.boucadair@orange.com>
Subject: [IPv6]Mohamed Boucadair's Discuss on draft-ietf-6man-addr-assign-02: (with DISCUSS and COMMENT)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vWqiq6eE6zzJH8gaYcrs454B5XM>
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>

Mohamed Boucadair has entered the following ballot position for
draft-ietf-6man-addr-assign-02: Discuss

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-addr-assign/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Hi Brian, Suresh, and David,

Thank you for writing this document.

Also, thanks to Giuseppe Fioccola (opsdir) for flagging that the “current IANA
review state is Not OK” and to the authors for the follow-up.

I will be balloting “Yes” but I’m holding a DISCUSS to zoom into the name
inconsistency issue.

# Rename (or not) the “Internet Protocol Version 6 Address Space” IANA registry

After reading the appendix (which wasn’t actually introduced early in the
document), I think that we need to adopt a consistent approach: either we add a
new IANA action to update the name or use the name as currently maintained by
IANA when referring to the registry (and remove the appendix).

The main body of the document uses a mix of “Internet Protocol Version 6
Address Space” (Section 5) vs. “IPv6 Address Space” (abstract, Section 1).

I don’t think this is critical per se but better to be consistent here.


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

# Introduction

## Avoid text that won’t age well: currently, recently, is currently, etc.
## s/regional address registries/Regional Internet Registries (RIRs)
## Consider the following:

OLD:
   is currently shown as "IESG approval", whereas for major allocations

NEW:
   was shown as "IESG approval" till the publication of this document, whereas for major allocations

## s/RFC 1881/[RFC1881]: Cite as reference. Idem for similar occurrences in the document.

# Section 2

(1) Cite the IANA registry:

OLD: Portions of the IPv6 address space are shown in the registry
NEW: Portions of the IPv6 address space are shown in the registry [IANA1]

(2) “recent” won’t age well. Consider the following change:

OLD:
   It may be noted that the recent allocation for [RFC9602], which was
   processed as a working group document, did indeed follow the more
   stringent "IETF Review" process proposed by this document.

NEW:
   The new stringent "IETF Review" process was followed for the
   allocation requested in [RFC9602], which was processed as a working
   group document.

Thank you.

Cheers,
Med