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 59D0A3A08F3
 for <nfsv4@ietfa.amsl.com>; Thu, 25 Jun 2020 03:13:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 ZDCTy18DOgnk for <nfsv4@ietfa.amsl.com>;
 Thu, 25 Jun 2020 03:13:17 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com
 [IPv6:2a00:1450:4864:20::631])
 (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 2BA253A08F0
 for <nfsv4@ietf.org>; Thu, 25 Jun 2020 03:13:17 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id w6so5371181ejq.6
 for <nfsv4@ietf.org>; Thu, 25 Jun 2020 03:13:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=xfm70AVow0D0AemTLqw8UgtPAYahJixNAeaX9rpSIK0=;
 b=TpFVukcViHqmh72ztcDs0VX0e+zm/1NJEd8bAf0tsBZO8ipV8RYFY9aukiJk4T6hkh
 FifyJdDT/JSw6SYdr13atgfqVv3sYY3NDrzQMXbs1xqno+Uym3QcSST9V/DnR1eKnCQb
 SwlPJx3tYpA03dKD9PhCLraqDF/9iZbdYmov8XxQHs5NFlJknwsw2beQC0iCwrFJbuAe
 NYjOkE9spIKuCawKFhoRtzp8IUQP1mSEh5QDzT+vOerqCqDZNMqYCVUrCWpzqKeRwI0t
 beKZzcz3H1jNBvwkv5yJ02x+eDLl0bG2cR4vf88UvjJ/+YOcgYCGH/tv37iu+uKHkDuF
 +YKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=xfm70AVow0D0AemTLqw8UgtPAYahJixNAeaX9rpSIK0=;
 b=rRRl9vXGLlTGZDSAi9fF74NG63OszDWoCyDmDLs4FjCtBsiN/sxc92OTMk4QkjSolZ
 RbXXJ3YH2gAFJF2Q/N5P33ICYScge/Bv21dKCdtS/N4aSX4JAY6zqzzQQ5ym93wgmE7q
 Vknd/wYeE894nEEbHCTzfzMd8IC3ajCwW1/5si2enWM8BUtrDB8QwJ3UUFm9kaR66J8T
 4HhlBADYQF7mJbWJQKICAl/sM5umsDd8LPiOm/PT+20OLMVDSA+sMv/gWHuvXpi10G5V
 ml/BAhiJPQSjspYJ/zbUOjUymqfIdQMiqAo+FoW595J5HhisMB8ddhO3iWT++RWcyMFN
 Cf7Q==
X-Gm-Message-State: AOAM533dJLvpNSnzUxnSzeJ8HXnJiU0gC1VDn0TmrPrWJKh+i+SXWcOQ
 8dvj/UJPTaLV1Ucg79rwWThE0Q896iJm//tFVsQ=
X-Google-Smtp-Source: ABdhPJwL54bt2urJReBnpyXwe63bW/KKqVTU7P/tojVnvuF9xE5U+QzBtZqwcZZjpf6FEc//B/sPsSdC+WSXJKCuCK0=
X-Received: by 2002:a17:906:50b:: with SMTP id
 j11mr10657286eja.127.1593079995580; 
 Thu, 25 Jun 2020 03:13:15 -0700 (PDT)
MIME-Version: 1.0
References: <159302848689.20110.5541767567049187843@ietfa.amsl.com>
 <aeb4feda663c455096c6a23638527788@x13pwdurdag1001.AMER.DELL.COM>
In-Reply-To: <aeb4feda663c455096c6a23638527788@x13pwdurdag1001.AMER.DELL.COM>
From: David Noveck <davenoveck@gmail.com>
Date: Thu, 25 Jun 2020 06:13:03 -0400
Message-ID: <CADaq8jf5es0L3_Yn3C6BgCbR4rrpKdQ8ijpBiDkXk-bZsneAqA@mail.gmail.com>
To: Faibish.Sorin@dell.com
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003c478005a8e5d7ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/sahUlNriL07gmNYYOo507B9Hd7A>
Subject: Re: [nfsv4] FW: New Version Notification for
 draft-faibish-nfsv4-data-reduction-attributes-03.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Jun 2020 10:13:19 -0000

--0000000000003c478005a8e5d7ea
Content-Type: text/plain; charset="UTF-8"

On Wed, Jun 24, 2020, 4:01 PM <Faibish.Sorin@dell.com> wrote:

> I posted a new version of the draft mainly to change the authors of the
> draft.


I suppose that the impending expiration of the -02 also had a role.

I was confused by the diffs from -02 since almost all the changes were
things we had already seen in the post-107 virtual meeting.  I suppose that
the document that we discussed at that time has not been posted until now.
???

I will present my plans for an implementation during the meeting/call.


If you are requesting a speaking slot at that meeting and it seems as if
you are, you need to send me something that tells me what you intend to
talk about and how much time you intend to take.

Normally "plans for an implementation" might be an OK description but in
this case the specific attributes you intend to implement have never been
described, so I'll need some clarification on that, as would anyone who
might be interested in interoperating with your proposed implementation.

No additional changes were made at this time.


In the eleven months since the -00 was published, there has been very
limited progress toward describing the substance of the proposed attributes
and I think the working group will want to hear about your plans to make
progress in that regard. The need for that description was made clear at
the post-107 meeting.

Also, you agreed to work on the nvme/pNFS document and we will need a
progress report on that effort.

Thank you
>
> Sorin Faibish, SDE, DellEMC Midrange Division
>
> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: Wednesday, June 24, 2020 3:55 PM
> To: faibish, sorin; Shilane, Philip
> Subject: New Version Notification for
> draft-faibish-nfsv4-data-reduction-attributes-03.txt
>
>
> [EXTERNAL EMAIL]
>
>
> A new version of I-D, draft-faibish-nfsv4-data-reduction-attributes-03.txt
> has been successfully submitted by Sorin Faibish and posted to the IETF
> repository.
>
> Name:           draft-faibish-nfsv4-data-reduction-attributes
> Revision:       03
> Title:          Support for Data Reduction Attributes in nfsv4 Version 2
> Document date:  2020-06-24
> Group:          Individual Submission
> Pages:          13
> URL:
> https://www.ietf.org/internet-drafts/draft-faibish-nfsv4-data-reduction-attributes-03.txt
> Status:
> https://datatracker.ietf.org/doc/draft-faibish-nfsv4-data-reduction-attributes/
> Htmlized:
> https://tools.ietf.org/html/draft-faibish-nfsv4-data-reduction-attributes-03
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-faibish-nfsv4-data-reduction-attributes
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-faibish-nfsv4-data-reduction-attributes-03
>
> Abstract:
>    This document proposes extending NFSv4 operations to add new
>    RECOMMENDED attributes to be used in the protocol to provide
>    information about the data reduction properties of files. The new
>    data reduction attributes are proposed to allow the client
>    application to communicate to the NFSv4 server data reduction
>    attributes associated with files and directories using new metadata,
>    communicated to the Block Storage data reduction engines.
>    Corresponding new RECOMMENDED attributes are proposed to allow
>    clients and client applications to query the server for data
>    reduction attributes support and allow to get and set data reduction
>    attributes on files and directories. Such data reduction
>    metadata is used as hints to the file server about what type of data
>    reduction to apply. The proposed data reduction attributes include
>    achievable ratios for compression and deduplication plus whether
>    each data reduction technique applies to a file or directory.
>
>
>
>
> 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.
>
> The IETF Secretariat
>
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>

--0000000000003c478005a8e5d7ea
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Wed, Jun 24, 2020, 4:01 PM  &lt;<a href=3D"mailto:F=
aibish.Sorin@dell.com" rel=3D"noreferrer noreferrer" target=3D"_blank">Faib=
ish.Sorin@dell.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I=
 posted a new version of the draft mainly to change the authors of the draf=
t.</blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">I =
suppose that the impending expiration of the -02 also had a role.</div><div=
 dir=3D"auto"><br></div><div dir=3D"auto">I was confused by the diffs from =
-02 since almost all the changes were things we had already seen in the pos=
t-107 virtual meeting.=C2=A0 I suppose that the document that we discussed =
at that time has not been posted until now. ???</div><div dir=3D"auto"><br>=
</div><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"> I will present my plans for an implementation during the meeting/ca=
ll. </blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">=
If you are requesting a speaking slot at that meeting and it seems as if yo=
u are, you need to send me something that tells me what you intend to talk =
about and how much time you intend to take.</div><div dir=3D"auto"><br></di=
v><div dir=3D"auto">Normally &quot;plans for an implementation&quot; might =
be an OK description but in this case the specific attributes you intend to=
 implement have never=C2=A0been described, so I&#39;ll need some clarificat=
ion on that, as would anyone who might be interested in interoperating with=
 your proposed implementation.</div><div dir=3D"auto"><br></div><div dir=3D=
"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">No addit=
ional changes were made at this time.</blockquote></div></div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">In the eleven months since the -00 was pub=
lished, there has been very limited progress toward describing the substanc=
e of the proposed attributes and I think the working group will want to hea=
r about your plans to make progress in that regard. The need for that descr=
iption was made clear at the post-107 meeting.</div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">Also, you agreed to work on the nvme/pNFS document a=
nd we will need a progress report on that effort.</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"> Thank you<br>
<br>
Sorin Faibish, SDE, DellEMC Midrange Division<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:internet-drafts@ietf.org" rel=3D"noreferrer norefer=
rer noreferrer" target=3D"_blank">internet-drafts@ietf.org</a> &lt;<a href=
=3D"mailto:internet-drafts@ietf.org" rel=3D"noreferrer noreferrer noreferre=
r" target=3D"_blank">internet-drafts@ietf.org</a>&gt; <br>
Sent: Wednesday, June 24, 2020 3:55 PM<br>
To: faibish, sorin; Shilane, Philip<br>
Subject: New Version Notification for draft-faibish-nfsv4-data-reduction-at=
tributes-03.txt<br>
<br>
<br>
[EXTERNAL EMAIL] <br>
<br>
<br>
A new version of I-D, draft-faibish-nfsv4-data-reduction-attributes-03.txt<=
br>
has been successfully submitted by Sorin Faibish and posted to the IETF rep=
ository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-faibish-nfsv4-data-redu=
ction-attributes<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A003<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Support for Data Reduction Attribu=
tes in nfsv4 Version 2<br>
Document date:=C2=A0 2020-06-24<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 13<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-faibish-nfsv4-data-reduction-attributes-03.txt" re=
l=3D"noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">https:/=
/www.ietf.org/internet-drafts/draft-faibish-nfsv4-data-reduction-attributes=
-03.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-faibish-nfsv4-data-reduction-attributes/" rel=3D"noreferrer=
 noreferrer noreferrer noreferrer" target=3D"_blank">https://datatracker.ie=
tf.org/doc/draft-faibish-nfsv4-data-reduction-attributes/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-faibish-nfsv4-data-reduction-attributes-03" rel=3D"noreferrer norefer=
rer noreferrer noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr=
aft-faibish-nfsv4-data-reduction-attributes-03</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-faibish-nfsv4-data-reduction-attributes" rel=3D"noreferrer =
noreferrer noreferrer noreferrer" target=3D"_blank">https://datatracker.iet=
f.org/doc/html/draft-faibish-nfsv4-data-reduction-attributes</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.o=
rg/rfcdiff?url2=3Ddraft-faibish-nfsv4-data-reduction-attributes-03" rel=3D"=
noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">https://www.=
ietf.org/rfcdiff?url2=3Ddraft-faibish-nfsv4-data-reduction-attributes-03</a=
><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document proposes extending NFSv4 operations to add new<b=
r>
=C2=A0 =C2=A0RECOMMENDED attributes to be used in the protocol to provide<b=
r>
=C2=A0 =C2=A0information about the data reduction properties of files. The =
new<br>
=C2=A0 =C2=A0data reduction attributes are proposed to allow the client<br>
=C2=A0 =C2=A0application to communicate to the NFSv4 server data reduction<=
br>
=C2=A0 =C2=A0attributes associated with files and directories using new met=
adata,<br>
=C2=A0 =C2=A0communicated to the Block Storage data reduction engines.<br>
=C2=A0 =C2=A0Corresponding new RECOMMENDED attributes are proposed to allow=
<br>
=C2=A0 =C2=A0clients and client applications to query the server for data<b=
r>
=C2=A0 =C2=A0reduction attributes support and allow to get and set data red=
uction<br>
=C2=A0 =C2=A0attributes on files and directories. Such data reduction<br>
=C2=A0 =C2=A0metadata is used as hints to the file server about what type o=
f data<br>
=C2=A0 =C2=A0reduction to apply. The proposed data reduction attributes inc=
lude<br>
=C2=A0 =C2=A0achievable ratios for compression and deduplication plus wheth=
er<br>
=C2=A0 =C2=A0each data reduction technique applies to a file or directory.<=
br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at <a href=3D"http://to=
ols.ietf.org" rel=3D"noreferrer noreferrer noreferrer noreferrer" target=3D=
"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
<br>
_______________________________________________<br>
nfsv4 mailing list<br>
<a href=3D"mailto:nfsv4@ietf.org" rel=3D"noreferrer noreferrer noreferrer" =
target=3D"_blank">nfsv4@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nfsv4" rel=3D"noreferrer n=
oreferrer noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mai=
lman/listinfo/nfsv4</a><br>
</blockquote></div></div></div>

--0000000000003c478005a8e5d7ea--

