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

Ted Lemon <ted.lemon@nominum.com> Mon, 02 June 2014 16:37 UTC

Return-Path: <Ted.Lemon@nominum.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 DEC981A0260 for <v6ops@ietfa.amsl.com>; Mon, 2 Jun 2014 09:37:09 -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 O7L4FCIMqi7C for <v6ops@ietfa.amsl.com>; Mon, 2 Jun 2014 09:37:08 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ECA51A025D for <v6ops@ietf.org>; Mon, 2 Jun 2014 09:37:08 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D71631B8208 for <v6ops@ietf.org>; Mon, 2 Jun 2014 09:37:02 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 8F64219005C; Mon, 2 Jun 2014 09:37:02 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Jun 2014 09:37:02 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <1DA781EA-D249-4B91-B8B7-3B719CE88925@nominum.com>
Date: Mon, 02 Jun 2014 12:37:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F07722F4-6791-4EF0-B8F2-3072DA98401E@nominum.com>
References: <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com> <5384937A.90409@foobar.org> <m2iooq4oqi.wl%randy@psg.com> <5385762E.5020901@dougbarton.us> <5385AA97.1050207@fud.no> <53864DCB.5070202@gmail.com> <53865EA2.9000502@fud.no> <02dc01cf7c06$cc6a4bc0$4001a8c0@gateway.2wire.net> <97390E9C-460F-4D08-AFCE-E4A991E2B0E4@cisco.com> <46D22F62-3528-4B9D-9FCF-C9C7466A9ABA@delong.com> <20140531104145.GQ46558@Space.Net> <m1WqqZ4-0000DqC@stereo.hq.phicoh.net> <20140531214908.10FEE1719BB4@rock.dv.isc.org> <m1WqrFK-0000BHC@stereo.hq.phicoh.net> <23125E9D-85A1-49EB-ACE6-DB5EAC67EE02@nominum.com> <538B6AC3.7020402@bogus.com> <1DA781EA-D249-4B91-B8B7-3B719CE88925@nominum.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/i58NKDsswD1SHa3-nlosRyWbXhQ
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 16:37:10 -0000

On Jun 1, 2014, at 4:38 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> On Jun 1, 2014, at 2:02 PM, joel jaeggli <joelja@bogus.com> wrote:
>> Assumption of the Existence of HE  is a pretty dodgy proposition.
> Then we can't do multihoming without NAT.

This rather badly qualified comment appears to have generated a lot of discussion, so to head off further discussion I'd like to clarify a few points.

First, if you are multihomed, and both paths are working, then a host that does nothing special will work.   Second, if one connection goes out, and the routing updates, then an application that just retries when it doesn't get a connection will get a connection; for applications for which delays on the order of the time it takes for routing to update are harmless, redundant multihoming will work with no changes.

So the statement I made was false when interpreted in this context.   I know that it's false, and you don't need to keep arguing with me to convince me it's false.   I'm sorry for having been sufficiently unspecific that people thought I meant my statement was true for the above cases.

The cases I care about are in fact edge cases.   They don't happen all the time, and depending on the application they may or may not be important.   I care about them because I've been affected by failures, and I'd like to be able to say how to get these cases right without resorting to the use of NAT or NPT.   I'd like for there to be better tools for application developers to use so that they can address these edge cases relatively cheaply; possibly even more cheaply than they now do network programming that doesn't address these edge cases.   If you don't care about these edge cases, you will have little concern for this, and will not consider dealing with these edge cases important.

I, and no doubt most participants on this mailing list, am deeply uninterested in hearing "it works okay for me, so your edge cases don't matter"   I am also not interested in trying to get you to say "I care deeply about these edge cases."   It's okay with me if you don't care about them, and don't consider it important that they be addressed.   You don't need to respond to this message with yet another assertion that there is no problem here--it won't convince me, and what I want to do about this probably won't affect your application anyway.

If you are interested in thinking about this problem, the place to discuss it is probably the MIF working group--it's related to the work that's being done there, although it's not the entirety of that work.   If you are not interested, please let's just let this drop.   I'm sorry for the troll--I didn't intend it to be a troll, but I could have phrased it in a way that was less trollish.  I will try to do better next time.