Re: [v6ops] Thoughts about wider operational input

Philip Homburg <pch-v6ops-11@u-1.phicoh.com> Tue, 22 March 2022 10:43 UTC

Return-Path: <pch-b28DE43C2@u-1.phicoh.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 B34423A0EE8 for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 03:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.722
X-Spam-Level:
X-Spam-Status: No, score=-1.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.186, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no 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 NJp1qM2FfEH8 for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 03:43:18 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6.hq.phicoh.net [IPv6:2001:981:201c:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5547D3A0FAF for <v6ops@ietf.org>; Tue, 22 Mar 2022 03:43:17 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #158) id m1nWbyp-0000IzC; Tue, 22 Mar 2022 11:43:11 +0100
Message-Id: <m1nWbyp-0000IzC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
Cc: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
From: Philip Homburg <pch-v6ops-11@u-1.phicoh.com>
Sender: pch-b28DE43C2@u-1.phicoh.com
References: <52661a3d-75dc-111a-3f23-09b10d7cb8d4@gmail.com> <A72CDDDB-CDCE-4EAF-B95E-997C764DB2C4@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>
In-reply-to: Your message of "Tue, 22 Mar 2022 10:34:22 +0100 ." <7F4AEB43-4B24-4A21-AE9D-3EB512B98C46@consulintel.es>
Date: Tue, 22 Mar 2022 11:43:10 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/EB5QxTHH2DFiNpd3gJnJHt2ExB8>
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: Tue, 22 Mar 2022 10:43:28 -0000

> 2. I think in the future almost
>    every site could want to be
>    multihomed, in some cases "n" links active, many other cases
>    just as a backup.
> 3. This means that renumbering is not
>    (probably) a valid choice in
>    any cases. 
> 4. Can we make PI work in such "huge scale"
>    scenario?
> 5. Can source-address forwarding work and solve all
>    that, or we need
>    that and/or something else.

It seems unlikely to me that PI will work in a 'huge scale', so we are
left with poor man's multi-homing where the user's network will use addresses
provided by different ISPs.

For outbound connections we have good options. Putting the smarts in the
host means that a router only has to drop it's default route to get hosts
to switch to another upstream.

With babel, etc. multi homing can be transparent to hosts.

The big advantage compared to NAT is that with NAT you would have a single
NAT box with multiple uplinks. With IPv6 you can put that in different
routers. Giving redundancy against router failure.

Obviously, companies that care about multi-homing would need to ask about
routers that support babel. 

The unsolved problem I see is inbound connections. What do you put in DNS?
Who keeps information in DNS up-to-date.