IETF Logo Mail Archive

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

Tom Haynes <loghyr@gmail.com> Thu, 19 April 2018 20:05 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 351AA12DA6F for <nfsv4@ietfa.amsl.com>; Thu, 19 Apr 2018 13:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=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 N6Vl9kAyUJLT for <nfsv4@ietfa.amsl.com>; Thu, 19 Apr 2018 13:05:43 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (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 73C2212DA6D for <nfsv4@ietf.org>; Thu, 19 Apr 2018 13:05:43 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id p15so3145786pff.11 for <nfsv4@ietf.org>; Thu, 19 Apr 2018 13:05:43 -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=pJf6JLdSLi4k2c3DCv4wmdU9r8G52g53DYqrMJQq3Hs=; b=SL3CinfXXjmYXXxCHbnpjM+P5YQsiil/WKaQ2N/R1DUFJ3CiRMkws+3PlY8bHEFMGH FxX/J9fM62VZ8S/nLDAQ+MIVOUx3VccmT+4c++QZYtiRPoi+bn97vEhPPaAotOhAx6xZ xR8sSRKTZspQ6xOc+BbWWhK8n1fZfGsRTA1UjHcv7h7krTpfrl3P76WGhYeMvjQKium6 mTfgEIwMb/+V9yxu+dm84FyNeV5RzJ1cjOOIKBklK0Q0ThwCCw5iNkxx2d1BVgVcj5LS JzDVgZmG5/st98CxvHPg2H8RGbfd4JwSzUaRlRUtbx8XAVhsl0QYZRncaUCoKXx16xMc uRfw==
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=pJf6JLdSLi4k2c3DCv4wmdU9r8G52g53DYqrMJQq3Hs=; b=md91A/x3eIDOK6FcunoeYi+JNrlqnMmdiwGr1nOp/Pua6EpKZ56AgkQCkJe7i+ejtj j5YPz9oNlxf9u9uc5EPQP0Adnt+cLKBmxhlbYKXfwagGSf0ZL0c3OGTzWtFQ5nVxwXRF ZKtAXZCDZkG1eF9tJSEimTVC5RAfBgRsXnOFAvvP9E9j5nnBs9NzFWoHa3H3odoSc7Wy JwNJQM7/7rXggvg0Bk8weh0nL9aScNLErVm2Dk7sq3RFgkFzaqH0lmPDLk+btG+3uMHf 5IFa8J5EBFSWEdtwPtCeTlwwznPQA+xkJElZXQZEmJJbRS6+Z22FczCFfhjNFhOs1hu1 DySQ==
X-Gm-Message-State: ALQs6tAdDRAwCyUbafMZAnFHabgIZ8LCIW+vysr9LvqbYydzFBpbQtPb 0sm/ouwgbwLOnYFYMyw07j2laf1zsP8=
X-Google-Smtp-Source: AIpwx493eMVDOmGYtlbwHumL8Gu1QDb1qB/uRe2WzoREAbhBwrXpix3klX7rlv0YIqVwXx6cON1n8g==
X-Received: by 10.167.128.207 with SMTP id a15mr6958443pfn.116.1524168342772; Thu, 19 Apr 2018 13:05:42 -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 e190sm7779985pfe.171.2018.04.19.13.05.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Apr 2018 13:05:42 -0700 (PDT)
From: Tom Haynes <loghyr@gmail.com>
Message-Id: <099C5324-3FBD-4EB4-BA3D-5A8983025E21@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F770AB40-F404-480F-85EF-8FD77E767563"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Thu, 19 Apr 2018 13:05:41 -0700
In-Reply-To: <CAKKJt-c9ZtAgVd=qOudN6oLrPpZOu=8HE2hR2MaUhq4gH6Qixw@mail.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>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/RZJfM6W5w12SkJg8nQYbZ5Pfe-w>
Subject: Re: [nfsv4] Fwd: 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: Thu, 19 Apr 2018 20:05:46 -0000

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

v2.23.0 | Report a Bug | By Email