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

Jen Linkova <furry13@gmail.com> Mon, 17 July 2017 08:30 UTC

Return-Path: <furry13@gmail.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 6F601131A88 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 01:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=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 luYohhReJr3L for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 01:30:48 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 F1146131798 for <v6ops@ietf.org>; Mon, 17 Jul 2017 01:30:47 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id z62so39416885ioi.3 for <v6ops@ietf.org>; Mon, 17 Jul 2017 01:30:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=mcLi89MwCkwunuuEMK0UnQwT6P/j8wDm5OEl1h3FAho=; b=P8PBW0OpmOjp1eHjFMa5TzkbJK7DylQ9RfTYgbtaKSu/PN67iBkejPn2LJMGxwc7uj 2YtNCOuFkzO7FRWb7KttHN9NovcHoFL5KnSQgeE6BLP8JC6ttQ2r1zkBgpuM/SCxJ3Yw W4dHov1dZdMNXjZwMQq/Yd/Ngmt3YMyJuFp41klLFhXbJci/DlfysZZiWWzbUezV4zzN LXCw4PmcczJvC9L27Qc8E5moAvuSLmIEuLOwYsEKl4aj598u1eaGqOKgvXOEo5BErhXj +Q0pEI6n7YQ2hHM5Tw2YLKC71UU+ByrZD7FY7NxcxO8zEO0HEqG8TjwC7/571ZVj35iV ieag==
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:content-transfer-encoding; bh=mcLi89MwCkwunuuEMK0UnQwT6P/j8wDm5OEl1h3FAho=; b=p2Bd0vQz3KyFpluVDm0JgAoYYLk8DS1eTXd5EMbiRsSjxwGuHvWe5NWjkUPG0mNaTn gcuhaQ8xC6yzFwuWxpUQi65XzpjyX2HlJPSTQqSWw+4zabDTB3mkyPV9IuhY+oeGaaqS 6MpLpoXVZHaaH6k243VVVh3siLwaIlw55bX9VO8Ai9mA6QwXNugWo47AIe7T8/6YwYu1 VgDcJC+OHLUWdq8sy9YcWQtLN//GKLu2J8oMmCUMP+U5n4UldPZ4n/1fgRpJG/Hyik5a aUK1MBNzFC5no0PrTqWF3KCbZK1hGEsQ9WPk9EER/yqZIVVQwwe2x+3phdiLZbdpQSsn L1qA==
X-Gm-Message-State: AIVw112ldPvkaABU0F3pQINGmm9IUF0IWV7LfdJAg1ldOidcdIUMnKnz uZJ/tyhkByCWtDP7RRcZM3UH2NxsaQ==
X-Received: by 10.107.137.161 with SMTP id t33mr18086639ioi.181.1500280247311; Mon, 17 Jul 2017 01:30:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.55.215 with HTTP; Mon, 17 Jul 2017 01:30:26 -0700 (PDT)
In-Reply-To: <7643C1DC-76A3-4652-9BB1-D0D42801F37E@consulintel.es>
References: <7643C1DC-76A3-4652-9BB1-D0D42801F37E@consulintel.es>
From: Jen Linkova <furry13@gmail.com>
Date: Mon, 17 Jul 2017 18:30:26 +1000
Message-ID: <CAFU7BASvuj+JrsSZzUKauBsph4hdr+ZdVjkg0_Q+00Spm5PJoQ@mail.gmail.com>
To: Jordi Palet Martinez <jordi.palet@consulintel.es>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Jim Martin <jim@daedelus.com>, Russ Housley <housley@vigilsec.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, Alissa Cooper <alissa@cooperw.in>, Randy Bush <randy@psg.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hC0O5Z9UDqVNs1B8V1iAtifyrZA>
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 08:30:50 -0000

On Mon, Jul 17, 2017 at 3:24 PM, JORDI PALET MARTINEZ
<jordi.palet@consulintel.es> wrote:
> In my opinion such kind of experiment should be only done once we approve the document as RFC, note before, so by the next IETF meeting (hopefully).

I'm not sure I understand the logic here.
The I-D is documenting the operational experience and actually I
believe it would make more sense to run the experiment *before*
finalizing the text/publish it as RFC to avoid the situation when  we
publish an RFC on smth we have not even done yet.

> We like it or not, this is not a valid option, unless we make sure that if some participants have troubles, the alternative SSIDs have other 2.4 and 5 GHz radios available. Is that the case?

