Re: [v6ops] Outcomes from v6ops@IETF98

Fred Baker <fredbaker.ietf@gmail.com> Sun, 02 April 2017 16:51 UTC

Return-Path: <fredbaker.ietf@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 B27031294B7 for <v6ops@ietfa.amsl.com>; Sun, 2 Apr 2017 09:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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=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 BlVP4eRfpHJt for <v6ops@ietfa.amsl.com>; Sun, 2 Apr 2017 09:51:35 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::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 31D0A1294B8 for <v6ops@ietf.org>; Sun, 2 Apr 2017 09:51:33 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id s16so23475432pfs.0 for <v6ops@ietf.org>; Sun, 02 Apr 2017 09:51:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=69T8Awey34Wpau6Of/s/VXK5e/Kc/oJ4+qkwoL1Bi4M=; b=LftoXgtZ3Svzp5B4MZYADWIl9jzA0bhVQbgba8tl4SmMCB/1MkJISCp9ARqwrueNNb HliSa6LGGA2XmCdrQ23+0dZTY/rMe6ZLe5AgXd5tD0cFPNXRzm6Y50d7Ia6ZkspCaDkR b4YPYua0xo1LW2k7/1RVZBCqEfkiQG3iq3GxZXyWGDAm7fxYoMKhNB7kpasaHVu8TabI vKwP5koYYWoZJZ1IK8c2u9meVCn2w9/iTvvP+jI8JiJ1KW2+UsorvxmJ4t7oKnxtMOLp LjABg64SRDwIayxpTQHAKRaj5Te3bEogqYaq5dEpRHOccOxmc1DybhWOtMIb1BCY66tT urRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=69T8Awey34Wpau6Of/s/VXK5e/Kc/oJ4+qkwoL1Bi4M=; b=M9fsX7b30PjdvZ/SCH/NXfLKx1fsXycO0fz2kTz/coCw6A0Aq2oqHYidsxK96y0HWc KXLlFckOeE144/lZrn/Lk6r5FHrNfwd3INvuH4M2DOsvvz0k7A2m7bMd8D7HnBWXnnjz jk87ugHP8exzlSiYtNSQg9/6QNSBgTyxx3y9HJA5F+pXahmmcf4UTcmcTMTbibT4Eptz Gy3b2jelXViPxrse6PhfqZKFDF4UJe5thvvu5khoku7G0pAV5/4Sm0F38BlOkAwzGqHj yklBoHpuv+d+Et0YPPTFlJmxeqd0jcvtZNmcLZSWqN+KvtrFD4VJ7r0kXtMNd1T4soPm Si/Q==
X-Gm-Message-State: AFeK/H1P9V1Ue+STHrJYrdS1L8WLfGLe6tVrxz3mcA2Rw7YO0oiiHLRZlCpDbEsLgv28BQ==
X-Received: by 10.99.55.78 with SMTP id g14mr13299871pgn.191.1491151892761; Sun, 02 Apr 2017 09:51:32 -0700 (PDT)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id b74sm21020278pfd.90.2017.04.02.09.51.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Apr 2017 09:51:31 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <F6384322-279F-4B23-8476-87C930B2ED35@jisc.ac.uk>
Date: Sun, 02 Apr 2017 09:51:33 -0700
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, v6ops list <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D42FD608-22CA-4ADD-A0ED-CC88DF3BE07B@gmail.com>
References: <6C1E351B-F8B6-4BC2-890D-993A1F081226@gmail.com> <8365a4e0-d317-ed3c-59b3-2e829ff210f3@gmail.com> <F6384322-279F-4B23-8476-87C930B2ED35@jisc.ac.uk>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/n6HOo3g0eNctION1YisciipVBiQ>
Subject: Re: [v6ops] Outcomes from v6ops@IETF98
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: Sun, 02 Apr 2017 16:51:38 -0000

> On Apr 1, 2017, at 4:41 PM, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
>>> One question I intended to ask and didn't get to was the appropriateness of an interim meeting, perhaps in mid-May. It would primarily address draft-ietf-v6ops-ula-usage-considerations and draft-petrescu-v6ops-ipv6-power-ipv4, and potentially draft-ietf-v6ops-design-choices if it is updated. There is an argument for leaving these to IETF 99, and potentially booking a second slot for that discussion. Your opinions?
> 
> Seconded. Is the intention a physical or virtual meeting, or both?

I was thinking in terms of webex or equivalent, somewhere in May 8-18. If folks want to have a meeting, I have to announce it 30 days in advance, which means I'll send a doodle poll and we'll figure out when to have it during this coming week. To my small mind, June is late enough that we may as well delay for July.

My *guess* at an agenda in July includes
    draft-ietf-v6ops-ula-usage-considerations if needed
    draft-ietf-v6ops-design-choices if updated and needed
    draft-petrescu-v6ops-ipv6-power-ipv4 if needed

    draft-ietf-v6ops-happy-eyeballs-update
    draft-ietf-v6ops-rfc7084-bis
    draft-ietf-v6ops-ipv6rtr-reqs

Plus possible additional work submitted between now and then. Note the "if needed"; they might be an argument for a second slot if we don't have an interim meeting, and if we do have one, would only be on the agenda if updated and there is working group interest.

If you look at https://tools.ietf.org/rfcdiff?url2=draft-ietf-v6ops-ula-usage-considerations-02.txt, you will see that the authors have done some pretty heavy-duty changes to the document. I think the question would be (and this could be in email or verbally) what additional changes people would like to see. I'd invite a thorough review of the document as it stands. I'll note that "let's deprecate ULA or tell people to never use it" doesn't fit with current operational practice; when my phone is not attached to a WiFi, the DNS address my provider offers me is a ULA address. "Don't NAT", fine, but "don't ULA" as a blanket statement is inconsistent with operational practice in some providers, and "ULA implies NAT" is just silly. It implies that the systems so addressed are not normally advertised in BGP, nothing more and nothing less.

draft-petrescu-v6ops-ipv6-power-ipv4 is a brand new draft, slipped in just under the wire. The first question is whether the working group is interested; there wasn't time for that discussion to happen before IETF 98. If we ARE interested, what do we think of it?

draft-ietf-v6ops-design-choices didn't get updated for this meeting, and sooner or later will simply drop off radar. Folks have periodically said that they find it interesting and potentially useful, but the authors have largely run out of steam. So at least part of the question is "what is the future for this draft?".