Re: [v6ops] new draft: draft-vyncke-v6ops-happy-eyeballs-cookie

Joe Touch <touch@isi.edu> Thu, 30 October 2014 22:43 UTC

Return-Path: <touch@isi.edu>
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 7F08F1A887C for <v6ops@ietfa.amsl.com>; Thu, 30 Oct 2014 15:43:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 FRPUHYG1pc6c for <v6ops@ietfa.amsl.com>; Thu, 30 Oct 2014 15:43:23 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 991D81A887B for <v6ops@ietf.org>; Thu, 30 Oct 2014 15:43:23 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s9UMgqOu028209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 30 Oct 2014 15:42:52 -0700 (PDT)
Message-ID: <5452BEEC.7000708@isi.edu>
Date: Thu, 30 Oct 2014 15:42:52 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Erik Nygren <erik+ietf@nygren.org>
References: <201410291508.s9TF8Ki1018634@irp-lnx1.cisco.com> <5452B843.10209@isi.edu> <CAKC-DJhGQ7v=-je9kiAgC4bjGAawjhRnmo2-nB7+9y_=LyLJoQ@mail.gmail.com>
In-Reply-To: <CAKC-DJhGQ7v=-je9kiAgC4bjGAawjhRnmo2-nB7+9y_=LyLJoQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/qslsEZWaQbQEnYpK1DamMd-a10I
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, draft-vyncke-v6ops-happy-eyeballs-cookie@tools.ietf.org
Subject: Re: [v6ops] new draft: draft-vyncke-v6ops-happy-eyeballs-cookie
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: Thu, 30 Oct 2014 22:43:25 -0000


On 10/30/2014 3:22 PM, Erik Nygren wrote:
> It's unclear if the solution space here is the same as for host IDs?  In
> particular, that draft talks about "remote servers are not able to
> distinguish between hosts sharing the same IP address" whereas here the
> case is "remote servers are not able to distinguish that a single host
> uses multiple IP addresses, some of which may be shared with other
> hosts". 

Yes, the role of client and server is reversed, but in both cases the
issue is the same:

	a single host using multiple IP addresses

The key issue for this doc is that the addresses are IPv4 and IPv6, but
the potential solutions remain relevant, AFAICT.

> In particular, the multiple IP addresses in the multi-homing
> context may not even be in the same administrative domain.

That affects *some* of the solutions, but not all.

Joe


> 
>    Erik
> 
> 
> On Thu, Oct 30, 2014 at 6:14 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
> 
> 
> 
>     On 10/29/2014 8:08 AM, fred@cisco.com <mailto:fred@cisco.com> wrote:
>     > A new draft has been posted, at http://tools.ietf.org/html/draft-vyncke-v6ops-happy-eyeballs-cookie.
>     Please take a look at it and comment.
> 
>     Under potential mitigations, is there a reason not to refer to the use
>     of alternate (non-IP address) host IDs?
> 
>     E.g., as noted in RFC 6967 and
>     draft-boucadair-intarea-host-identifier-scenarios.
> 
>     Joe
> 
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org <mailto:v6ops@ietf.org>
>     https://www.ietf.org/mailman/listinfo/v6ops
> 
>