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

Ted Lemon <ted.lemon@nominum.com> Tue, 24 June 2014 20:51 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 6D0021B288C for <v6ops@ietfa.amsl.com>; Tue, 24 Jun 2014 13:51:32 -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 msPfxb-OcCin for <v6ops@ietfa.amsl.com>; Tue, 24 Jun 2014 13:51:31 -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 463A01B2889 for <v6ops@ietf.org>; Tue, 24 Jun 2014 13:51:31 -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 DFE3A1B81C7 for <v6ops@ietf.org>; Tue, 24 Jun 2014 13:51:30 -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 C75FD190074; Tue, 24 Jun 2014 13:51:30 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 24 Jun 2014 13:51:30 -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: <53A9E2F3.6080206@foobar.org>
Date: Tue, 24 Jun 2014 16:51:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <21C61EF9-A82A-4493-9597-DCC62DE37F78@nominum.com>
References: <20140602013829.875B917236AC@rock.dv.isc.org> <53A843C9.1040002@gmail.com> <70F894D7-8701-420F-B16F-F8EAF3AE276F@nominum.com> <53A94E88.6070101@foobar.org> <8E5FC7CC-454E-437F-A85B-69366BC5D7B5@nominum.com> <53A989D8.2080704@foobar.org> <BA6D229B-0645-42CB-BC29-DB467EB697A7@nominum.com> <53A9C84A.8020304@foobar.org> <20140624194638.GZ46558@Space.Net> <53A9D643.6040100@foobar.org> <20140624195720.GA46558@Space.Net> <53A9E2F3.6080206@foobar.org>
To: Nick Hilliard <nick@foobar.org>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/mVDM6FYC-IZqnBMVutIcGIPFjJU
Cc: 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: Tue, 24 Jun 2014 20:51:32 -0000

On Jun 24, 2014, at 4:43 PM, Nick Hilliard <nick@foobar.org> wrote:
> So I ask again: can we please define what we mean by multihoming in the
> context of this discussion?  Until we have clarified what we're talking
> about, the discussion is not going to lead anywhere.

I shut up about this because as far as I can tell, the question of multihoming has no bearing on this discussion.   That is, I'm fairly sure that even if I explained what I meant by multihoming, it would still not lead us anywhere useful.