IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 27 March 2024 05:13 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 A97C6C151980 for <ipv6@ietfa.amsl.com>; Tue, 26 Mar 2024 22:13:25 -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 qN8GVGQ537xO for <ipv6@ietfa.amsl.com>; Tue, 26 Mar 2024 22:13:20 -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 EBA49C151527 for <ipv6@ietf.org>; Tue, 26 Mar 2024 22:13:19 -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 B0D5C1F448; Wed, 27 Mar 2024 05:13:16 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="asXvMRD4"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 0405FA1914; Wed, 27 Mar 2024 16:13:13 +1100 (AEDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711516393; bh=Nz37B5GNSLJoVQhF2lxeZvD211/5HapQ076CIOLlYiw=; h=From:To:Subject:In-reply-to:References:Date:From; b=asXvMRD435dEgbPLbUDWDAUw41BZXC/5/Sz1t60ZcjY8xvvnJGiTPMteyAY+CXyca aDG3lYxBZG5a21kzGnKHIsHyLE2ePRsJ5qT5BfsOMLrxM5YIZFxPOJ70hI5wKyTw2Q NzCu61hADaEb3BKLBdt1ieoihyH337B7oASMvi6LHjkvFqh3hElEo0077obCBsl5kJ M0/D2MLPrsuTo4LhpxHUjmy7/hXX04xA0+msOmDUatHSNB9RsY4RJZGzc9upDKZFUC aa4oil4iSB8ZVgBh79AABFdrfwcydTULJrTNpGlnB6i1IoqMQy5XDhOCHUg23WkA9W rTFAQ01dDd9LQ==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 01C48A190E; Wed, 27 Mar 2024 16:13:13 +1100 (AEDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Naoki Matsuhira <matsuhira.ietf@gmail.com>, =?UTF-8 ?Q?Ole_Tr=C3=B8an?= <otroan@employees.org>, 6man WG <ipv6@ietf.org>
In-reply-to: <CADmxuPEBXYeTPrJqfPEGaxmUM75iKQx6kfCcpHHjxyekZy0xuQ@mail.gmail.com>
References: <CADmxuPF1AReQCSY13HjqXE+8Jofy_uoo1wmnzs8+whG7Tdc+UQ@mail.gmail.com> <836E3A12-FAAF-4C19-91A1-322203645AAA@employees.org> <CADmxuPEBXYeTPrJqfPEGaxmUM75iKQx6kfCcpHHjxyekZy0xuQ@mail.gmail.com>
Comments: In-reply-to Naoki Matsuhira <matsuhira.ietf@gmail.com> message dated "Tue, 26 Mar 2024 17:53:29 +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: Wed, 27 Mar 2024 16:13:12 +1100
Message-ID: <492484.1711516392@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/4wn2TbVTuIIsjt1GoKxIZnZxc_w>
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: Wed, 27 Mar 2024 05:13:25 -0000

Naoki Matsuhira <matsuhira.ietf@gmail.com> wrote:
    > I am not a native English speaker and this is the first time I have see the
    > word "unilaterally". If the meaning according to the English-Japanese
    > dictionary is correct, I feel that this is the reason why there are
    > opinions against adoption. How about that.

unilaterally in this context means that I can do something without someone
else's permission.

In particular, end-users have been able to "deploy" NAT44 on their
desktops/laptops in order to get their VMs or containers "online" without
permission from the (network) administrators.

At one point (1997), incumbent telco ISP thought that they would deploy PPPoE
to every single desktop in the home, charging more for each connection.
People said, "screw you" and put up a NAT44 on their own.  This became the
norm as home routers came out and people installed them ad-hoc, and then ISPs
deployed them as a matter of course.

We are risk the same price gouging behaviour in IPv6.
Yet, I support adoption of the document, although I would prefer to create a
new WG for it.


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

v2.23.0 | Report a Bug | By Email