IETF Logo Mail Archive

Re: [v6ops] PI heresy [draft-ietf-v6ops-ula-usage-recommendations - work or abandon?]

Philip Homburg <pch-v6ops-3@u-1.phicoh.com> Fri, 13 November 2015 12:49 UTC

Return-Path: <pch-bBB316E3E@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3331A1A21AF for <v6ops@ietfa.amsl.com>; Fri, 13 Nov 2015 04:49:24 -0800 (PST)
X-Quarantine-ID: <karM69hOk5Iw>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 karM69hOk5Iw for <v6ops@ietfa.amsl.com>; Fri, 13 Nov 2015 04:49:22 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 0195B1A21A4 for <v6ops@ietf.org>; Fri, 13 Nov 2015 04:49:22 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1ZxDn5-0000EpC; Fri, 13 Nov 2015 13:49:19 +0100
Message-Id: <m1ZxDn5-0000EpC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-3@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <20151106.063106.74659839.sthaug@nethelp.no> <CAO42Z2x3O8A1XKqN3PTcvM=xpF8W_WNSL1rVhHQ4ZY5HbVG=OQ@mail.gmail.com> <20151106.081425.74651560.sthaug@nethelp.no> <6ED54502-C5D1-4D09-877C-FE283E3EF142@delong.com> <5644EE46.7000805@gmail.com> <CAKr6gn1KokTGJ0cg70OR=q8Uv-1mr7TmjcYJwLVgsK_3i6tcpw@mail.gmail.com> <56453026.3090607@gmail.com> <CAKD1Yr1nb1svwHDE3Z7a1xF00CRw-kOrN6+Xgd6fVjqrN=gb+g@mail.gmail.com> <20151113080508.GB89490@Space.Net> <CAKD1Yr2paTyq7L8-dU9vhtxhDd17LvKPoQt4YY2DDxB-_5ZRbA@mail.gmail.com> <20151113112141.GN89490@Space.Net>
In-reply-to: Your message of "Fri, 13 Nov 2015 12:21:41 +0100 ." <20151113112141.GN89490@Space.Net>
Date: Fri, 13 Nov 2015 13:49:13 +0100
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/juV-VVCg_TrCgsRzlLR8dtYu8GQ>
Subject: Re: [v6ops] PI heresy [draft-ietf-v6ops-ula-usage-recommendations - work or abandon?]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 13 Nov 2015 12:49:24 -0000

>Networks break further upstream, without the actual upstream being
>noticeable
>broken.  Networks break certain paths, while others are working fine.
>
>We can do better than all-or-nothing.  We should.

I don't think a host should try to figure out which paths work and which
don't.

Maybe somebody can come up with a simple algorithm that generalises
happy-eyeballs and that is compatible with today's host operating systems.
But I doubt it. 

So while we wait for hosts to magically figure out what works and what doesn't
(and for mobile hosts, in any possible context, even when there is
high packet loss on the local link, etc),

I propose that routers just inform hosts which source prefixes are unusable
according to unspecified monitoring code running on the router. (Obviously,
routers should also propate that knowledge over internal routing protocols in
setups with multiple routers).

v2.23.0 | Report a Bug | By Email