IETF Logo Mail Archive

Re: [v6ops] draft-ietf-v6ops-64share

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 30 July 2013 14:58 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 880ED21E80E3 for <v6ops@ietfa.amsl.com>; Tue, 30 Jul 2013 07:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level:
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKqiGEnyKdBn for <v6ops@ietfa.amsl.com>; Tue, 30 Jul 2013 07:58:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 3837421E80BB for <v6ops@ietf.org>; Tue, 30 Jul 2013 07:58:07 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 386322018A; Tue, 30 Jul 2013 12:04:09 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A9C7E63A7C; Tue, 30 Jul 2013 10:56:43 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9A15B636AD; Tue, 30 Jul 2013 10:56:43 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Lorenzo Colitti <lorenzo@google.com>
In-Reply-To: <CAKD1Yr27Y_wp1f89=gvarUc2q77p9LaKr_y-HJeCzYFPcuqMyA@mail.gmail.com>
References: <12351.1375184644@sandelman.ca> <CAKD1Yr27Y_wp1f89=gvarUc2q77p9LaKr_y-HJeCzYFPcuqMyA@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 30 Jul 2013 10:56:43 -0400
Message-ID: <9422.1375196203@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "Byrne, Cameron" <Cameron.Byrne@t-mobile.com>
Subject: Re: [v6ops] draft-ietf-v6ops-64share
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Jul 2013 14:58:18 -0000

Lorenzo Colitti <lorenzo@google.com> wrote:
    mcr> I sure prefer scenario 1.  I think that MIF-aware applications will be
    mcr> happier with two v6 addresses.

    > Why? One would hope that a MIF-aware application would understand that it's
    > possible to have an IP address on one interface and use it on another
    > interface.

Ideally, a MIF aware application would see the same IP address on two different
interfaces as being in two entirely different domains.
Having one IP makes debugging and human stuff harder.

    mcr> (I think that privacy extensions are useless for a device/network which
    mcr> likely
    mcr> has the same /64 all the time)

    > It doesn't have the same /64 all the time. When you lose coverage or switch to
    > wifi, when you come back to the 3G network you'll get a different prefix.

That's might be true, but I really hope that they give me the same /64 when
I'm in the same place, so that I can have longer lived incoming connections.
Otherwise, I might as well NAT66 :-)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works

v2.23.0 | Report a Bug | By Email