Return-Path: <tigran.mkrtchyan@desy.de>
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 AAA6D12F280
 for <nfsv4@ietfa.amsl.com>; Tue, 25 Jul 2017 01:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.297
X-Spam-Level: 
X-Spam-Status: No, score=-4.297 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001,
 URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=desy.de
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 J2wXYojhOhry for <nfsv4@ietfa.amsl.com>;
 Tue, 25 Jul 2017 01:14:02 -0700 (PDT)
Received: from smtp-o-3.desy.de (smtp-o-3.desy.de
 [IPv6:2001:638:700:1038::1:9c])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id ABC0C127978
 for <nfsv4@ietf.org>; Tue, 25 Jul 2017 01:14:01 -0700 (PDT)
X-Clacks-Overhead: GNU Terry Pratchett
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp-o-3.desy.de 0B16C28025E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=desy.de; s=default;
 t=1500970439; bh=MOKgY2YwqEzAeJ/bvFxtxSxTkBsMr+Dhl7v4HJyRxnw=;
 h=Date:From:To:Cc:In-Reply-To:References:Subject:From;
 b=PpF/ChsNqC1eJB4e7k23gCLOC9jfrBRz8B9xBJG+i7dun3CBr6AS8zfMbl1ApCEzR
 mVz2m8ayIcSkBR1Cp1tFcP5pSL3BWLJOcIQNWSN3UZRu2wcDyK7RQ5nCx2eFZ5PiJe
 8PrpDl/ZUi79CWR6bjJ7nMXfsywSbjo//9KYs+v4=
Received: from smtp-map-3.desy.de (smtp-map-3.desy.de [131.169.56.68])
 by smtp-o-3.desy.de (DESY-O-3) with ESMTP id 0B16C28025E
 for <nfsv4@ietf.org>; Tue, 25 Jul 2017 10:13:59 +0200 (CEST)
X-Virus-Scanned: amavisd-new at desy.de
Received: from z-mbx-2.desy.de (z-mbx-2.desy.de [131.169.55.140])
 by smtp-intra-1.desy.de (DESY-INTRA-1) with ESMTP id 608F03E901;
 Tue, 25 Jul 2017 10:13:57 +0200 (MEST)
Date: Tue, 25 Jul 2017 10:13:57 +0200 (CEST)
From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Thomas Haynes <loghyr@primarydata.com>
Cc: NFSv4 <nfsv4@ietf.org>
Message-ID: <636807134.724761.1500970437094.JavaMail.zimbra@desy.de>
In-Reply-To: <3D63CFB2-D6EC-4BD5-A735-724329A6252A@primarydata.com>
References: <3D63CFB2-D6EC-4BD5-A735-724329A6252A@primarydata.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="=_e7fab3a6-017d-4825-a422-9de5040c55ab"
X-Mailer: Zimbra 8.7.6_GA_1776 (ZimbraWebClient - FF54 (Linux)/8.7.6_GA_1776)
Thread-Topic: Request for WG Last Call
Thread-Index: AQHTAU9em+wT10r5nkCwg6O4xmmSZwf/Ut00
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/n1uaBhA341zxQlOD8CQibsM_SCo>
Subject: Re: [nfsv4] Request for WG Last Call
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: Tue, 25 Jul 2017 08:14:05 -0000

--=_e7fab3a6-017d-4825-a422-9de5040c55ab
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi Tom, 

some typos: 

page 6: 
" A client presenting the 
wrong credential for the deisred access will get a NFS4ERR_ACCESS 
error." deisred -> desired 

page 7: 
"that would never be used to grant acccess." acccess -> access 

page 9: 
"OPEN_DOWNGRADE and CLOSE only require local execution on the 
metadata sever." sever -> server 

page 10: 
"2.3.2. Tighly Coupled Locking Model" Tighly -> Tightly 

"of the association between the metadata-sever-chosen stateid and" metadata-sever-chosen -> metadata-server-chosen 
"device aware of the association between the metadata-sever-chosen" metadata-sever-chosen -> metadata-server-chosen 

page 11: 
"rather than only to daya storage device that contain the locked" daya -> data 

page 19: 
" If an implementation needs a different statedid per file handle, then" statedid -> stateid 

page 20: 
" if the client could determine that there was a network diconnect" diconnect -> disconnect 

page 24: 
"client's responsibility with resepect to COMMIT is explained in" resepect -> respect 

page 36: 
"modifying the syntethic uid or gid on the data file." syntethic -> synthetic 

Regards, 
Tigran. 

