IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 27 March 2024 07:29 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 91C76C14F5FB for <ipv6@ietfa.amsl.com>; Wed, 27 Mar 2024 00:29:17 -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 KchZE9YAVDsw for <ipv6@ietfa.amsl.com>; Wed, 27 Mar 2024 00:29:13 -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 6AFBCC14F71F for <ipv6@ietf.org>; Wed, 27 Mar 2024 00:29:13 -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 BD6841F448; Wed, 27 Mar 2024 07:29:11 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="OAzq/lMz"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 4B1CEA1914; Wed, 27 Mar 2024 18:29:07 +1100 (AEDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711524547; bh=N0JbqSaQeUI/RhOmYo4WZcVAb3CbJ33IlYUBrUKiIao=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=OAzq/lMzGeQV95dMXA7QEve5ExSluMlKaUSugu+ONLiyLTduzWQQZo6VwsjUNzpCX Xp4dZVTJtWTXbs1F66+oI0uV8dXyi9lEG25+UGj/ruAivr3lRa/QOynan0xTpywWL9 HVY9e8M3g6ud6RMuoWN8HMeN1ujEw+J2SoYj5eOXhJ0vsY8MjlFmQ0pWGxHMthu7pT 32V3YexBL6njoe/c3YGSCM87szquhNI7zeX0Hqlm8JhdJcocLo8TYBrhU4n4lL19z9 7fZsG1Qrh3HBbP2rQHjcH26wH9YWD/hJUlKDxjvzFFQTDo8nuvAkgT599+AY7lmQ/r WjtmEiNifxmbA==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 48F1CA190E; Wed, 27 Mar 2024 18:29:07 +1100 (AEDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
cc: 6man WG <ipv6@ietf.org>, =?UTF-8?Q?Ole_Tr=C3=B8an?= <otroan@employees.org>, Naoki Matsuhira <matsuhira.ietf@gmail.com>
In-reply-to: <CAPt1N1=8B17ab6-54_L8u5KK1Px5AJ9j8VmTWec0Hp3Dg1OKKQ@mail.gmail.com>
References: <CADmxuPF1AReQCSY13HjqXE+8Jofy_uoo1wmnzs8+whG7Tdc+UQ@mail.gmail.com> <836E3A12-FAAF-4C19-91A1-322203645AAA@employees.org> <CADmxuPEBXYeTPrJqfPEGaxmUM75iKQx6kfCcpHHjxyekZy0xuQ@mail.gmail.com> <492484.1711516392@dyas> <CAPt1N1=8B17ab6-54_L8u5KK1Px5AJ9j8VmTWec0Hp3Dg1OKKQ@mail.gmail.com>
Comments: In-reply-to Ted Lemon <mellon@fugue.com> message dated "Wed, 27 Mar 2024 01:19:10 -0400."
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 18:29:07 +1100
Message-ID: <498159.1711524547@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/-V2rRxbQu-RH0jEkC2RbGaPbsOg>
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 07:29:17 -0000

Ted Lemon <mellon@fugue.com> wrote:
    > Are you aware of ISPs that are contemplating single-address-to-the-home or
    > charge-per-device? Or is this just speculation based on remembered
    > trauma?

For IPv6?  I'm unware of any ISPs in Canada that know they are providing
IPv6, even among those that in fact, are.  They don't have commodity NPTv6
solutions out there for them to even begin to comtemplate thinking about it.

For IPv4?  it occurs regularly today, and I have recent quotes for upgrades
that propose fees.



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

v2.23.0 | Report a Bug | By Email