[v6ops] IETF 103 meeting planning

Fred Baker <fredbaker.ietf@gmail.com> Thu, 13 September 2018 22:30 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 A68E3130E78 for <v6ops@ietfa.amsl.com>; Thu, 13 Sep 2018 15:30:21 -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, 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 1u-EljUuYcz8 for <v6ops@ietfa.amsl.com>; Thu, 13 Sep 2018 15:30:20 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 01D79130DC5 for <v6ops@ietf.org>; Thu, 13 Sep 2018 15:30:19 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id i10-v6so2800124oth.0 for <v6ops@ietf.org>; Thu, 13 Sep 2018 15:30:19 -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:reply-to:message-id :references:to; bh=QzJC4e7Qg3FARoJ9Hf9SvxZpFBKxMdtY7KNFU7M7V0A=; b=QTdTGBVlPeeJ7+BV2AziAf3DoYWFxvT77b4vAxi3gtb4DieZfjckC1efZFSii9Gik9 sCfaoN11Lf0k4v1aQyB33QQwi1TTpxRO9IpltPNhoJk8MDueWkhTKVydRz8NaYE2qQOJ yPF2wR7LwOMEMuV8X7Gn8zYiETXpFsvISQ5aAnx5ShSlIqExj+TLiN9gYekXouUpRvOV 1iyDD0gESpn7c3YLOIUn5cbo8ojCapQgCbbt8w+e7n8JNEkxlcBT8jIxu8dyQSVvUgZn V8bbNidPBgwuTB29D5O8Q1KnvQOAiihffZhdv1H6dXahfa+tKmgAHio80220NxmCaSFp uhQQ==
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 :reply-to:message-id:references:to; bh=QzJC4e7Qg3FARoJ9Hf9SvxZpFBKxMdtY7KNFU7M7V0A=; b=Iqh5WUa5PATmpbA/LeYPGz/nMjKAL4wid7k5z0BejkfBTE5wW1d8YJkplrkAiKwtrU ORvekwoqAW+s+MlU+2ULMD4UNbaF9lqsbLDQsRUEnLI82XZSs2DxsK7r5Ey319am5Rfm 9KhVLQuHnZrqsvxZkwMBkpR0puEvK3xZAfwv0la3kZTnbOsjjV9OFDD7TDaYydfDbEkj qBW3i4ZtYmx8cHuGsJ3o5WNBegOCzwjjQ9T/jcliKIuUkDKTbGRZFSMg6sXjIkFSHAHu mk1l0kUy/ZAdbylj0s3hJg0lvwRI1tzUfpy4uMPD4Kao7+Gr0FxWWKkKeGXE7AlkaFxo f7xQ==
X-Gm-Message-State: APzg51B8fX07+ic6qjtMJoQzDBHRUqNJ2kjzlupUdFvVP+CH9JYbIJx2 mg2jjMMfUJuq5fXDnj/Zzl7Zh8e3
X-Google-Smtp-Source: ANB0VdZDVViA/d3RuZIk0lERyjnTEHjrUoRl7H7CNeFwUN+RP8rk97UBg7m9c/DmCBZLAG4352NiHA==
X-Received: by 2002:a9d:2055:: with SMTP id n79-v6mr2474455ota.379.1536877818183; Thu, 13 Sep 2018 15:30:18 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1073? ([2600:8802:5600:1546::1073]) by smtp.gmail.com with ESMTPSA id q124-v6sm2471756oif.8.2018.09.13.15.30.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Sep 2018 15:30:17 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_C4C94C2D-DCEF-48FA-BFDE-4BDCA92DCB71"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <153687556514.29625.12933889270084668897.idtracker@ietfa.amsl.com>
Date: Thu, 13 Sep 2018 15:30:15 -0700
Cc: Warren Kumari <warren@kumari.net>, Ron Bonica <ron@bonica.org>
Reply-To: V6Ops Chairs <v6ops-chairs@ietf.org>
Message-Id: <7CEF9C90-C47A-4711-8384-B1C579965ED7@gmail.com>
References: <153687556514.29625.12933889270084668897.idtracker@ietfa.amsl.com>
To: V6 Ops List <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jruyYPKqkrqIOF5Q_7u_znl0Hyc>
Subject: [v6ops] IETF 103 meeting planning
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Sep 2018 22:30:22 -0000

FYI, I have requested one meeting for v6ops in November, as follows. Most important might be the clash list; I derived that in part from history and in part from the list of working groups our authors also have work in. I freely admit I may have misprioritized a potential conflict. If you have any heartburn in this, please let Ron and I know to correct it.

One thing that is happening, experimentally, is reducing the meeting days from Monday-Friday to Monday-Thursday, and apparently no longer having 2.5 hour morning meetings (such slots were not presented to me as option). In the past few meetings, we have had a too-packed meeting (in London) and time on our hands (in Montreal). Given the current set of drafts, I expect to have a presentation from CERNET on their IPv6-only experience (which has been ongoing for 10+ years, with IVI/SIIT between their IPv6-only network and their IPv4-only network), an discussion of an updated version of draft-ietf-v6ops-nat64-deployment, and a discussion of an updated version of draft-byrne-v6ops-dnssecaaaa. We'll see what else shakes out between now and November...

Let me pose a question that I think I know the answer to, but per our procedures I need to formally ask. We had several comments during the discussion of draft-byrne-v6ops-dnssecaaaa to the effect that it should be BCP. To accomplish that, I think it should be a working group draft (e.g., we agree to collaborate to make it happen). Do we agree to ask Cameron to resubmit as draft-ietf-v6ops-dnssecaaaa and target BCP status?

While I'm commenting and asking questions, let me ask one more. On several occasions in the past, I have asked the working group to focus on a particular draft and comment on it, with mixed results. Between IETF 101 and 102, and again since IETF 102, we have weekly asked the working group to look at a given draft and comment. That has seemed, to Ron and I, to have worked reasonably well - we have gotten comments on drafts without the noise level that we have seen in the past, and have gotten some pretty clear direction on what should happen with various drafts. One side-effect, not altogether unintended, has been to need less meeting time f2f. We talk about the IETF doing much of its work on mailing lists, but v6ops has had difficulty doing that in the past. I'd like to believe that maybe we have a formula that helps this work better.

What is your opinion of the weekly "let's take a look at X"? Is it helpful to you? Is it a practice you would like to see continue?

On Sep 13, 2018, at 2:52 PM, IETF Meeting Session Request Tool <session-request@ietf.org> wrote:
> A new meeting session request has just been submitted by Fred Baker, a Chair of the v6ops working group.
> 
> ---------------------------------------------------------
> Working Group Name: IPv6 Operations
> Area Name: Operations and Management Area
> Session Requester: Fred Baker
> 
> Number of Sessions: 1
> Length of Session(s):  2 Hours
> Number of Attendees: 70
> Conflicts to Avoid:
> First Priority: rtgwg mboned ipsecme dnsop grow intarea 6man  ippm
> Second Priority: suit tsvwg opsec idr
> Third Priority: 6lo bess bier ccamp ipwave l2sm lsr lsvr mpls netmod nvo3 opsawg quic sfc teas
> 
> 
> People who must be present:
>  Fred Baker
>  Ron Bonica
>  Warren &quot;Ace&quot; Kumari
> 
> Resources Requested:
> 
> Special Requests:
> 
> ---------------------------------------------------------
> 

--------------------------------------------------------------------------------
The fact that there is a highway to hell and a stairway to heaven is an interesting comment on projected traffic volume...