Return-Path: <davenoveck@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 2534413218C
 for <nfsv4@ietfa.amsl.com>; Tue, 15 Aug 2017 04:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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 fOwrZ81MFbxg for <nfsv4@ietfa.amsl.com>;
 Tue, 15 Aug 2017 04:00:28 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com
 [IPv6:2607:f8b0:4001:c06::22e])
 (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 34E9213208E
 for <nfsv4@ietf.org>; Tue, 15 Aug 2017 04:00:28 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id m88so2332091iod.2
 for <nfsv4@ietf.org>; Tue, 15 Aug 2017 04:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :cc; bh=aaAaRBLyTsv+RcTTt5BqjRAZ8VJMw7w/aqXP4zJu36s=;
 b=u8LC2SugQ1EekUVSsvBYdtNqK6Tgb2Eoye37CZHSbz+iYZ7fmjD0UJnj6lllZODDKJ
 lyZI4UC2cLyar7OJlpUYl6144zrGxG7J17ZXoBK9EheifsOjCJUYUl8xV1Qtq2ykvBgf
 6TueS3+kx+u6nP9W3ZNIkfxgxSl5oe50H6+p2SZzijwoM3LjSXky0CZZ2Dxv3e1mB1T5
 7I7QvCSbQVonYovyTAicapg6e3mAjb7J29Lt4Tq7bcxI85bqdqQDr3RCadtvWPJEjQqM
 hOPXwvjmwT4b1oJ0PIcHYczpn3YtERysATQLd1L68tzqiUYUrEowSTtwCQFIoQl0ZfW7
 TgNA==
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=aaAaRBLyTsv+RcTTt5BqjRAZ8VJMw7w/aqXP4zJu36s=;
 b=MpjhSAERXtMK5ZeFWJj8rm3SGjeWSjfF+yc0sDfixxAgCvWLaz8HctK/8ps9p8KqoY
 J8NUazfg4ovti4V5zxfhkOYt4Cu3IjnGdmmKuH8TryZjmtcZyYlnPh5bYtHI4sUDg3wd
 rRH4qFo1buyVFmLl87X4jlsNG3FjUneKtWKqd5zf3y2OlkYtem6tUiAOCyqXCIVO8RPk
 ARM/yElkkpK+k9oFlELdSzqK3XRNrsrGwdoZvW8UuINt0ZZkxYcSvf9AQKKYJiDDlhcs
 UXDASgSTTs3DBh7VUMhTViTV7kJ9xxdu61UcdUqhBRpXCNeAyK5RD1mWd/CkB8gHFsmN
 yzqA==
X-Gm-Message-State: AIVw1129p0/D8x43SxFLsV0wk072Ulrk03m6cD59YH6AK2sFnH0UhkXj
 37TZjx/3+DLUzpoXuERYn/I2LV513Q==
X-Received: by 10.107.29.76 with SMTP id d73mr21187299iod.211.1502794827387;
 Tue, 15 Aug 2017 04:00:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.142.72 with HTTP; Tue, 15 Aug 2017 04:00:26 -0700 (PDT)
In-Reply-To: <CAFt6Ba=zox9Cyu--WwGtLpF2MQOEjJppaQvjrL+qsTZv918jig@mail.gmail.com>
References: <150214681284.12459.7958419961024288184@ietfa.amsl.com>
 <01E22DE7-123E-4765-908E-AF79FD8E4C5E@primarydata.com>
 <CADaq8jfVy-9LHPxJz818bLKwg0HSmpGLcR2dEsLkidEHZUShuw@mail.gmail.com>
 <CAFt6Ba=zox9Cyu--WwGtLpF2MQOEjJppaQvjrL+qsTZv918jig@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Tue, 15 Aug 2017 07:00:26 -0400
Message-ID: <CADaq8jdZ28Wr+FV4MYMgO8T17mtxnypZFk+H+PoMom_nFNiHMQ@mail.gmail.com>
To: spencer shepler <spencer.shepler@gmail.com>
Cc: Thomas Haynes <loghyr@primarydata.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="001a11409da2db589d0556c8af14"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/RJZrDF7flxB9V6mI-BY5oHNtC9I>
Subject: Re: [nfsv4] I-D Action: draft-ietf-nfsv4-flex-files-13.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: Tue, 15 Aug 2017 11:00:31 -0000

--001a11409da2db589d0556c8af14
Content-Type: text/plain; charset="UTF-8"

There is a need to adress the issue of a last call for flex-files-13.

I previously suggested extending the -12 LC to encompass the -13 and ending
on 8/21, but Spencer on 8/8 responded:.

> Thanks for the suggestion, Dave.  However, we will let the timer run on
the current last call (ends on Friday).

> Once that is complete, we will start another last call on the version of
the I-D that is available then.

Since that last call ended on 8/11, the version available now is -13.so we
have to start that new last call.

> Note that this is always the case - if there has been enough change
during a last call to warrant another round, then we do another last call.
Not a big deal.

I think it is pretty clear that there has been enough change.  If there is
anyone who disagrees, please speak up..

The only remaIning issue is the the end date.  I previously proposed a
two-week last call period to enable me to do
a comprehensive review.  Others might want to focus on the security changes
in -13 but I skipped a comprehensive
review of -12 because it was always pretty clear there would have to be a
-13.

Two weeks from today would be 8/29.  However, it may be simpler to make the
end date the following Fridiay, which is 9/1.
Is Tom and the rest of the working group OK with that end date for the -13
WGLC?



On Tue, Aug 8, 2017 at 2:26 PM, spencer shepler <spencer.shepler@gmail.com>
wrote:

>
>
> Thanks for the suggestion, Dave.  However, we will let the timer run on
> the current last call (ends on Friday).
>
> Once that is complete, we will start another last call on the version of
> the I-D that is available then.
>
> Note that this is always the case - if there has been enough change during
> a last call to warrant another round, then we do another last call.  Not a
> big deal.
>
> Spencer
>
> On Tue, Aug 8, 2017 at 3:16 AM, David Noveck <davenoveck@gmail.com> wrote:
>
>> I can't see reviewing this by 8/11.  I think we will need to reset the
>> WGLC clock.
>>
>> I thibk it should be extended  to 8/21 to give us two weeks to review the
>> new draft.  Other opinions?
>>
>> In any case, Spencer S should announce a new date, so everybody is in
>> sync.
>>
>> On Mon, Aug 7, 2017 at 8:09 PM, Thomas Haynes <loghyr@primarydata.com>
>> wrote:
>>
>>> This is a result of the earlier reviews in the WGLC and a desire for an
>>> update by said reviewers.
>>>
>>> > On Aug 7, 2017, at 4:00 PM, internet-drafts@ietf.org wrote:
>>> >
>>> >
>>> > A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> > This draft is a work item of the Network File System Version 4 WG of
>>> the IETF.
>>> >
>>> >        Title           : Parallel NFS (pNFS) Flexible File Layout
>>> >        Authors         : Benny Halevy
>>> >                          Thomas Haynes
>>> >       Filename        : draft-ietf-nfsv4-flex-files-13.txt
>>> >       Pages           : 40
>>> >       Date            : 2017-08-07
>>> >
>>> > Abstract:
>>> >   The Parallel Network File System (pNFS) allows a separation between
>>> >   the metadata (onto a metadata server) and data (onto a storage
>>> >   device) for a file.  The flexible file layout type is defined in this
>>> >   document as an extension to pNFS which allows the use of storage
>>> >   devices in a fashion such that they require only a quite limited
>>> >   degree of interaction with the metadata server, using already
>>> >   existing protocols.  Client side mirroring is also added to provide
>>> >   replication of files.
>>> >
>>> >
>>> > The IETF datatracker status page for this draft is:
>>> > https://datatracker.ietf.org/doc/draft-ietf-nfsv4-flex-files/
>>> >
>>> > There are also htmlized versions available at:
>>> > https://tools.ietf.org/html/draft-ietf-nfsv4-flex-files-13
>>> > https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-flex-files-13
>>> >
>>> > A diff from the previous version is available at:
>>> > https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-flex-files-13
>>> >
>>> >
>>> > 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.
>>> >
>>> > Internet-Drafts are also available by anonymous FTP at:
>>> > ftp://ftp.ietf.org/internet-drafts/
>>> >
>>> > _______________________________________________
>>> > nfsv4 mailing list
>>> > nfsv4@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/nfsv4
>>> >
>>>
>>> _______________________________________________
>>> nfsv4 mailing list
>>> nfsv4@ietf.org
>>> https://www.ietf.org/mailman/listinfo/nfsv4
>>>
>>
>>
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfsv4
>>
>>
>

--001a11409da2db589d0556c8af14
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><span style=3D"font-size:16px">There is a need to adr=
ess the issue of a last call for flex-files-13.=C2=A0</span></div><div><spa=
n style=3D"font-size:16px"><br></span></div><div><span style=3D"font-size:1=
6px">I previously suggested extending the -12 LC to encompass the -13 and e=
nding on 8/21, but Spencer on 8/8 responded:.</span></div><div><span style=
=3D"font-size:16px"><br></span></div><span style=3D"font-size:16px">&gt; Th=
anks for the suggestion, Dave.=C2=A0 However, we will let the timer run on =
the current last call (ends on Friday).</span><div><span style=3D"font-size=
:16px"><br></span></div><div><span style=3D"font-size:16px">&gt; Once that =
is complete, we will start another last call on the version of the I-D that=
 is available then.</span></div><div><div><span style=3D"font-size:16px"><b=
r></span></div><div><span style=3D"font-size:16px">Since that last call end=
ed on 8/11, the version available now is -13.so we have to start that new l=
ast call. =C2=A0</span></div><div><span style=3D"font-size:16px"><br></span=
></div><div><span style=3D"font-size:16px">&gt;=C2=A0</span><span style=3D"=
font-size:16px">Note that this is always the case - if there has been enoug=
h change during a last call to warrant another round, then we do another la=
st call.=C2=A0 Not a big deal.</span></div><div><span style=3D"font-size:16=
px"><br></span></div><div><span style=3D"font-size:16px">I think it is pret=
ty clear that there has been enough change.=C2=A0 If there is anyone who di=
sagrees, please speak up..</span></div><div><span style=3D"font-size:16px">=
<br></span></div><div><span style=3D"font-size:16px">The only remaIning iss=
ue is the=C2=A0</span><span style=3D"font-size:16px">the end date.=C2=A0 I =
previously proposed a two-week last call period to enable me to do=C2=A0</s=
pan></div><div><span style=3D"font-size:16px">a comprehensive review.=C2=A0=
 Others might want to=C2=A0</span><span style=3D"font-size:16px">focus on t=
he security changes in -13 but I skipped a comprehensive=C2=A0</span></div>=
<div><span style=3D"font-size:16px">review=C2=A0</span><span style=3D"font-=
size:16px">of -12 because it was always pretty clear there would=C2=A0</spa=
n><span style=3D"font-size:16px">have to be a -13.</span></div><div><span s=
tyle=3D"font-size:16px"><br></span></div><div><span style=3D"font-size:16px=
">Two weeks from today would be 8/29.=C2=A0 However, it may be simpler to m=
ake the end date the following Fridiay, which is 9/1.</span></div><div><spa=
n style=3D"font-size:16px">Is Tom and the rest of the working group OK with=
 that end date for the -13 WGLC?<br></span><div><span style=3D"font-size:16=
px"><br></span></div><div><span style=3D"font-size:16px"><br></span></div><=
/div></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Tue, Aug 8, 2017 at 2:26 PM, spencer shepler <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:spencer.shepler@gmail.com" target=3D"_blank">spencer.shepler@g=
mail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div><br></div><div><br></div><div>Thanks for the suggestion, Dave=
.=C2=A0 However, we will let the timer run on the current last call (ends o=
n Friday).</div><div><br></div><div>Once that is complete, we will start an=
other last call on the version of the I-D that is available then.</div><div=
><br></div><div>Note that this is always the case - if there has been enoug=
h change during a last call to warrant another round, then we do another la=
st call.=C2=A0 Not a big deal.</div><span class=3D"HOEnZb"><font color=3D"#=
888888"><div><br></div><div>Spencer</div></font></span></div><div class=3D"=
HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Tue, Aug 8, 2017 at 3:16 AM, David Noveck <span dir=3D"ltr">&lt=
;<a href=3D"mailto:davenoveck@gmail.com" target=3D"_blank">davenoveck@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r">I can&#39;t see reviewing this by 8/11.=C2=A0 I think we will need to re=
set the WGLC clock.<div><br></div><div>I thibk it should be extended =C2=A0=
to 8/21 to give us two weeks to review the new draft.=C2=A0 Other opinions?=
</div><div><br></div><div>In any case, Spencer S should announce a new date=
, so everybody is in sync.</div></div><div class=3D"m_3105308156765519733HO=
EnZb"><div class=3D"m_3105308156765519733h5"><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Mon, Aug 7, 2017 at 8:09 PM, Thomas Haynes <=
span dir=3D"ltr">&lt;<a href=3D"mailto:loghyr@primarydata.com" target=3D"_b=
lank">loghyr@primarydata.com</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">This is a result of the earlier reviews in the WGLC and a desire =
for an update by said reviewers.<br>
<div class=3D"m_3105308156765519733m_908866555369037243HOEnZb"><div class=
=3D"m_3105308156765519733m_908866555369037243h5"><br>
&gt; On Aug 7, 2017, at 4:00 PM, <a href=3D"mailto:internet-drafts@ietf.org=
" target=3D"_blank">internet-drafts@ietf.org</a> wrote:<br>
&gt;<br>
&gt;<br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts dir=
ectories.<br>
&gt; This draft is a work item of the Network File System Version 4 WG of t=
he IETF.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: Parallel NFS (pNFS) Flexible File Layout<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: =
Benny Halevy<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Thomas Haynes<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-=
ietf-nfsv4-flex-files-13<wbr>.txt<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: 40<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 : 2017-08-07<br>
&gt;<br>
&gt; Abstract:<br>
&gt;=C2=A0 =C2=A0The Parallel Network File System (pNFS) allows a separatio=
n between<br>
&gt;=C2=A0 =C2=A0the metadata (onto a metadata server) and data (onto a sto=
rage<br>
&gt;=C2=A0 =C2=A0device) for a file.=C2=A0 The flexible file layout type is=
 defined in this<br>
&gt;=C2=A0 =C2=A0document as an extension to pNFS which allows the use of s=
torage<br>
&gt;=C2=A0 =C2=A0devices in a fashion such that they require only a quite l=
imited<br>
&gt;=C2=A0 =C2=A0degree of interaction with the metadata server, using alre=
ady<br>
&gt;=C2=A0 =C2=A0existing protocols.=C2=A0 Client side mirroring is also ad=
ded to provide<br>
&gt;=C2=A0 =C2=A0replication of files.<br>
&gt;<br>
&gt;<br>
&gt; The IETF datatracker status page for this draft is:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-nfsv4-flex-file=
s/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<wbr=
>oc/draft-ietf-nfsv4-flex-files<wbr>/</a><br>
&gt;<br>
&gt; There are also htmlized versions available at:<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-nfsv4-flex-files-13"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr<wbr>af=
t-ietf-nfsv4-flex-files-13</a><br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-flex=
-files-13" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/d<wbr>oc/html/draft-ietf-nfsv4-flex-<wbr>files-13</a><br>
&gt;<br>
&gt; A diff from the previous version is available at:<br>
&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-nfsv4-flex-f=
iles-13" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?=
u<wbr>rl2=3Ddraft-ietf-nfsv4-flex-file<wbr>s-13</a><br>
&gt;<br>
&gt;<br>
&gt; Please note that it may take a couple of minutes from the time of subm=
ission<br>
&gt; until the htmlized version and diff are available at <a href=3D"http:/=
/tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<b=
r>
&gt;<br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" tar=
get=3D"_blank">ftp://ftp.ietf.org/internet-dr<wbr>afts/</a><br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; nfsv4 mailing list<br>
&gt; <a href=3D"mailto:nfsv4@ietf.org" target=3D"_blank">nfsv4@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/nfsv4" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/nfsv4</a>=
<br>
&gt;<br>
<br>
______________________________<wbr>_________________<br>
nfsv4 mailing list<br>
<a href=3D"mailto:nfsv4@ietf.org" target=3D"_blank">nfsv4@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nfsv4" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/nfsv4</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
nfsv4 mailing list<br>
<a href=3D"mailto:nfsv4@ietf.org" target=3D"_blank">nfsv4@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nfsv4" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/nfsv4</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a11409da2db589d0556c8af14--

