Re: [v6ops] Question on multi-homed nodes and address/route selection

Gert Doering <gert@space.net> Mon, 06 March 2017 19:50 UTC

Return-Path: <gert@space.net>
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 234ED1299BF for <v6ops@ietfa.amsl.com>; Mon, 6 Mar 2017 11:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] 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 nbd1Pv3tqo2i for <v6ops@ietfa.amsl.com>; Mon, 6 Mar 2017 11:49:59 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (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 1ED7D1299BE for <v6ops@ietf.org>; Mon, 6 Mar 2017 11:49:59 -0800 (PST)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id A54E86138E for <v6ops@ietf.org>; Mon, 6 Mar 2017 20:49:57 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 6B18F60771; Mon, 6 Mar 2017 20:49:57 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 5D1CE307D; Mon, 6 Mar 2017 20:49:57 +0100 (CET)
Date: Mon, 06 Mar 2017 20:49:57 +0100
From: Gert Doering <gert@space.net>
To: Simon Hobson <linux@thehobsons.co.uk>
Message-ID: <20170306194957.GT2367@Space.Net>
References: <E969A0C5-46E5-4B58-BDEB-AE686D76210F@thehobsons.co.uk> <013B7A75-E5F6-4F47-9D92-33114F1781F8@cisco.com> <B1BBBF51-2B5D-4E65-BB23-1D1A52C1A183@thehobsons.co.uk> <CC646EAB-3175-4A6E-A6EC-0623198C2C9F@employees.org> <38FD32ED-C942-40AA-8FC7-365A244AB7C9@gmail.com> <C5B204AE-CD12-42A9-9EBE-48CB49019B70@thehobsons.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C5B204AE-CD12-42A9-9EBE-48CB49019B70@thehobsons.co.uk>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-hSLxbgU0H9lw_GtjSaqq6P9Nuw>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Question on multi-homed nodes and address/route selection
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 06 Mar 2017 19:50:00 -0000

Hi,

On Fri, Mar 03, 2017 at 04:53:15PM +0000, Simon Hobson wrote:
> Where there are multiple routers (eg separate routers provided
> by each ISP), then my *assumption* would be that the IPv6 stack
> would forward packets to the router which advertised the prefix
> containing the IP address the host/service has chosen to use for
> the outbound connection.

That only works if these routers are actually directly adjacent to
the host making the decision.  In the more generalized homenet model,
routers could be meshed in any ways, and the routers injecting a 
/48 into "the homenet mesh" could all be talking through an intermediate
router to the host - so the host would see a RA with (say) 3x /64 coming
from the same router.

But this is easily solved by source-dependent routing - "forward packets
with a source address from ISP A out via the line to ISP A, and so on
for ISP B, C, ...".

The source address selection part is much harder, and to my knowlege,
still mostly unsolved.  6724 has a list of rules that are not really
helping your use case ("multiple ISPs that have different characteristics,
and some of them might not even be working right in this moment") - 
especially, source-address *failover* is not something I've seen work
("I tried source A, and it did not work, so maybe ISP A has a problem
reaching target Z.  Let's try source address B, via ISP B -> Z").

> In general we would frown upon this setup since it doesn't work well in the IPv4 world - in the general case it means manual configuration on nodes to select the egress router and is inflexible.

The homenet architecture puts this nicely on the routers, and that part
really works quite well ("built a test setup, liked the result").

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279