Re: [nfsv4] New Version Notification for draft-ietf-nfsv4-layout-types-12.txt

Tom Haynes <loghyr@gmail.com> Wed, 25 April 2018 18:28 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 56C5C127869 for <nfsv4@ietfa.amsl.com>; Wed, 25 Apr 2018 11:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 iK_rdfSRbQDh for <nfsv4@ietfa.amsl.com>; Wed, 25 Apr 2018 11:28:46 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::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 7F079127698 for <nfsv4@ietf.org>; Wed, 25 Apr 2018 11:28:46 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id n9so1133805pgq.5 for <nfsv4@ietf.org>; Wed, 25 Apr 2018 11:28:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=CX+tXwO/Fyb6d4jE8jzOZJ6wATZOUNIvM4yEGg6Ztbw=; b=b8rEtywEXUF5tlyecy/jRUhuWFA8orfK4W4Q+V8sb2YZy5zM6caZ+POv+nTxHsoUx1 GJZ6TJZwkGtY215xKrjD/2vw3rxjPIVcF+wh53gVzWQLDy0rle++4oEMjwVJRulhjnXz Lhed1TlQMiBa4rM6VJlOu3kTLr6pr/wWXF6Tb2BKSGNn1A7VNwYvuYivefIx4ikZtRwi zNId1cd28pWNQx7W7i5o75OdddSPxs4aRVQP5nk7YkQhR0BgCr6g2w2T+UQ9588kl0fY rjxj23hWlQkDkknjD5moZDm1Xb/2Rlu7RhIHii0CGZNd4N+saUEwM9hWP3kWWA3kjvTz 9Lww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=CX+tXwO/Fyb6d4jE8jzOZJ6wATZOUNIvM4yEGg6Ztbw=; b=rH4igAvHvvNyeNJluh9PLFbfZKKt8XeHg5l8sP1BjejYAFYd1pGHSszSmCpHO940fK k9ov8gryands0utodwLTBcMF3TTixOUarv83TA+Rs9JmQuE71N4Fr07p/ZZATb0hyIoX sVBN99QvFxcfUrdoPSrpGDp3AC+K00hlr1KqK+x8oPizz8kMrfXf+JRpcn7rL0p2IbUW dZ5F4yNCGqa0VcKSJFz0Hbtr7TUslO6bs/5DQ1DU5bnDDjHynbtYlwGcrKRiwr0hfEOH em0+iRuKSYx+RlmU36X6UvTP20Yd8N/08Amq9r8QMh+r8YBETc6CAirC/fCIU4SQuN5O e/3A==
X-Gm-Message-State: ALQs6tDlNBRH1qSio+jSmbd2hJpYpxbB4okSEUzCaUcgqAGG6a6N6x9A dbyHtSw1NfGK47R6yWX26rI=
X-Google-Smtp-Source: AB8JxZprRC8C8BQdgM0NY9QbkEit3ufcqqaUD+Ar2EamXk6Wc/RIdM5VLcwiU5Ak2LzOx/g2BilvsQ==
X-Received: by 2002:a17:902:76c1:: with SMTP id j1-v6mr5178598plt.284.1524680926084; Wed, 25 Apr 2018 11:28:46 -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 x84sm54621878pfi.160.2018.04.25.11.28.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Apr 2018 11:28:45 -0700 (PDT)
From: Tom Haynes <loghyr@gmail.com>
Message-Id: <5302E57E-0355-4FC3-B868-A6F9C9D965AB@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FC3F0FEE-3C56-40A7-A2A8-AB4BDBF80F93"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Wed, 25 Apr 2018 11:28:44 -0700
In-Reply-To: <099C5324-3FBD-4EB4-BA3D-5A8983025E21@gmail.com>
Cc: NFSv4 <nfsv4@ietf.org>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
References: <152416107200.28684.15531571510439665324.idtracker@ietfa.amsl.com> <F27833FB-0667-4085-AD86-C46BBD2C0C73@gmail.com> <CAKKJt-c9ZtAgVd=qOudN6oLrPpZOu=8HE2hR2MaUhq4gH6Qixw@mail.gmail.com> <099C5324-3FBD-4EB4-BA3D-5A8983025E21@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/qUtJyqn3A-mOcdJumrBwgr8KLy8>
Subject: Re: [nfsv4] New Version Notification for draft-ietf-nfsv4-layout-types-12.txt
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: Wed, 25 Apr 2018 18:28:49 -0000

