Re: [nfsv4] Warren Kumari's No Objection on draft-ietf-nfsv4-layout-types-10: (with COMMENT)

Warren Kumari <warren@kumari.net> Fri, 20 April 2018 17:12 UTC

Return-Path: <warren@kumari.net>
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 ED23112D87F for <nfsv4@ietfa.amsl.com>; Fri, 20 Apr 2018 10:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 ZwQoav4wO1Df for <nfsv4@ietfa.amsl.com>; Fri, 20 Apr 2018 10:12:00 -0700 (PDT)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 D5AE8124319 for <nfsv4@ietf.org>; Fri, 20 Apr 2018 10:11:59 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id z73-v6so24833426wrb.0 for <nfsv4@ietf.org>; Fri, 20 Apr 2018 10:11:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WBnxbpoT1BepQ3k2O5HA9ag/XRxL7RgMVg9QNqxN6Gs=; b=c5lHTgymxHME6M3kL9hx8QiIfLzzGh5r+n1PwiZ6/Qsda4U3H2gKhTa4/YRNewdy6b O44rhiOZ1IYni1wPt0J2brcQW3xrFfVLKEXOL+yS2OARmXmc0/WGzJLyHAOpjnd/8GSd 7i90qbE3rRKVzHe21N6lv63uUD0zFttBHKhJZ6MtsEmTLojdHcBVyRGJ6fsrd8lZKRG8 bkYwMqH3HlncziofcENQidmSbTW3iXxrlooCCPC78hsnDJ8WYM6B+Yz3eDD1QlUVL7ax /PJwnbj4wmqUjoOz6sfj079rqHa5Ur7a+nIvXEl0D1cs1vvjOwGrdxXBmGWWCVLOVlYQ XsLw==
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; bh=WBnxbpoT1BepQ3k2O5HA9ag/XRxL7RgMVg9QNqxN6Gs=; b=nmLrKlm1AH4VVyXkZcB7Mr29zbUKLxkCY2m279aN7rcAYVjGBV7ZYXelaWkWs8U4yX vL/VySpwgDIBRtPZvhitySYr5DQ59s3SBdp0CX0+VuTLFlj+ugh0Yvvl+qm/7RTddkSV FXHtd12/r/J30gjUBbmABE8V8gvPAVSC1f/TdS3TDJdJbKb9zi0wVYlmsYPD/uS70pQR mnetgN3N2nhwbLo8FK8zzWsgcKmGWCgj3RZtml9hnkswkV1Ko59Z0u/LGugG3M6MfgOe +bCaIeSPL9WktNBT8i0kFW8gKslTHhy5+ctK8QeidKujSCx4wnuUGN5cRL1ZbiFdqmsd PAbw==
X-Gm-Message-State: ALQs6tADtHKDXvqkGsEhfB89l3MQrCGmM+LSXdVRh9fB53l1GvxydMZc Nylwff2ujH9T639JiXTDFqBaaOwF0pbjeZvqe4T6RA==
X-Google-Smtp-Source: AB8JxZq2itdQhxlmjfQnfGU4mzr6ZuH0HraBHHHboTg9REoyNkS52dRTAKeiu/OgbtXiKVUwCpVwmcxSKOWtyWq2XWs=
X-Received: by 10.28.109.80 with SMTP id i77mr2389013wmc.46.1524244317966; Fri, 20 Apr 2018 10:11:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.197.138 with HTTP; Fri, 20 Apr 2018 10:11:17 -0700 (PDT)
In-Reply-To: <45C038FA-897C-4006-8CAC-40913D8AFD2C@gmail.com>
References: <152389784555.19590.7923299037011745780.idtracker@ietfa.amsl.com> <BBBFA4C1-F24B-42E9-AEAB-3218C476DC51@gmail.com> <45C038FA-897C-4006-8CAC-40913D8AFD2C@gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Fri, 20 Apr 2018 13:11:17 -0400
Message-ID: <CAHw9_iJrkja8oma4P6bDiv_YVPbZyVtroVivbSA5fPMVWv+YMQ@mail.gmail.com>
To: Tom Haynes <loghyr@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-nfsv4-layout-types@ietf.org, nfsv4-chairs@ietf.org, Spencer Shepler <spencer.shepler@gmail.com>, nfsv4@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/DqhArfqgfswc-AN5A2JQOFwJbw0>
Subject: Re: [nfsv4] Warren Kumari's No Objection on draft-ietf-nfsv4-layout-types-10: (with COMMENT)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 20 Apr 2018 17:12:03 -0000

On Thu, Apr 19, 2018 at 11:27 AM, Tom Haynes <loghyr@gmail.com> wrote:
> Hi Warren (and likewise Dave),
>
> I went with:
>
>    control communication requirement:  is the specification for
>       information on layouts, stateids, file metadata, and file data
>       which must be communicated between the metadata server and the
>       storage devices.  There is a separate set of requirements for each
>       layout type.
>


Nice! Thank you...

W

>
>> On Apr 16, 2018, at 4:34 PM, Tom Haynes <loghyr@gmail.com> wrote:
>>
>> Thanks Warren, Ill try to clean it up.
>>
>>
>>> On Apr 16, 2018, at 9:57 AM, Warren Kumari <warren@kumari.net> wrote:
>>>
>>> Warren Kumari has entered the following ballot position for
>>> draft-ietf-nfsv4-layout-types-10: No Objection
>>>
>>> When responding, please keep the subject line intact and reply to all
>>> email addresses included in the To and CC lines. (Feel free to cut this
>>> introductory paragraph, however.)
>>>
>>>
>>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>>> for more information about IESG DISCUSS and COMMENT positions.
>>>
>>>
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layout-types/
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>>
>>> Thank you for this.
>>>
>>> I had one readability issue -- I find:
>>> " control communication requirements:  are for a layout type the
>>>     details regarding information on layouts, stateids, file metadata,
>>>     and file data which must be communicated between the metadata
>>>     server and the storage devices."
>>>
>>> to be very hard to read. I tried for a while to break this up into multiple
>>> sentences but was unable. It would be nice if the authors could succeed where I
>>> failed...
>>>
>>>
>>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf