Re: [nfsv4] Virtual meeting scheduling (wasL Re: Network File System Version 4 (nfsv4) WG Virtual Meeting: 2020-07-09)

Brian Pawlowski <beepee@gmail.com> Thu, 09 July 2020 07:05 UTC

Return-Path: <beepee@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C05623A07BD; Thu, 9 Jul 2020 00:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=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 gnJ8CA0bcdkz; Thu, 9 Jul 2020 00:05:00 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 2C4423A07C2; Thu, 9 Jul 2020 00:05:00 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id p1so461419pls.4; Thu, 09 Jul 2020 00:05:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=HymeBiETXTgLseFQdlZdkGzWAMhWu6BnPp0lXG3hcXo=; b=VBcDKpWiXNWjG19rc3i7did5dIs8NK59SbeRfb15DwmFMT1+FFppeKyd1OJhJHxBeR 7qzJ1jyaUCJNU7HKn3xFBFkG1O6erzr30LKBHZZGAsWdP83w6U+O8Cf0yB5AFPJE7D7N 5WkbOgmWfNT9JgcfsvJDDU+dUWt6bsuEKX8BpGqOZJSTVBWczRK0V76sVv5P66ylnILs WR8yr503q9BT32FuL/+0Yz5QTfNnVkkyfGFL/2ITe54dzio4nyjv1sEGZzD0z4asH6qw ARqY/nDtLNEa6CzOOqEzU0Z6dIBkvz+a1QQw4lTrPw5lgHT54e6+2F4BckiiKDu4+NnD Ouqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=HymeBiETXTgLseFQdlZdkGzWAMhWu6BnPp0lXG3hcXo=; b=tMEUADpsaUjgy77GLIM8dvJi+pHfkd8kj/LUJ5VtkwT5Od0SRRCLDTWRQGq5u5vs6Q HvF1Sk21fgkFroEVsVOA4SbLZhyTr6aKiKjLV0vUZaIXNY7p2Y4++CbfZazDDVC1GYky zXs9DnuZe7NF15lTfE2AKqdXiTMF68YmOy6OTfyztDd154zu6GzuDt/US4IyUUZ2KlXe 5sZhnqk1WzqBFAUhkpJRSQo2MrOiDsnQoxBblhVkLPwzsdCaa5vMTFnzX5qkXR73xNmd Gpk6SzRVwOeCjUubAWhFRNa/v1FVWZ+Klm144phkw1IDUaj0V+noOFnrkY8IUIyPHHOC SwjA==
X-Gm-Message-State: AOAM53054Bnm5ehEo82NHngCLltrNRzmbpaqmep1ujOuqAPZ8XYRVpwH AcSULEtOpcjd6sIjPHr/VOo=
X-Google-Smtp-Source: ABdhPJwKI/blPKGBfBc7l86eG0m5WVyW3BPSiavLmikn5Auzj7q5HtNnEx5DYaoYmpknE6UX4l8hXQ==
X-Received: by 2002:a17:902:d704:: with SMTP id w4mr14668504ply.278.1594278299571; Thu, 09 Jul 2020 00:04:59 -0700 (PDT)
Received: from [192.168.1.246] (c-24-6-14-119.hsd1.ca.comcast.net. [24.6.14.119]) by smtp.gmail.com with ESMTPSA id h9sm1649010pfk.155.2020.07.09.00.04.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 09 Jul 2020 00:04:58 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Brian Pawlowski <beepee@gmail.com>
In-Reply-To: <20200709070215.GA58025@faui48f.informatik.uni-erlangen.de>
Date: Thu, 09 Jul 2020 00:04:57 -0700
Cc: David Noveck <davenoveck@gmail.com>, John C Klensin <john-ietf@jck.com>, IESG Secretary <iesg-secretary@ietf.org>, NFSv4 <nfsv4@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Message-Id: <3348AC0E-07D0-4D17-A1F3-96E803206AB0@gmail.com>
References: <20200709070215.GA58025@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: iPhone Mail (17F80)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/T6mJudB6n3Jdg9kt4npoz6Gd6Pk>
Subject: Re: [nfsv4] Virtual meeting scheduling (wasL Re: Network File System Version 4 (nfsv4) WG Virtual Meeting: 2020-07-09)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2020 07:05:02 -0000

👍🏻

On Jul 9, 2020, at 00:02, Toerless Eckert <tte@cs.fau.de> wrote:

On Wed, Jul 08, 2020 at 11:05:33PM -0400, David Noveck wrote:
>> There is an obvious matter of principle
> 
> It is it not clear to me what principle you are referring to.

Probably https://www.ietf.org/how/meetings/interim

I am surprised the tooling lets you create an interrim meeting without
the standard 4 week headway.

The obvious workaround for expedience is that any group of people can
always have an informal, not IETF "blessed" meeting.

Given how actual WG decisions have to be made on the mailing list anyhow,
the only difference between any such informal and official (virtual/side)
meeting are IMHO really only the processes. For better or worse.

IMHO, inoffical side meetings are the best way to solve expediency issues.
Just make sure that even more diligence is taken in recording what
happened during such a meeting via notes and spend more time presenting
summary at the next official meeting and allowing a discussion about it then.

Cheers
   Toerless

> because
> 
> 
> people who are
>> interested in the WG's work but might not have been actively
>> participating on its mailing list
> 
> 
> I accept that there are interested people who are not actively
> participating.
> 
> However, I'm having trouble understanding how someone interested in the
> work of the working group can totally avoid reading the working group list.
> Color me skeptical.
> 
> 
> (assuming there more notice on
>> that list)
> 
> 
> It has.
> 
> might not be able to arrange attendance with that
>> sort of notice.
> 
> 
> If there are such people, I want to offer them my apologies.
> 
> Equally important, there has been an extended
>> discussion of some of the directions of NFS on another list that
>> might reasonably justify a summary or discussion on the agenda
>> but presumably cannot be proposed given this short notice.
>> 
> 
> I'm unaware of any such discussion.  The appropriate way to make the
> working group aware of it would be to send mail to the working group list.
> This still should.be done.
> While you might want a slot on the agenda, it might not be available, even
> if you had been reading the working group list when this meeting was first
> discussed.
> 
> If it should have been announced earlier but slipped through
>> that cracks that is regrettable but should still not, at least
>> IMO, be justification for going ahead with a meeting on such
>> short notice.
> 
> 
> My opinion is different.  I cannot see delaying at this point and
> inconveniencing the working group members, who have been preparing for this
> meeting for some time. This is especially so since our AD's vacation
> schedule is such that the next opportunity to meet would be in September.
> 
> 
> 
>> thanks,
>>   john
>> 
>> 
>> 
>> --On Wednesday, July 8, 2020 14:26 -0700 IESG Secretary
>> <iesg-secretary@ietf.org> wrote:
>> 
>>> The Network File System Version 4 (nfsv4) WG will hold
>>> a virtual interim meeting on 2020-07-09 from 09:00 to 11:00
>>> America/Los_Angeles (16:00 to 18:00 UTC).
>>> 
>>> Agenda:
>>> 
>>> Who Time MS Doc Description
>>> D. Noveck 5 min. N/A Introduction including NOTE WELL.
>>> D. Noveck 5 min. N/A Agenda bashing.
>>> S. Faibish 20 min. Yes. ? Discussion of progress and plans for
>>> standards-track document describing use of NVMe  in connection
>>> with pNFS. D. Noveck 5 min. N/A Discussion of overall process
>>> for rfc5661bis. 5 min 2/2021 I-D Discussion of revised
>>> internationalization document (for all minor versions) to be
>>> referenced by rfc5661bis. 20 min. WBD
>>> I-D Discussion of needed changes for new NFSv4 security
>>> approach. 5 min. WBD No. Discussion of plans and status for a
>>> revised NFSv4.1 specification. 5 min N/A Summary of current
>>> decisions and actions necessary to move forward. C. Lever 15
>>> min. 12/2020 Yes. Discussion of status and possible remaining
>>> issues for RPC-over-RDMA v2. S. Faibish 15 min. TBD I-D
>>> Discussion of proposed storage compression attributes and
>>> associated implementation plans. D. Noveck 10 min. N/A
>>> Discussion of issues with client caching of directories
>>> concerning how the directory entry cookies and ordering are
>>> to be managed, both in the same-client and other-client cases.
>>> D. Noveck 5 min. N/A Review of document and milestone status.
>>> 
>>> Information about remote participation:
>>> https://ietf.webex.com/ietf/j.php?MTID=mef56921edfe5a931dedf78
>>> 51b1507ebf
>>> 
>>> This is supposed to be scheduled for July 9 (tomorrow) -
>>> sorry, something went wrong.
>>> 
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>> 
>> 
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfsv4
>> 

-- 
---
tte@cs.fau.de

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4