Re: [IPv6] communicating multiple link (status) to hosts

Philip Homburg <pch-ipv6-ietf-10@u-1.phicoh.com> Thu, 21 March 2024 20:29 UTC

Return-Path: <pch-b538D2F77@u-1.phicoh.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 537CAC14F6B8 for <ipv6@ietfa.amsl.com>; Thu, 21 Mar 2024 13:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 HJIo_AiJNBNz for <ipv6@ietfa.amsl.com>; Thu, 21 Mar 2024 13:29:13 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [IPv6:2a10:3781:2413: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 61248C14F6AD for <ipv6@ietf.org>; Thu, 21 Mar 2024 13:29:08 -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 m1rnP28-0000LiC; Thu, 21 Mar 2024 21:29:04 +0100
Message-Id: <m1rnP28-0000LiC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
From: Philip Homburg <pch-ipv6-ietf-10@u-1.phicoh.com>
Sender: pch-b538D2F77@u-1.phicoh.com
References: <186314.1710989921@dyas> <m1rnIQF-0000M1C@stereo.hq.phicoh.net> <CAPt1N1njXg9crrzZXYTjbH+96dcAytvAmbZFiccEq6cHGHvVyA@mail.gmail.com>
In-reply-to: Your message of "Fri, 22 Mar 2024 03:01:13 +1000 ." <CAPt1N1njXg9crrzZXYTjbH+96dcAytvAmbZFiccEq6cHGHvVyA@mail.gmail.com>
Date: Thu, 21 Mar 2024 21:29:04 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vakBeULJWuZd07je44QapsYVovY>
Subject: Re: [IPv6] communicating multiple link (status) to hosts
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: Thu, 21 Mar 2024 20:29:15 -0000

>    I think it's actually unrealistic to expect routers to forward
>    packets to each other in many of the settings we care about,
>    e.g. home networks. "Routing protocol in the home" is pretty
>    much the hill that homenet died on. Not because it's hard, but
>    because it's hard to do automatically and nobody wanted to agree
>    on a single protocol (we did finally agree on Babel, but tell
>    me where I can buy a router with Babel in it?).  

In the good old days, one would enable RIP on two routers, and that's it.
No need to configure anything. Just enable it and be done.

I made an extension to RIPv6 to do src/dst routing. No need to configure
anything. Just enable it and router could route packets based on source
address.

But that was not good enough for the IETF. RIPv6 is way to simple to handle
a few upstreams on a shared link.