> From: "Thomas Haynes" <loghyr@primarydata.com>
> To: "NFSv4" <nfsv4@ietf.org>
> Sent: Thursday, July 20, 2017 1:57:32 PM
> Subject: [nfsv4] Request for WG Last Call

> One of my AIs from the IETF meeting was to inform the WG that I wanted the
> following two documents to be in WGLC:

> [ https://datatracker.ietf.org/doc/draft-ietf-nfsv4-flex-files/ |
> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-flex-files/ ] - draft 12
> [ https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layout-types/ |
> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layout-types/ ] - draft 05

> So this is that request...

> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4

--=_e7fab3a6-017d-4825-a422-9de5040c55ab
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"font-family: courier new,courier,monaco,monospace=
,sans-serif; font-size: 14pt; color: #000000">Hi Tom,<br><br>some typos:<br=
><br>&nbsp;&nbsp; page 6:<br>&nbsp;&nbsp;" A client presenting the<br>&nbsp=
;&nbsp; wrong credential for the deisred access will get a NFS4ERR_ACCESS<b=
r>&nbsp;&nbsp; error." &nbsp;deisred -&gt; desired <br><br>&nbsp;page 7:<br=
>&nbsp;&nbsp; "that would never be used to grant acccess." &nbsp;acccess -&=
gt; access<br><br>&nbsp;page 9:<br>&nbsp;&nbsp;"OPEN_DOWNGRADE and CLOSE on=
ly require local execution on the<br>&nbsp;&nbsp; &nbsp; &nbsp;metadata sev=
er." &nbsp; sever -&gt; server<br><br>&nbsp;page 10:<br>&nbsp;"2.3.2. &nbsp=
;Tighly Coupled Locking Model" &nbsp;Tighly -&gt; Tightly <br><br>&nbsp;"of=
 the association between the metadata-sever-chosen stateid and" metadata-se=
ver-chosen -&gt; metadata-server-chosen<br>"device aware of the association=
 between the metadata-sever-chosen" metadata-sever-chosen -&gt; metadata-se=
rver-chosen<br><br>&nbsp;page 11:<br>&nbsp;&nbsp;"rather than only to daya =
storage device that contain the locked" daya -&gt; data<br><br>&nbsp;page 1=
9:<br>&nbsp;" If an implementation needs a different statedid per file hand=
le, then" &nbsp;statedid -&gt; stateid<br><br>&nbsp;page 20:<br>&nbsp;" if =
the client could determine that there was a network diconnect" diconnect -&=
gt; disconnect<br><br>page 24:<br>&nbsp;"client's responsibility with resep=
ect to COMMIT is explained in" &nbsp;resepect -&gt; respect<br><br>&nbsp;pa=
ge 36:<br>&nbsp;&nbsp;"modifying the syntethic uid or gid on the data file.=
" syntethic -&gt; synthetic<br><br>Regards,<br>&nbsp;&nbsp; Tigran.<br><br>=
<hr id=3D"zwchr" data-marker=3D""><div data-marker=3D""><blockquote style=
=3D"border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#0=
00;font-weight:normal;font-style:normal;text-decoration:none;font-family:He=
lvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Thomas Haynes" &lt;=
loghyr@primarydata.com&gt;<br><b>To: </b>"NFSv4" &lt;nfsv4@ietf.org&gt;<br>=
<b>Sent: </b>Thursday, July 20, 2017 1:57:32 PM<br><b>Subject: </b>[nfsv4] =
Request for WG Last Call<br></blockquote></div><div data-marker=3D""><block=
quote style=3D"border-left:2px solid #1010FF;margin-left:5px;padding-left:5=
px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;fon=
t-family:Helvetica,Arial,sans-serif;font-size:12pt;">One of my AIs from the=
 IETF meeting was to inform the WG that I wanted the following two document=
s to be in WGLC:
<div class=3D""><br class=3D"">
</div>
<div class=3D""><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-nfsv=
4-flex-files/" class=3D"" target=3D"_blank">https://datatracker.ietf.org/do=
c/draft-ietf-nfsv4-flex-files/</a>&nbsp;- draft 12</div>
<div class=3D""><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-nfsv=
4-layout-types/" class=3D"" target=3D"_blank">https://datatracker.ietf.org/=
doc/draft-ietf-nfsv4-layout-types/</a>&nbsp;- draft 05</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">So this is that request...</div>


<br>_______________________________________________<br>nfsv4 mailing list<b=
r>nfsv4@ietf.org<br>https://www.ietf.org/mailman/listinfo/nfsv4<br></blockq=
uote></div></div></body></html>
--=_e7fab3a6-017d-4825-a422-9de5040c55ab--

