Re: [v6ops] PI [ULA draft revision #2 Regarding isolated networks]

Gert Doering <gert@space.net> Mon, 02 June 2014 15:26 UTC

Return-Path: <gert@Space.Net>
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 363601A0380 for <v6ops@ietfa.amsl.com>; Mon, 2 Jun 2014 08:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 2RH9FJNiTxIQ for <v6ops@ietfa.amsl.com>; Mon, 2 Jun 2014 08:26:49 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 213731A0382 for <v6ops@ietf.org>; Mon, 2 Jun 2014 08:26:48 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 479AE60B3F for <v6ops@ietf.org>; Mon, 2 Jun 2014 17:26:42 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 2252160B34 for <v6ops@ietf.org>; Mon, 2 Jun 2014 17:26:42 +0200 (CEST)
Received: (qmail 6952 invoked by uid 1007); 2 Jun 2014 17:26:42 +0200
Date: Mon, 02 Jun 2014 17:26:42 +0200
From: Gert Doering <gert@space.net>
To: joel jaeggli <joelja@bogus.com>
Message-ID: <20140602152642.GB46558@Space.Net>
References: <2A4B72CD-EDF3-4D11-AC39-B65892F9173F@nominum.com> <CAKD1Yr2NH4Kca4EvhjN2XnDbt8F2eS56ipxu3npH9yOh1bmQaA@mail.gmail.com> <F12F173B-9FF2-4EF8-B11E-33AEDA24961F@nominum.com> <CAKD1Yr1cGx7UfxZaEhm7oHA5PLvghVc52oPVkEQF90_7Vm__vw@mail.gmail.com> <1FDC3A7F-15EC-4397-AF3E-10F86EA04228@nominum.com> <538BDA84.6030800@bogus.com> <37D09BEE-FEDF-4514-8CEB-62959A89C3FF@nominum.com> <538BE13C.7050900@bogus.com> <20140602081743.GP46558@Space.Net> <538C93E9.7080405@bogus.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="+X7K3ZbSRJxCtaUy"
Content-Disposition: inline
In-Reply-To: <538C93E9.7080405@bogus.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/mcVo6tudjXGVcWm_Kv4RgQVXdOA
Cc: Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>, V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] PI [ULA draft revision #2 Regarding isolated networks]
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: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2014 15:26:52 -0000

Hi,

On Mon, Jun 02, 2014 at 08:10:33AM -0700, joel jaeggli wrote:
> > Well.  It might not have been your intention, but what you said is very
> > clear "we're not going to make multihoming in the homenet case work".
> 
> No sorry I did not. What I said is that I believe you're pushing an
> expectation of a certain amount of complexity onto hosts in the
> interests of measurement and detection of topological corner cases. some
> hosts might choose to do that in the interest of improved connectivity,
> the expectation that they all should is onerous, you be should have an
> expection that devices and applications will work in the absence of HE.
> 
> having a router invalidate itself as a nexthop because it has detected
> that it's paritioned from a provider or the internet seems like an
> incredibly basic concession that you'd want to have happen even were
> everything HE enabled.

You seem to be using a different Internet than I do, which seem to consist
of "the only way things can break is if my CPE loses contact to it's ISP,
which is always easily detectable, but as soon as the packet reaches the
ISP, it will be 100 percent reliably transported and answered, all the
time".

My Internet, unfortunately, seems to have less boolean cases where
packets just disappear when being sent into certain directions, without
even adjacent devices noticing, much less "devices 10 hops away".

> > In the case
> > 
> >     host --> router --> ISP A ---->  ISP C --------+
> > 	       +------> ISP B ---->  ISP D ------> ISP E --> target
> > 
> > where "host" has source addresses A and B, and there is a problem at 
> > ISP *C*, preventing connectivity via A->C->, how exactly is the homenet
> > router "router" supposed to *know* that, or even solve it?
> 
> It doesn't.

Thanks for acknowledging that.

> > Assuming "as long as connectivity to ISP A is there, the whole Internet
> > will be reachable via ISP A" is completely ignoring reality.  Blackhole
> > issues happen (where even BGP to the customer router won't help you)...
> 
> yes, bgp multihoming doesn't solve it either. that has not rendered it
> unsuitable for use.

BGP multihoming has it's uses, but I think all but Owen agree that it's
not going to solve the "billions of leaf networks without IT knowledge"
case.

Multi-Address multihoming has the potential to be a radical improvement
for "leaf networks without IT knowledge".  

Especially for cases that BGP based multihoming will not handle well today, 
like "black hole problems due to people's MPLS stuff running amock", 
"stateful firewalls in the packet path that do not handle asymmetric 
traffic well", "selection of the ISP used by the user, not by the CPE 
router", etc.

It's certainly not a replacement for BGP based multihoming for "networks
with lots of servers and qualified IT staff".  Just to avoid that particular
avenue of ratholing.


> > (IETF is complaining about lack of operator input.  Here is operator input.
> > Don't ignore it, otherwise operators get bored and find solutions outside
> > IETF space, like, with NAT)

Maybe I should include this in of my signature when writing to IETF lists...

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