Re: Possible issue with source address selection for ULAs...

Ted Lemon <mellon@fugue.com> Wed, 08 December 2021 19:17 UTC

Return-Path: <mellon@fugue.com>
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 D0D9F3A0988 for <ipv6@ietfa.amsl.com>; Wed, 8 Dec 2021 11:17:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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=fugue-com.20210112.gappssmtp.com
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 Bi6Vqp4YTnCX for <ipv6@ietfa.amsl.com>; Wed, 8 Dec 2021 11:17:11 -0800 (PST)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30DCE3A0983 for <ipv6@ietf.org>; Wed, 8 Dec 2021 11:17:11 -0800 (PST)
Received: by mail-oi1-x229.google.com with SMTP id q25so5543356oiw.0 for <ipv6@ietf.org>; Wed, 08 Dec 2021 11:17:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jnWKlRdH04oGY8LPFdlAGmbdN0QQuwfOEKNJYFXWfWI=; b=7vasPOb1ydtIZ6NmiuH13vqg8fJOQ7yHBhNlFZ0qX2zVt3meFy4rxrvk0e7oWwjSZb vBh6KrF0xu18ZwpyiaMEqERPFuU2H3VAwYoQdCQNle7PnHuE0NvAaOyT3PU1SzQt3lcw St3UtYMkiTk0GHTRQQojZSAIpIoOKDqaeOcJ87NqKefLrKJBm1OUbyyCpc1J3DnJu3Jm VLv2gGRjnvSPNaQlwzekl4+qd3wn95HDHh5ZmRAWt23iEIXMJ02IxIZV7nGZfnhFe/3b LKE1n7nEDhDSGMKZS9mqVVvtzZvw7vbgqLc8hbXGT+w7QCshuFoyOhLBZskW+bEtEskJ vqWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jnWKlRdH04oGY8LPFdlAGmbdN0QQuwfOEKNJYFXWfWI=; b=aWkOd7LqOkLAwLWVMQk6PBjueD/yzRiWSRdb/M0b04YzPQqLvvpRhOyIxnxT1YMTcP JCE+kcA9YCNzptNRXEhADTI6HEBVg6kKzfXRJG+jPUf8ozDjMrQ/kmQ+kFwsZgdcJxz/ QtbJH0Jv3KNlVNRed0AC6e/cTCkbG87/E74NQ+cquPl6l2IIqeSWOF5uwardp6xt71ZY OgIZ3YeKCmfrKnUoYbNG4+AFORAjK9pHNa3qPAXnht4JEqHFCZX4e8vnJgchy+MqqDa/ clWjmZh9vHJQfVKodJKmU0EzY8xhO15jd9tKA1dl21I0ycosUDpTcfpYcTcF/VzvT9oX 2Dsw==
X-Gm-Message-State: AOAM533Tdt+jUVwpBkc+ejZAKtq6aiRmeWJoLuAZW5QZdJnbLv+LxBib 5r2YF6m4cQji+qSKuSdobObsYkWZyLUsgfYoesk5cR2mjmrboA==
X-Google-Smtp-Source: ABdhPJxpTfgOFJHFFj52x4Fd73g9Ix8HdZmZZCP+PWfODfJTpaUrGTQg6xrho9As4MdFLUoGvQLXm0o6bfj5QXgWjTM=
X-Received: by 2002:a05:6808:1389:: with SMTP id c9mr1316821oiw.55.1638991028912; Wed, 08 Dec 2021 11:17:08 -0800 (PST)
MIME-Version: 1.0
References: <CAPt1N1=SbZLDwHZ5U6_U7ixPRo_Oi0BRjP3m-CDy_v8+nUW=uQ@mail.gmail.com> <m1muWxh-0000IFC@stereo.hq.phicoh.net> <CAPt1N1kfw+R8PX951nF1JvLz-=gosjc290avhyuR9zuhNZTWEA@mail.gmail.com> <303090B0-DAC3-4666-BBD7-A18ADB8CB3F0@employees.org> <m1mv0QV-0000IFC@stereo.hq.phicoh.net> <CAPt1N1nTH9x5xd0kTrern6Eb9vmNfn-L+QsUK+ptbz9X3x4pWg@mail.gmail.com> <9b3f4f31-c988-5700-5269-dbc3f44f4ba3@foobar.org>
In-Reply-To: <9b3f4f31-c988-5700-5269-dbc3f44f4ba3@foobar.org>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 08 Dec 2021 14:16:33 -0500
Message-ID: <CAPt1N1nOM6dFa0vq4zJnESFSJZQ=jb65_bBcvHcPUfn0Bj-2sw@mail.gmail.com>
Subject: Re: Possible issue with source address selection for ULAs...
To: Nick Hilliard <nick@foobar.org>
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001194c405d2a75663"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KBg4UNI60uTSC99jpxrUjlfvPvI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Dec 2021 19:17:16 -0000

I think it's not completely inaccurate to say that the network setup I
described is broken, but it's not completely accurate either. What I'm
describing is a situation where a perfectly valid network configuration
stopped working because of an automatic behavior that I think is also
perfectly valid. Certainly we can cure this problem by adding routing, but
that's not practicable at the moment, and I don't actually know what it
will take to get to where it is.

So given that assumption, what we are seeing here is something that
certainly could happen, and that the owner of the network might not know
how to fix. So the question I'm trying to get to is whether (a) it's worth
addressing this issue, and (b) what harm addressing it in the way I'm
suggesting might cause.

On Wed, Dec 8, 2021 at 12:38 PM Nick Hilliard <nick@foobar.org> wrote:

> Ted Lemon wrote on 08/12/2021 17:11:
> > I think we can take it as read that the right solution to this problem
> > is a full routing protocol on the home network.
>
> I was mid-reply on an email which pointed this out, and was stuck on how
> to suggest this without causing too much offence, so thank you for
> pre-empting  :)
>
> > However, my question is
> > about what a host can do to avoid this problem, given that there is no
> > full routing protocol running on the home network, which is a problem we
> > can't immediately solve.
>
> Couple of stream-of-consciousness thoughts:
>
> 1. your network is broken and you want to implement a protocol change in
> ipv6 as a workaround.  Well, ok.  Ultimately there's some complexity on
> your network, and this complexity has consequences.  The question is how
> to address the consequences: reconfig of the network to remove the
> multiple networks, ensuring that all networks have reachability to all
> others as appropriate, or change the underlying protocol to change how
> SAS works..
>
> Moving the mountain is rarely the best approach.
>
> 2. your proposed fix may not be a bad idea in its own right, but not
> because of the reasons that you want it.
>
> Nick
>