IETF Logo Mail Archive

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

Tom Haynes <loghyr@gmail.com> Thu, 19 April 2018 15:27 UTC

Return-Path: <loghyr@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 7F42212DA21; Thu, 19 Apr 2018 08:27:11 -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 K8huL1BcQOnP; Thu, 19 Apr 2018 08:27:09 -0700 (PDT)
Received: from mail-pl0-x232.google.com (mail-pl0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) (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 6C88312DA24; Thu, 19 Apr 2018 08:27:09 -0700 (PDT)
Received: by mail-pl0-x232.google.com with SMTP id z12-v6so3455032plo.1; Thu, 19 Apr 2018 08:27:09 -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=1gqzkHteAXj/awbRPCFIgpUyX0CwVr/KVkStMQ6irc0=; b=DDXdk4ZLJ3wek+5VhYcW8dS5ZZTIS+dfQSSzvYmDY8t4ucuAm7s+V+pJ2x1nHHTW5L 7LtARUBUbnt6Mf4IAP9Mx/RsnFUUlAkhnz7I6J4pPchi04wLSOdgqsRxtRo4v/If3J9+ VMPva5HCSKDepXWZauswK1NrJNSxFiAuTBcrAOLYZusX4j+tDdLRMH/hXqgO4jPOeZwv ZKsQcOB9ELSx1eCPNi96gOnwrzBryCIeP4qQ+cZ1hUHvg7FoTCOjZ5f/UwulfyAPkL5G voo2O35gB8Zvix138itzaXqUgi6uAzxYWiKfUqhHL7Z1qwRbAtsz1BlB+zwAfSr9f5vI MKXw==
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=1gqzkHteAXj/awbRPCFIgpUyX0CwVr/KVkStMQ6irc0=; b=QJzRKmv1+uqRwCMb4TXEnGE/kdaVn/XU3XKvbp0pipTExo42sZAYA3aSRRja1e65Ed QYMTwBNwMwCp2KUoYbhrQ4HASNnGToE2UmK+DW6n9lwP4ZoRlOwUH0hg170Us0SZAljc rR8js2OWkvBI32UdPakOKNSOxk0px3ZGQwKtYJ5/TLLq9yEa3OMEVOBjFaYx76n+6ILS Df14ON8Y5tnnL4prbpuNKCQcdgUAX6bW6jTyuDVAXu54WGX4XQ5Ft+y7YQbwrIlKwWVW kb5d2Qhq8Vkv4o8GWfsKehG60t7W15bptgt6koxH/+3CqNlf7PH02cNB5lbyobp3f5Uq RmNw==
X-Gm-Message-State: ALQs6tBW8jlhG9yfTrE6yQ1TeXYshHbChJ6SjOkJb0MvSXo5uI5Lba2u +rhX4fxddc3OpbCHbYrx7qFNhfL9ZNs=
X-Google-Smtp-Source: AIpwx49EOtX3PZBAI25NP2NKUFuHOh26aouWVgkVm336aFL3G0O25xlmIUpqJfhzKb39ekmuxmgClA==
X-Received: by 2002:a17:902:8c94:: with SMTP id t20-v6mr6522073plo.129.1524151629085; Thu, 19 Apr 2018 08:27:09 -0700 (PDT)
Received: from kinslayer.corp.primarydata.com (63-157-6-18.dia.static.qwest.net. [63.157.6.18]) by smtp.gmail.com with ESMTPSA id k9sm6933330pgo.62.2018.04.19.08.27.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Apr 2018 08:27:08 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Tom Haynes <loghyr@gmail.com>
In-Reply-To: <BBBFA4C1-F24B-42E9-AEAB-3218C476DC51@gmail.com>
Date: Thu, 19 Apr 2018 08:27:07 -0700
Cc: Warren Kumari <warren@kumari.net>, 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-Transfer-Encoding: quoted-printable
Message-Id: <45C038FA-897C-4006-8CAC-40913D8AFD2C@gmail.com>
References: <152389784555.19590.7923299037011745780.idtracker@ietfa.amsl.com> <BBBFA4C1-F24B-42E9-AEAB-3218C476DC51@gmail.com>
To: Thomas Haynes <loghyr@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/e-AayNnYMYqtLYGHyLbMd1fjlzM>
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: Thu, 19 Apr 2018 15:27:11 -0000

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.


> 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...
>> 
>> 
>

v2.23.0 | Report a Bug | By Email