IETF Logo Mail Archive

[v6ops] Re: Call for adoption: draft-palet-v6ops-rfc7915-bis-01 (Ends 2026-02-13)

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 23 January 2026 18:49 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: v6ops@mail2.ietf.org
Delivered-To: v6ops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5A773AC2357D for <v6ops@mail2.ietf.org>; Fri, 23 Jan 2026 10:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBK5FxuqJHJL for <v6ops@mail2.ietf.org>; Fri, 23 Jan 2026 10:49:04 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E6DDDAC23575 for <v6ops@ietf.org>; Fri, 23 Jan 2026 10:49:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6C76F18018 for <v6ops@ietf.org>; Fri, 23 Jan 2026 13:49:04 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id 6Rai0OizLuiT for <v6ops@ietf.org>; Fri, 23 Jan 2026 13:49:03 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1769194143; bh=Eo6/VJpSgMqcJnWI3QI+4hQtrxUlsKBsQs5E+1iUYPs=; h=From:To:Subject:In-Reply-To:References:Date:From; b=rF0E5ichwtycHvwFxz7FftAFQ9kpgykng6EWcZLBK+KaoAj5e1SJT8MR+I9+HXJ7i qy6lUmPCf5c4e55uzmt3Llm35/kPSPrgio1CNOBgoIG5okk2WyFRZTarSgAmQWHqCW /w6A6rONW15xrXR+iWD2HRuvPA07LZmC0xW6XLDgs7C+6tw9192vzzEyh0PD6lu/n7 XmxCZ1+NqX4htPHtB5FpAJVMTtZBa9yav/Wa1Y+JLu2QxFsxMAkiLfx0+lNyufjWQa A9ISI6dFWcZ9sVUPE8ErTUrTlrfB2oGPGXNygIJ0e1zp/c4e+tcshRPUzTtvQgHqR7 u91+XWA+RPQ7Q==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 3DDB218014 for <v6ops@ietf.org>; Fri, 23 Jan 2026 13:49:03 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3A68A17C for <v6ops@ietf.org>; Fri, 23 Jan 2026 13:49:03 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: v6ops@ietf.org
In-Reply-To: <176918237621.145871.3505135775102287722@dt-datatracker-77f8b84995-z4hzn>
References: <176918237621.145871.3505135775102287722@dt-datatracker-77f8b84995-z4hzn>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 23 Jan 2026 13:49:03 -0500
Message-ID: <18601.1769194143@obiwan.sandelman.ca>
Message-ID-Hash: RON4AJOKI43GOS4NRZXL77XUFBH5LOPL
X-Message-ID-Hash: RON4AJOKI43GOS4NRZXL77XUFBH5LOPL
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [v6ops] Re: Call for adoption: draft-palet-v6ops-rfc7915-bis-01 (Ends 2026-02-13)
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/F33jA9ZyvDpYYkN0ewR6035qczA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>

I have read draft-palet-v6ops-rfc7915-bis-01 as compared to RFC7915.
I think that a goal of this effort is to Internet Standard?

The major changes I see seem to be in section 5.2/4.2 around ICMP message
explanation.  And 4.2/3.2.
But, a lot of it just looks like bad reformatting.
Do you think you can fix that?
IGMP messages is new?

My experiences have been with Jool, and Ecdysis (a long time).
I'm a very keen user of this, particularly for making v4-only equipment
reachable in limited (v6-only) domains.

I think you could leave many of the previous authors in place.
Obviously not Fred or anyone else who does not answer.
(Ha. So, many of the changes are for ICMP Unreachable...)

But Fernando...

https://author-tools.ietf.org/iddiff?url1=rfc7915&url2=draft-palet-v6ops-rfc7915-bis-01&difftype=--html

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.38.3 | Report a Bug | By Email | System Status