IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 23 March 2024 22:19 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 ADBE1C14F68E for <ipv6@ietfa.amsl.com>; Sat, 23 Mar 2024 15:19:47 -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=unavailable 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 gPV8o2p7FYQU for <ipv6@ietfa.amsl.com>; Sat, 23 Mar 2024 15:19:42 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 C6F64C14F6A5 for <ipv6@ietf.org>; Sat, 23 Mar 2024 15:19:42 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [103.73.84.14]) by relay.sandelman.ca (Postfix) with ESMTPS id 31F561F4A8; Sat, 23 Mar 2024 22:19:40 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="SYI0LCK/"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 70846A1913; Sun, 24 Mar 2024 08:19:37 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711232377; bh=h/quLezUKpXq/8xGtKu8ZMa6pMdQyelwRahw3WdvaRk=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=SYI0LCK/ETmPLU+WtEosgeqECdIcjT+cbPPH3K1yXGbV/WM5eijaA7RGB1gTkuXJa uW6RmImTv0IMsbFkxKuFGoRuc3kyVHF/eRQ8/COMa9tfK6mSFHXWekFBS5j9yqG+uX WEyxP/b/l6Loduw4Rh3rX+A4MaGUyeFhlwK3P+a9MTZz3BqSxL1AntyqJSQlOubcEf UpVnqAFIrZAYsKDf+r22ESbAgLwKgnC/cxzCF6RVwk7Yq1lFr1/5t4uB+YvEZ15pu7 tKzCsR6vHc6ds285ufdyN4D2OS4PxjA51ak9kHH/FXnkx0wEQWHFE4ApMsVbFrUC/9 VYXm0nJf15n9Q==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 6E379A0012; Sun, 24 Mar 2024 08:19:37 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ole Troan <otroan=40employees.org@dmarc.ietf.org>
cc: Mark Smith <markzzzsmith@gmail.com>, 6man WG <ipv6@ietf.org>
In-reply-to: <F784AA41-36FB-4ACC-BCA8-982A3469DEC6@employees.org>
References: <CAPt1N1mOyG2jrLcK3Gc47_i-XkbVPY=GweTMWNKOK7O00BpaFg@mail.gmail.com> <04BB59E2-D7DD-4409-A5AB-17321FA8E061@employees.org> <CAO42Z2yqemkhJx3Kpdx0_tg4f07XV6auJo5X8LOy93fQNK0A8w@mail.gmail.com> <F784AA41-36FB-4ACC-BCA8-982A3469DEC6@employees.org>
Comments: In-reply-to Ole Troan <otroan=40employees.org@dmarc.ietf.org> message dated "Sat, 23 Mar 2024 07:21:51 +0100."
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: Sun, 24 Mar 2024 08:19:37 +1000
Message-ID: <317567.1711232377@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1QYEltXaikXJ2uPLn-1pAkmK6VY>
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: Sat, 23 Mar 2024 22:19:47 -0000

Ole Troan <otroan=40employees.org@dmarc.ietf.org> wrote:
    > Yes, that one is interesting to explore.
    > We have a wireguard implementation in VPP, pretty sure that doesn’t
    > deal with all these intricacies out of the box at least.

    > Am I the only one who see the irony of the application taking advantage
    > of IPv6 end-to-end only to use it to build an even more end to end
    > transparent overlay? :-)

There is no irony.  The future is here, it's transparent.  It's not just
evenly dristributed yet, which is why people are willing to pay extra (even
if it's in the form of effort) to get that.

The fact that there is value in the transparent overlay.





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

v2.23.0 | Report a Bug | By Email