Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues

Klaus Frank <klaus.frank@posteo.de> Mon, 07 February 2022 18:54 UTC

Return-Path: <klaus.frank@posteo.de>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B4583A0B67 for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 10:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=posteo.de
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dmymty0KzIlW for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 10:54:51 -0800 (PST)
Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 443D23A0B35 for <behave@ietf.org>; Mon, 7 Feb 2022 10:54:50 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id ADB86240027 for <behave@ietf.org>; Mon, 7 Feb 2022 19:54:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644260088; bh=VKVsEWCTMMpV9lVa84tlXCPHrnChWWit7sg1h1MkcBo=; h=Date:Subject:To:From:From; b=p+W5lhkD4i37EqK0GgYHoTxIG9Mi20wOM1yd0gZX7oaApYQjZ8psrP7ZaKIwRG8EN lcrghoSGGd0vLwU5odZrYyT8tyJhjuEK4Qd2Xku/3XlfThaBN9j20ckapiVJW3aIWp 0vT8DrkhCvqDvq/QSFNrpTSMgtZJigd533nthAuUzu8o5EN5AWI2rVkNjSpEmb3J7D Q0XKVXojzVfjZgI8b+xqtfJYwjH9m8snuCqE49QS9b/Xs1h+X8j8aqSxOo1Qu/mxZz cU6mmREP+LcBxv7SewHqh1r0Ip4gQYEYRFB7v1imaN9mgBzafH+ekxIWuddZtc2TTG mPjZcPxfFbNNA==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JswLJ3F8gz6tpT for <behave@ietf.org>; Mon, 7 Feb 2022 19:54:47 +0100 (CET)
Message-ID: <54ca9cef-df6b-3643-a432-4e9cc00a1a5e@posteo.de>
Date: Mon, 07 Feb 2022 18:54:45 +0000
MIME-Version: 1.0
Content-Language: en-US
To: behave@ietf.org
References: <077D662F-5E6D-44F5-8DD3-B58D8B535C5D@network-heretics.com> <B6D6B4CC-AC1F-459C-952A-E9493E00FDB3@huitema.net> <7e53925e-46b0-29e4-6deb-47bcf389ff97@posteo.de> <3ff58733-ccd5-fe15-8b06-dd69bfad0c74@network-heretics.com> <59E4D416-0B86-46D3-BE0E-9C12881A07FD@virtualized.org> <3ae61684-10d1-dde6-222a-69f456dbe5e3@network-heretics.com> <9B8076BE-FF9F-498E-BF2C-983A4F2ACE50@virtualized.org> <59b18485-2d26-8eff-8110-e1d5c5c9412e@network-heretics.com>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <59b18485-2d26-8eff-8110-e1d5c5c9412e@network-heretics.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms070409090903030304050404"
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/No3P6xM8C6ZUhWvMXgaFQqt3FdQ>
Subject: Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2022 18:54:56 -0000

Instead of reminding people on here about how you disapprove of NATs 
your time may be better spent going after the k8s community (and others) 
and talking them out of wanting to further adoption and encourage the 
use of NAT66. We cannot change the past. But we've a change to steer the 
future and avoid repeating mistakes...

On 2022-02-07 19:10, Keith Moore wrote:
> On 2/7/22 13:06, David Conrad wrote:
>
>> I suppose I don’t find continually putting my fingers in my ears and 
>> chanting “NAT is bad” any time the topic comes up particularly 
>> productive. YMMV.
> I suppose I don't find constantly trying to find solutions to every 
> new problem that NATs cause particularly productive either, which is 
> why I occasionally remind people that that's counterproductive.
>
>> It’s not about encouraging spread. That ship sailed long, long ago. 
>> It is about accepting reality and coming up with solutions, as ad hoc 
>> as may be required, to reduce the pain that that reality entails.
>
> If NATs weren't reality, there would be no need to get rid of them.   
> But ultimately that is the only solution.
>
> Keith
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave