Re: [v6ops] Thoughts about wider operational input

Joe Maimon <jmaimon@jmaimon.com> Fri, 01 April 2022 21:36 UTC

Return-Path: <jmaimon@jmaimon.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFF563A1160 for <v6ops@ietfa.amsl.com>; Fri, 1 Apr 2022 14:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 kY4SfEtHlr5m for <v6ops@ietfa.amsl.com>; Fri, 1 Apr 2022 14:36:45 -0700 (PDT)
Received: from smtp.chl.com (bindzonemaster.ttec.chl.com [216.222.148.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 231573A0F04 for <v6ops@ietf.org>; Fri, 1 Apr 2022 14:36:25 -0700 (PDT)
Received: from [216.222.150.100] (joe.ttec.chl.com [216.222.150.100]) by smtp.chl.com (8.13.6/8.13.6) with ESMTP id 231LaNid030143; Fri, 1 Apr 2022 16:36:24 -0500
To: Simon <linux@thehobsons.co.uk>, v6ops list <v6ops@ietf.org>
References: <52661a3d-75dc-111a-3f23-09b10d7cb8d4@gmail.com> <9175dc32-45c1-e948-c20a-3bcc958b77b9@gmail.com> <YjmJQMNgnJoSInUw@Space.Net> <D75EF08F-6A41-41B2-AFB2-649CBCC1D83E@consulintel.es> <CAPt1N1nRnYUFA=yyJHx6t52yqWbmcd2Tf1H8gQuCZBd3Q3VqJw@mail.gmail.com> <7F4AEB43-4B24-4A21-AE9D-3EB512B98C46@consulintel.es> <8fac4314b8244ba6b33eea68694296d0@huawei.com> <9A13E47B-75D0-443F-9EE9-D2917ACB2D0F@consulintel.es> <CAO42Z2xUG+BXj+VQpajed9aGjH+q-HR7RX7C-T4DsTbouz7xWQ@mail.gmail.com> <F6A90BBF-7F44-403E-960A-8F756353B562@chinatelecom.cn> <B49417F7-3EFB-4A4D-9D1A-0D21574EA4F2@consulintel.es> <44B01ACA-3D5C-4618-B608-3B3479D29875@consulintel.es> <62447DCB.1010206@jmaimon.com> <7228D9A7-54A8-4BAE-9299-204C049F600B@consulintel.es> <6244BA91.3060306@jmaimon.com> <67762447-43D4-4393-851C-99370D3BF623@thehobsons.co.uk> <6246126C.1030609@jmaimon.com> <259B108A-C3DD-4460-B41A-A0028ACA9594@thehobsons.co.uk> <624759B1.8060700@jmaimon.com> <89D652EB-8920-4992-99EC-CC3C3A856D57@thehobsons.co.uk>
From: Joe Maimon <jmaimon@jmaimon.com>
Message-ID: <62477058.6020901@jmaimon.com>
Date: Fri, 01 Apr 2022 17:36:24 -0400
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
MIME-Version: 1.0
In-Reply-To: <89D652EB-8920-4992-99EC-CC3C3A856D57@thehobsons.co.uk>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mIiRuyiXG1w-GRyKsRl0TnPf0To>
Subject: Re: [v6ops] Thoughts about wider operational input
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2022 21:36:58 -0000


Simon wrote:

> Identifying endpoints in a consistent fashion is trivially easy - you use its IP address*.

Which you know because you have successful communications with it.

What you dont know is what IP address YOU have from the point of view of 
the other endpoint. And the assumption that you do requires that the 
network not change it in any way.

Which if you consider it carefully, there never was any such guarantee. 
It was just the path of least resistance.


>   It is only if the network starts mangling the address that it becomes non-trivial. “The internet” has never been "free to translate packets addressing between them for whatever reasons they want” for the simple reason that doing so breaks stuff.

But you are free to break stuff. So the network was always free to do so 
and building on the assumption that it never would turns out have been 
not the flawless design otherwise thought.

> As far as I can see, you're taking a starting point that it’s OK for “the network” to mangle packets (specifically addresses), and then using that to justify everything else. You’ve cited an RFC to support your viewpoint, but my reading of that RFC says “don’t mangle packets because it breaks things”.

Did the network every come with an explicit guarantee that the source 
address of a packet would not get changed once it left the host?

Or was that just an implicit assumption? Citation please.
>
>
> * Yes, the IP address you use needs to remain stable for the duration of the session.
>
>
> So, serious question. How do you read the RFC you cited and come to the conclusion that “the internet” has always been free to mangle addresses in any way it likes” ?
>
> Simon
>
>

I read the RFC and I see that it says if you are going to use endpoints 
identifiers you need to ensure they are consistent. And if they belong 
to other protocol layers and traverse a network you do not control, more 
than an assumption is required for that sort of reliable behavior.

Joe