Both are updated.

> On Apr 19, 2018, at 1:05 PM, Tom Haynes <loghyr@gmail.com> wrote:
> 
> Hi Spencer,
> 
> I’ll review this one (and also do the same for FlexFiles).
> 
> Thanks,
> Tom
> 
>> On Apr 19, 2018, at 12:32 PM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com <mailto:spencerdawkins.ietf@gmail.com>> wrote:
>> 
>> Hi, Tom,
>> 
>> On Thu, Apr 19, 2018 at 1:05 PM, Tom Haynes <loghyr@gmail.com <mailto:loghyr@gmail.com>> wrote:
>> This has the changes per the IESG review process.
>> 
>> This is looking good. I have one last question - did you see Mirja's question about possible use of RFC 8174 boilerplate, since the draft uses both uppercase and lowercase RFC 2119 language (and that's what RFC 8174 is supposed to help with)?
>> 
>> Mirja's review ended up in the mailing list archive at https://www.ietf.org/mail-archive/web/nfsv4/current/msg16137.html <https://www.ietf.org/mail-archive/web/nfsv4/current/msg16137.html>.
>> 
>> Thanks,
>> 
>> Spencer (D)
>>  
>>> Begin forwarded message:
>>> 
>>> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>>> Subject: New Version Notification for draft-ietf-nfsv4-layout-types-12.txt
>>> Date: April 19, 2018 at 11:04:32 AM PDT
>>> To: "Thomas Haynes" <loghyr@gmail.com <mailto:loghyr@gmail.com>>
>>> 
>>> 
>>> A new version of I-D, draft-ietf-nfsv4-layout-types-12.txt
>>> has been successfully submitted by Thomas Haynes and posted to the
>>> IETF repository.
>>> 
>>> Name:		draft-ietf-nfsv4-layout-types
>>> Revision:	12
>>> Title:		Requirements for pNFS Layout Types
>>> Document date:	2018-04-19
>>> Group:		nfsv4
>>> Pages:		16
>>> URL:            https://www.ietf.org/internet-drafts/draft-ietf-nfsv4-layout-types-12.txt <https://www.ietf.org/internet-drafts/draft-ietf-nfsv4-layout-types-12.txt>
>>> Status:         https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layout-types/ <https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layout-types/>
>>> Htmlized:       https://tools.ietf.org/html/draft-ietf-nfsv4-layout-types-12 <https://tools.ietf.org/html/draft-ietf-nfsv4-layout-types-12>
>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-layout-types <https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-layout-types>
>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-layout-types-12 <https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-layout-types-12>
>>> 
>>> Abstract:
>>>   This document defines the requirements which individual pNFS layout
>>>   types need to meet in order to work within the parallel NFS (pNFS)
>>>   framework as defined in RFC5661.  In so doing, it aims to clearly
>>>   distinguish between requirements for pNFS as a whole and those
>>>   specifically directed to the pNFS File Layout.  The lack of a clear
>>>   separation between the two set of requirements has been troublesome
>>>   for those specifying and evaluating new Layout Types.  In this
>>>   regard, this document updates RFC5661.
>>> 
>>> 
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/>.
>>> 
>>> The IETF Secretariat
>>> 
>> 
>> 
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org <mailto:nfsv4@ietf.org>
>> https://www.ietf.org/mailman/listinfo/nfsv4 <https://www.ietf.org/mailman/listinfo/nfsv4>
>> 
>> 
>