Re: [IPv6] Suggestion for multi homed clients without NAT/NPT

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 05 January 2023 16:06 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 1874AC14CE2B for <ipv6@ietfa.amsl.com>; Thu, 5 Jan 2023 08:06:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 s-xOB2K4Pjgz for <ipv6@ietfa.amsl.com>; Thu, 5 Jan 2023 08:06:47 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2DCAC14F727 for <ipv6@ietf.org>; Thu, 5 Jan 2023 08:06:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9F5E03898C; Thu, 5 Jan 2023 11:35:05 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id OhySX40QLrou; Thu, 5 Jan 2023 11:35:05 -0500 (EST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 00F313898B; Thu, 5 Jan 2023 11:35:04 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1672936505; bh=Venz5VTawUNnrE28nMqJcK4gySQmmRqYr0+HKhmNQQk=; h=From:To:Subject:In-Reply-To:References:Date:From; b=RqJlO6rbzYIkO1XpTMc2YNM6P1SjrgLC9wudTYAJnA+haGs+E9e14xi8kqvy7bDqI xO0Qrwp0jVCljRx/vySDrrNGFBKygu2pKxuVbhmUSbRL9UBeVc5ieI6lGJYfbwdWKV +VZXG4+1rfNO76Sx5pJ5uL9lNF6r7BfCM7dhbdj22lK2mwfdt0NHT38n94k1bmzxX8 3SWkl0tVxBNNIIIWEf84LVYjI2L9UhYiWwf2BF0y/TNaBqjDatDvl/ZjhN05qLGl3d 6iw4qAEzL2KU3qIqkrWh/xFqZTRIOoknQwVk8rdP45lYsomrgYKWGfcZrTyygMzTrA E1Ttp5+6d27rw==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 3C8EE252; Thu, 5 Jan 2023 11:06:44 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Philipp S. Tiesel" <philipp@tiesel.net>, 6man <ipv6@ietf.org>
In-Reply-To: <14437462-8E95-4554-A4A4-A83E08382439@tiesel.net>
References: <b3742e2b-6472-9eb4-bee2-507fa8cdf4c6@posteo.de> <05ed3426-7731-baef-44a1-6fc50ce69a5b@gmail.com> <9586.1672523456@localhost> <14437462-8E95-4554-A4A4-A83E08382439@tiesel.net>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 05 Jan 2023 11:06:44 -0500
Message-ID: <9192.1672934804@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jQrH3HWthVMStW7XEFhxTuW-MWI>
Subject: Re: [IPv6] Suggestion for multi homed clients without NAT/NPT
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, 05 Jan 2023 16:06:52 -0000

Philipp S. Tiesel <philipp@tiesel.net> wrote:
    > I did my Ph.D. on that topic and called it Happy Eyeballs on Steroids.

    > Most results went into the TAPS WG… maybe have a look at
    > - https://datatracker.ietf.org/doc/draft-ietf-taps-arch/
    > - https://datatracker.ietf.org/doc/draft-ietf-taps-interface/
    > - https://datatracker.ietf.org/doc/draft-ietf-taps-impl/

Very cool.  I will read them. I didn't know TAPS was doing this, and I
suspect that few in 6man know either.  Maybe a 5 minute presentation is in order.

Philipp S. Tiesel <philipp@tiesel.net> wrote:
    > I am convinced RFC 8028 would also be a great start for clients with
    > multiple default routes, e.g., enabling stuff like multi-path TCP to
    > work correctly, but it will not be sufficient for meaningful
    > multi-homing / source address selection.

Do your IDs explain why?

    > In addition, to avoiding problems with CDNs, it is also  required to
    > separately keep track of DNS on a per-router/PvD basis and only use the
    > matching source addresses for new connections, so RDNSS should also be
    > treated analog to the source address in RFC 8028.

I'm surprised to hear this.  I'm not convinced that PvD are a good idea, I
think that they represent IPv4 thinking, and I think that there are better
ways to do this in IPv6.  So I'm curious to understand how they are connected.

    > Having tried to manage traffic from within getaddrinfo() I can only
    > recommend to abandon that idea.
    > A lengthly write-up why can be found here in Section 6 of this expired
    > draft:
    > https://datatracker.ietf.org/doc/html/draft-tiesel-taps-socketintents-bsdsockets-02

Thank you. I agree that it can't be done properly in getaddrinfo().

    > The only way forward I see is something like TAPS and Appel’s
    > implementation is already pretty close what it would needs to make use
    > of multi-homing here. They just need a litte more
    > aggressive/opportunistic happy eyeball candidate selection.

Is there a FAQ on how to play with this code?


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide