Re: [IPv6] Adoption call for draft-bctb-6man-rfc6296-bis

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 26 March 2024 11:07 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9084C14CEFC for <ipv6@ietfa.amsl.com>; Tue, 26 Mar 2024 04:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxfogY0NHmAU for <ipv6@ietfa.amsl.com>; Tue, 26 Mar 2024 04:07:14 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FAFAC19330B for <ipv6@ietf.org>; Tue, 26 Mar 2024 04:06:54 -0700 (PDT)
Received: from dyas.sandelman.ca (60-240-91-174.static.tpgi.com.au [60.240.91.174]) by relay.sandelman.ca (Postfix) with ESMTPS id 45C601F448; Tue, 26 Mar 2024 11:06:52 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="mJEpBQbk"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 6D1FEA0C69; Tue, 26 Mar 2024 21:06:47 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711451207; bh=fpu91wwSqBdQ9JqPue0q5gbZsynSkG4rgUAirrkIGwg=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=mJEpBQbk9ajSU93JeVrf3bn67ms+fewmVlcBjq8d9pyAjfN53o2NXJa8nI/RQPzRC lfoWOmfj+YxDCaPMRogkCgRAaVlL2X1SHgGka2WdvwDtEmuLO0XkAR5+7K/wjOr1ti /zP2XTCIvSkUnXejJ3Gtni9HZBnkIbrjxTjn4TOyVtNnuHsk9bbtCRaCc4PBP5kVUX 65pn0qNOtbXZikn5NFtxL4TcfxPKVTwxaCvggKpClCLVlYSgXZYyewCIkMow95FuWU 0SY5synYcXQ4jrecfymtbr2lVTh4KqyCYD+vl14xKB3+C6aKZR3BBMubI5p7jtALW2 a1VamfC2WJsLw==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 6AF22A0012; Tue, 26 Mar 2024 21:06:47 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Naoki Matsuhira <matsuhira.ietf@gmail.com>
cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man WG <ipv6@ietf.org>
In-reply-to: <CADmxuPF1AReQCSY13HjqXE+8Jofy_uoo1wmnzs8+whG7Tdc+UQ@mail.gmail.com>
References: <df333346-f108-3782-0ff5-4bd85d7b49ac@gmail.com> <015F13BE-32F7-4C8B-8C86-C9153FE9C9E9@employees.org> <CAKD1Yr3dJ0EcMVPEGz-oHzNdWzJO1fE1u73Xxiw44BObuYTXbQ@mail.gmail.com> <CADmxuPExdq93HFRBpk6EeJdZsXOFQFDwB2EfVvkM++CDPb2gkg@mail.gmail.com> <CADmxuPEtbaehHwJhxfuhWzTeiZ7sHsveTrm69U2R67Swd1n0Bg@mail.gmail.com> <5ED8B6B1-991F-4D45-A3C3-C6BE20B00518@employees.org> <22452b49-227b-435c-9f2a-79bc231b00d9@gmail.com> <CADmxuPF1AReQCSY13HjqXE+8Jofy_uoo1wmnzs8+whG7Tdc+UQ@mail.gmail.com>
Comments: In-reply-to Naoki Matsuhira <matsuhira.ietf@gmail.com> message dated "Tue, 26 Mar 2024 10:59:59 +0900."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 26 Mar 2024 21:06:47 +1000
Message-ID: <441440.1711451207@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Uq_0wCVxo6Kzu_Yt_byVin05u9o>
Subject: Re: [IPv6] Adoption call for draft-bctb-6man-rfc6296-bis
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2024 11:07:18 -0000

Naoki Matsuhira <matsuhira.ietf@gmail.com> wrote:
    > I understand that there have been many discussions over the years, and I
    > think this is a very difficult issue. In the IPv4 era, there was no choice
    > with assuming exhaustion of IPv4 addresses, but in the IPv6 era, there are
    > plenty of addresses. If so, I think we should make use of our NAT
    > experience from the IPv6 era.

The rfc6296-bis document has short introduction that goes into the why.
As you say, it's not about address exhaustion.

I find that the applicability section (1.2) says a few small things and then
gets into a feature/benefit analysis rather than a "when" to use this.
I think that section 1.1 does a better job at what it sets out to do.

I've said for over ten years that it's just way too hard to get PI IPv6.
Particularly in the ARIN region.   I would be much happier with this document
and technology if SME's could easily get PI IPv6.
I don't mind if they have to NPTv6 it when their primary internet connection
dies. (It might be annoying to applications though)
It could be that many will arrange with all their ISPs to announce it, and
some will worry that we'll blow up the DFZ.  Maybe.

There have been other proposals, for instance the geographically assign IP
address scheme from Tony Hain: https://datatracker.ietf.org/doc/draft-hain-ipv6-geo-addr/
There are a number of ways to use it.  Probably never appropriate for single
occupant homes, because of privacy.  But 100 storey buildings might be okay
with it, and certainly SMEs will not have the same concerns.
But a brilliant part about it is that far from that location, the addresses
naturally aggregate.   At the time, we imagined that address to be the
primary one for connection establishment, and then SHIM6 could negotiate some
number of PA addresses.  We can't do that with SHIM6 (yet?!), but we could do
that with QUIC and/or MPTCP.

If this document is adopted and published, would you support adding a
signaling mechanism to indicate that NPTv6 is in use?


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*