I believe the draft clearly states the the fallback option needs to be
available.

> The way you’re proposing, will mean that many folks may switch to alternative SSID, or simply don't report those failures, so at the end you don’t have any results of how much is not working, etc.

Actually if the fallback dual-stack network requires an explicit
configuration on the client side (as the draft recommends) to avoid
users connecting to it accidentally, the number of clients falling
back to the dual stack SSID is very good data point to demonstrate
what % of users are experiencing issues.

> De: v6ops <v6ops-bounces@ietf.org> en nombre de "Brzozowski, John" <John_Brzozowski@comcast.com>
> Responder a: <John_Brzozowski@comcast.com>
> Fecha: lunes, 17 de julio de 2017, 6:23
> Para: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>
> CC: Jim Martin <jim@daedelus.com>, Alissa Cooper <alissa@cooperw.in>, Russ Housley <housley@vigilsec.com>, Randy Bush <randy@psg.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
> Asunto: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>
>     Folks,
>
>     Apologies in advance for the gratuitous cross posting (v6ops, ietf, ipv6, sunset4, softwires).  I hope, to you all, this is worth the added email.
>
>     The draft below was written to provide the necessary documentation to enable the IETF (the NOC, participants, etc.) to migrate to an IPv6 only primary network connection (Wi-Fi and wired) that utilizes NAT64+DNS64 to access IPv4 only content.  The request for IETF 99 has been to have the primary “ietf” SSID adhere to what is documented in the I-D below.  I trust the motivation is understood.  This means that the main “ietf” SSID would be switched to be IPv6 only with NAT64+DNS64 (at layer 3) per the I-D below.  Given the that IETF99 is upon us, this may or may not be entirely possible.
>
>     At this stage, the infrastructure preparations for IETF 99 should be in place to ensure that the IETF has the necessary hardware for redundancy and performance.
>
>     So, we are all seeking your input.  Given the above, what would all you suggest is tolerable for IETF99 as it pertains to the I-D below?
>
>     • IPv6 only per the I-D for the balance of IETF week?
>     • IPv6 only per the I-D for one or more days this week?
>     • IPv6 only per the I-D for the plenary?
>     • IPv6 only per the I-D for the next IETF meeting?
>
>     Please send us your feedback.
>
>     Regards,
>
>     John
>     +1-484-962-0060
>
>     -----Original Message-----
>     From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>     Date: Saturday, July 1, 2017 at 03:04
>     To: Marcus Keane <marcus.keane@microsoft.com>, Jen Linkova <furry@google.com>, Lorenzo Colitti <lorenzo@google.com>, John Brzozowski <John_Brzozowski@Cable.Comcast.com>, Erik Kline <ek@google.com>, John Brzozowski <John_Brzozowski@Cable.Comcast.com>, David Schinazi <dschinazi@apple.com>, Stuart Cheshire <cheshire@apple.com>, Jen Linkova <furry@google.com>, Paul Saab <ps@fb.com>, David Schinazi <dschinazi@apple.com>
>     Subject: New Version Notification for draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt
>
>
>         A new version of I-D, draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt
>         has been successfully submitted by John Jason Brzozowski and posted to the
>         IETF repository.
>
>         Name:           draft-jjmb-v6ops-ietf-ipv6-only-incremental
>         Revision:       00
>         Title:          Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>         Document date:  2017-06-30
>         Group:          Individual Submission
>         Pages:          15
>         URL:            https://www.ietf.org/internet-drafts/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt
>         Status:         https://datatracker.ietf.org/doc/draft-jjmb-v6ops-ietf-ipv6-only-incremental/
>         Htmlized:       https://tools.ietf.org/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00
>         Htmlized:       https://datatracker.ietf.org/doc/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00
>
>
>         Abstract:
>            The purpose of this document is to provide a blueprint and guidance
>            for deploying IPv6-only Wi-Fi at IETF meetings.  This document
>            outlines infrastructure and operational guidance that operators
>            should consider when deploying IPv6-only networks using NAT64 and
>            DNS64 to support communication to legacy IPv4-only services.
>
>
>
>
>         Please note that it may take a couple of minutes from the time of submission
>         until the htmlized version and diff are available at tools.ietf.org.
>
>         The IETF Secretariat
>
>
>
>
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org
>     https://www.ietf.org/mailman/listinfo/v6ops
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



-- 
SY, Jen Linkova aka Furry