IETF Logo Mail Archive

Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

Ted Lemon <mellon@fugue.com> Mon, 17 July 2017 14:43 UTC

Return-Path: <mellon@fugue.com>
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 3F771131C26 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 07:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 VVclxqzNQZ1y for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 07:43:52 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2324B131C42 for <v6ops@ietf.org>; Mon, 17 Jul 2017 07:43:52 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id q86so77503119pfl.3 for <v6ops@ietf.org>; Mon, 17 Jul 2017 07:43:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=m9sH/PgXw42VxwSRlf58tIgG9IAwIKjNndudeeFx/Y0=; b=p3xlrjYJ6Xm/nzEAJB9efiZTwcstvP/yEAIawpwBfuy6/yC/6JS+mXLq5QswQ8HKaG MntFl4mf6paqbyafep/iW5A7sS9jrof/+iiiIYd5viUminBPEQ2bqpnLYw1vZ+GsbTkM le1lnVax2uZ66JOVQVjti0rcNzkpbfU/Vo2amrfDS9+aXssUFQ/o8eM6SelqdMiEzOBl dX1VEvNOpyF2Kn7Ll13KrdioS9EeCld0nD5BVKInXlyrfAZAPmhipfK9Wj9VgvM19wQK 1YgyMvOFh18jBXDae1C/B4V6JLUqKpw1RDqdghEu1gNrzR7FNIPLyakAzP3amTgacKpC QgPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=m9sH/PgXw42VxwSRlf58tIgG9IAwIKjNndudeeFx/Y0=; b=Cpb6m4ktTpJgmiFegHa6Md/knEoZIDqebvXnii4gTXRAScujZeusPf7TrWDBCYbZXe shxU1Ny5fdsBUb4LqCBzz0UG4UhX+HXAfuMqqO9BhcJMAhRiVGVOtuAAJjQ1Sbj9sP8y OYdrgyPaBOx9FMpjqtP3MeVTBBc/Y9Hu81bhko55TB4cEjsChNLAm0HzK4DUaGeSQPMz A+dxwEnWtdZjOJ/W2MdZFrUBhWW/tVYaHJzI3Jckr2hWeKNTRIoC5BQMhJFawuWp5Zww fUeaIl9wZkSxzoakkHY0syZ4kyMq8SZU2S70asUafo9qMQdOVYgrmp8VNpECvnJRFUQa klGw==
X-Gm-Message-State: AIVw1139qxV9Ba9LjxC8Sowq0sizGYTyvYZWbh3oWBdPM8a77tzI5Tta +rtgWyCx7r5jhf5YEyesGFHVZmv1TqG87zw=
X-Received: by 10.98.67.147 with SMTP id l19mr19134967pfi.198.1500302631621; Mon, 17 Jul 2017 07:43:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.42 with HTTP; Mon, 17 Jul 2017 07:43:10 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1707171636110.29742@uplift.swm.pp.se>
References: <7643C1DC-76A3-4652-9BB1-D0D42801F37E@consulintel.es> <CAPt1N1kroh2cPkTr8HRfNjLTdG0hkC1oQsUZdhQzQA5tA9-xug@mail.gmail.com> <9AF791E9-1E12-425E-93A4-2913E2D18CBA@consulintel.es> <CAPt1N1kU4cpVCsp7W3XNAZupYqjTWVH+BNp9bwtznnWD_uP2oQ@mail.gmail.com> <CAEqgTWZzZW0wKggDXjY=-aMfDxzd5-GoRqju1829XwY3aHQuYg@mail.gmail.com> <0FAF1E05-DA4B-47BF-95F7-7EFCD1BED9B0@cable.comcast.com> <42188852-BBEB-4D75-967F-4BED79BBBCAE@consulintel.es> <CAFU7BARahTfH_Uy_t22EthGuFMJ=q-N1zxismNAVkHWWJA-Obw@mail.gmail.com> <CBA23B1B-C5A3-413C-B399-93F537C99015@consulintel.es> <CAFU7BARz_u92NweYkTizT2=q420sBRh11m9bqWO9+aexCi3ANA@mail.gmail.com> <2A639918-C6AC-44B8-8D66-5293EE13A7BD@consulintel.es> <CAFU7BASrxoroJVHwxFpwwBxCUC62_VZXsUGgfDOj6y+KVWk6tw@mail.gmail.com> <C510C095-B9AB-432F-A050-FD9CD640A6DE@consulintel.es> <CAFU7BAR413hwY_G2Cw-Ab+J158udPDLSFo==EN4LHjWb_YzD5Q@mail.gmail.com> <10FFC885-81E1-45E6-B87D-5520C35FDE2C@consulintel.es> <alpine.DEB.2.02.1707171636110.29742@uplift.swm.pp.se>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 17 Jul 2017 16:43:10 +0200
Message-ID: <CAPt1N1kSFpdynEU0tyfF8aorFBmrNGtR6hCbg4E6GJjt+ZpitQ@mail.gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0c0f4469ec400554846d16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MHzKWg0koLE5fWwG4-5rp_LwTv0>
Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Jul 2017 14:43:57 -0000

I realize that Jordi is not satisfied by any of the responses to this
message that have been sent so far, and I don't want to minimize the
unfortunateness of that, but I do not think there is any change that
further discussion on the topic is going to result in that satisfaction
happening, and I don't think we are learning anything new by continuing the
discussion.   I am muting this thread now, so please do not take my
subsequent silence as agreement with Jordi's position.

On Mon, Jul 17, 2017 at 4:41 PM, Mikael Abrahamsson <swmike@swm.pp.se>
wrote:

> On Mon, 17 Jul 2017, JORDI PALET MARTINEZ wrote:
>
> So the dogfood that we need to try (now) is the one that can sever the
>> “real” market, not the one that could serve the marked when they are ready
>> to replace (in a big %) all the apps and devices that are IPv4 only. We
>> could try this in a follow up phase (actually there is an SSID for that
>> already).
>>
>
> My android and iOS devices work great on IPv6 only using the proposed
> suggestion. My MacOS and Windows do not (because they don't have the
> 464XLAT or bump-in-the-API that is available on the mobile platforms). I
> already know this. I don't need to prove it to anyone.
>
> It's premature to go IPv6 only on the main wifi before main operating
> systems support the same mechanisms available on the mobile devices.
>
> 1. My "mosh" session only tries the same AF that it initially connected
> to. If I initially connected on an IPv4 network, it will never connect to
> anything on an IPv6 network.
>
> 2. My Windows VM which needs to reach IPv4 only resources have no way to
> do this through the Parallels NAT44. I would need a CLAT for this.
>
> There are lots of desktop OS applications that do not work on IPv6 only
> DNS64+DNS64 without CLAT. I have tried this, it doesn't work, there is no
> need to do wider test. OS vendors need to implement CLAT (or equivalent)
> for it to be viable.
>
> If the main wifi is going IPv6 only, I will run my mobile devices on it,
> but I will immediately swap to the dual stack SSID for my computer.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>

v2.23.0 | Report a Bug | By Email