Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 28 July 2017 23:25 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6718B13203D; Fri, 28 Jul 2017 16:25:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 EJICWVywxzsK; Fri, 28 Jul 2017 16:25:50 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 DA1BB131E6C; Fri, 28 Jul 2017 16:25:49 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id m88so86176421iod.2; Fri, 28 Jul 2017 16:25:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=5YT86f5vcCa8LYickVfTzfyrmvAJ5uOsWstLYVhbvzI=; b=LWfcHqNXIZlmjnlI1aY+FDX4vVgX2F7dxYB7KuLGHcOroOYgB4l8tHU5Z5X2gJrjwI 4Kbez4Dkk3iVfy45RmOA11P7ozni/9BGAyOSYhDySLCj9+NBALEW/UeY2R7GeDT4FO+0 Xhhiaeo1yK0BFz5aLyBeAPVqNjfh0xohA4e+uPbOtnS0TxoqciDm1qwSoCC3jQK66Pvo IiyXPNWRGqODyPV5BcgbS6fXMOSJM1gLyewnnRrf0G6OuBS8XWs1C9A61biJbAGY8vxa WjKCRxSWwsh7wf3UAL9gLez9M1g/SsZEKJv661LY05ZdARu6DPjwXkfGq3b9kSRIO1Jo yMzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=5YT86f5vcCa8LYickVfTzfyrmvAJ5uOsWstLYVhbvzI=; b=HXsheg8P8Xdr+WBvEayQDUUtD6+OULUdhn/PijwVuhW2VEYzR4uaTtOpEZ12t96WYm SbB7PUgh3eYWwusl+dEV8GgHct00lryLWx4/7sedpe44oxXH6pgLUCEUNZEYV9pG1oUr iHzqomuWRIVmGO+2glmzwB7nVpHy+ToZtBjsEgJVbPS5sB8erj6lomJLEn40n9VZkjsk g9mJKAO1yWZa1ls5OphxAWTgpeNF0p2C/wYHLxJxGe0PWMbL86y1nWZllp/kXNcnvPvB lxQBezOayr0xuliH1bQYYEwkDgh5B6I1AbLX7hYiNbskwVwcwxzQDRvfGfg9kdbBzmJ4 dcnw==
X-Gm-Message-State: AIVw110B1b1rwf+kjIzyZodAoFqqd9nVdGQ7AtjeAtKz7PShS5BISToU a4CfxS0rjO6kBj5+
X-Received: by 10.107.190.194 with SMTP id o185mr10860595iof.287.1501284349216; Fri, 28 Jul 2017 16:25:49 -0700 (PDT)
Received: from [192.168.0.108] (47-36-65-40.dhcp.reno.nv.charter.com. [47.36.65.40]) by smtp.gmail.com with ESMTPSA id 202sm2731503itx.24.2017.07.28.16.25.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 16:25:48 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Fri, 28 Jul 2017 16:25:46 -0700
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, Ted Lemon <mellon@fugue.com>
CC: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, "Brzozowski, John" <John_Brzozowski@comcast.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <3A2839E4-EAB9-41A1-83DA-B91F98606549@gmail.com>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CAA=duU1y8y97f6fBau-g2Oc8uuzmoQMbb96di3HEqjv+Vo6_AA@mail.gmail.com>
In-Reply-To: <CAA=duU1y8y97f6fBau-g2Oc8uuzmoQMbb96di3HEqjv+Vo6_AA@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3584103948_1202729791"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DG21L0NujA8vhDC1kBYNONnok5w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 23:25:52 -0000

I assume – many of us are in the similar situation, especially those who use VPN access to their enterprises.

I’m all for v6 everywhere, however, in order to support those, who can’t be on v6, separate SSID should be provided, perhaps would be good to remind all IETF attendees – test your stuff on v6 only network, otherwise you might be out of luck in the future. Singapore however wouldn’t be the right point in time to switch v4 off completely.

 

My 0.2

 

Cheers,

Jeff

 

From: ietf <ietf-bounces@ietf.org> on behalf of "Andrew G. Malis" <agmalis@gmail.com>
Date: Friday, July 28, 2017 at 14:41
To: Ted Lemon <mellon@fugue.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, "Brzozowski, John" <John_Brzozowski@comcast.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

 

Ted,

 

As one example, I have a VPN application over which I have no control that I must use to reach corporate resources, including email. I haven’t yet had a chance to try it with V6 and nat64, maybe it’ll work and maybe it won’t. If it doesn’t, I’ll need to use the legacy network, which is currently unencrypted. We would need to include a new SSID for an encrypted v4/v6 network (what we currently deliver on the “ietf” SSID). If that new SSID is provided, then I’ll be OK with the migration.

 

Thanks,

Andy