Re: [v6ops] IETF 103 meeting planning

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 13 September 2018 23:46 UTC

Return-Path: <prvs=1794e86a39=jordi.palet@consulintel.es>
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 B764212008A for <v6ops@ietfa.amsl.com>; Thu, 13 Sep 2018 16:46:08 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 1IoT64gAURWM for <v6ops@ietfa.amsl.com>; Thu, 13 Sep 2018 16:46:06 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AF2A129C6B for <v6ops@ietf.org>; Thu, 13 Sep 2018 16:46:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1536882363; x=1537487163; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=abHWRWJj m24enmace4m0GMv2msUUFCkLoLRuSzhFSg8=; b=gPmk0GveFFpWln8VB+JjAxrA x4/KFSaG2O7Sh+tvfEM0UclxH4J1cOc3T2NSvLZ4hrOXFZYRK7AnxYBaVzmPXAFT 3uB/dkRhPWtPZxZWOlHVQuRrceBeN6olF9yfAhR6k90kSziW10rKZKrzynSCt0FC 0i7N4blQ7PdFat/UluA=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Fri, 14 Sep 2018 01:46:03 +0200
X-Spam-Processed: mail.consulintel.es, Fri, 14 Sep 2018 01:46:03 +0200
Received: from [172.16.188.4] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50005878758.msg for <v6ops@ietf.org>; Fri, 14 Sep 2018 01:46:01 +0200
X-MDRemoteIP: 10.8.10.10
X-MDHelo: [172.16.188.4]
X-MDArrival-Date: Fri, 14 Sep 2018 01:46:01 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1794e86a39=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Fri, 14 Sep 2018 10:45:43 +1100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <36F6603F-D589-4EE1-99F2-15E05E591EC2@consulintel.es>
Thread-Topic: [v6ops] IETF 103 meeting planning
References: <153687556514.29625.12933889270084668897.idtracker@ietfa.amsl.com> <7CEF9C90-C47A-4711-8384-B1C579965ED7@gmail.com>
In-Reply-To: <7CEF9C90-C47A-4711-8384-B1C579965ED7@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/NDwvFn3j-uJ0HTCTQrwlojJv_3k>
Subject: Re: [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 23:46:09 -0000

Hi Fred, all,

I agree that it will be good to adopt draft-byrne-v6ops-dnssecaaaa as a BCP/WG item.

Regarding the one week per draft. I think is good, but I also think that from time to time, if a document is not getting inputs, it may be because people is busy with their own daily work, and the option is to repeat that after a few weeks. A kind of rolling list among the different documents.

We had several documents that got no inputs at a given moment, and when we tried again after some weeks, they got comments.

Regards,
Jordi
 
 

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Fred Baker <fredbaker.ietf@gmail.com>
Responder a: V6Ops Chairs <v6ops-chairs@ietf.org>
Fecha: viernes, 14 de septiembre de 2018, 9:31
Para: V6 Ops List <v6ops@ietf.org>
CC: Ron Bonica <ron@bonica.org>
Asunto: [v6ops] IETF 103 meeting planning

    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...
    
    _______________________________________________
    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 exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.