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

Ted Lemon <ted.lemon@nominum.com> Sun, 01 June 2014 20:32 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 7A1361A008C for <v6ops@ietfa.amsl.com>; Sun, 1 Jun 2014 13:32:01 -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 RxAi9y3vwu23 for <v6ops@ietfa.amsl.com>; Sun, 1 Jun 2014 13:32:00 -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 F3AB61A0086 for <v6ops@ietf.org>; Sun, 1 Jun 2014 13:31:59 -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 0DB0E1B806B for <v6ops@ietf.org>; Sun, 1 Jun 2014 13:31:55 -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 06FD019005C; Sun, 1 Jun 2014 13:31:55 -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; Sun, 1 Jun 2014 13:31:54 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <m1WrCJ2-0000DVC@stereo.hq.phicoh.net>
Date: Sun, 01 Jun 2014 16:31:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <3F6C2102-4572-41AE-B31F-5ED5183954C0@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> <CAKD1Yr0pvet1oOip-Y2Xi_h2mSZfW1R5HtfiAGbDEns0dY-d2A@mail.gmail.com> <2A4B72CD-EDF3-4D11-AC39-B65892F9173F@nominum.com> <m1WrCJ2-0000DVC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/bhSdq9SnhWQUB077ZF7Q1Ea6ZZQ
Cc: 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: Sun, 01 Jun 2014 20:32:01 -0000

On Jun 1, 2014, at 4:24 PM, Philip Homburg <pch-v6ops-3a@u-1.phicoh.com> wrote:
> Nice how this thread evolves:
> - Use PI space, it works (but is not really scalable)
> - No, no, get with the program. Get multi-homed on PA.
> - We don't actually have anything for servers and multi-homed PA.
> - Every piece of software has to do HE because of how multi-homed PA fails.
> 
> Great way of advertising IPv6.

Every piece of software that uses the network has to use DNS for ease-of-use, and has to use some kind of API to establish connections or send datagrams.   There is no reason why this API can't do happy eyeballs for the application without requiring any complexity _in_ the application.   Indeed, the API provided by Apple already provides this capability for free.

In comparison to what most apps have to do to work because of the higher-layer protocols they use (e.g., RESTful APIs have to support HTTP and TLS, streaming APIs have to support loss detection and data rate adaptation), doing happy eyeballs is the picture of simplicity.   The only reason it seems like it's not is that your mental model of a network API is (apparently) the BSD sockets API, which, while extremely useful, is pretty bare-bones.