Re: [nfsv4] FW: New Version Notification for draft-faibish-nfsv4-data-reduction-attributes-03.txt Thu, 25 June 2020 20:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C28B53A0FFE for <>; Thu, 25 Jun 2020 13:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5OTI6frEJO6X for <>; Thu, 25 Jun 2020 13:34:02 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8CE833A0F56 for <>; Thu, 25 Jun 2020 13:34:02 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id 05PKVqg1021114 for <>; Thu, 25 Jun 2020 16:34:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=smtpout1; bh=pYTBFhku2iOOYMw+dZ8Fc+VPj54adneMyaKfyVGITr0=; b=HxYjUyhralggS9zckZfPnDhPzw78GaCxtSv+J0lynKwopb2fChAT1AL381f/X+IkjyQk BVPBgSzlb8Z9DUfQPZQaNHV5whQuLfH6uji8BrIjo0kwu5BNi7CZ3OWdVyV+iJkkW7dk unHWJg5+822Py2ymBNTGUUBtlV/VlpD2y7v3ipFfKWt1XEeOo6v3Wi7yydy+wb3MD3N0 P2KrOPSyW/oEsLDCLTpKho94SOBqgpsZC6B8KjvtZItoP21DRUvE+pJqOXmHjJ11zf4X hJfF/s20T9Ph5NrkaN6LZJAkGH7oCPC0Pl0T1eNE+/EySs2RAO4kV2OBSsT2s7zSvGJz Cg==
Received: from ( []) by with ESMTP id 31uusuqvnt-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <>; Thu, 25 Jun 2020 16:34:01 -0400
Received: from pps.filterd ( []) by ( with SMTP id 05PKXQgj065845 for <>; Thu, 25 Jun 2020 16:34:01 -0400
Received: from ( []) by with ESMTP id 31w27mruqt-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <>; Thu, 25 Jun 2020 16:34:00 -0400
X-LoopCount0: from
X-PREM-Routing: D-Outbound
X-IronPort-AV: E=Sophos;i="5.60,346,1549951200"; d="scan'208,217";a="1401812157"
Thread-Topic: [nfsv4] FW: New Version Notification for draft-faibish-nfsv4-data-reduction-attributes-03.txt
Thread-Index: AQHWSmGdBGo9bA0/8E2dtwST9naOw6joLrnAgAEx/oCAAGfUIA==
Date: Thu, 25 Jun 2020 20:33:58 +0000
Message-ID: <6c4e528d002c4dc0b5828b53ccc50fba@x13pwdurdag1001.AMER.DELL.COM>
References: <> <aeb4feda663c455096c6a23638527788@x13pwdurdag1001.AMER.DELL.COM> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
msip_labels: MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Enabled=True; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_SiteId=945c199a-83a2-4e80-9f8c-5a91be5752dd;; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_SetDate=2020-06-25T20:33:57.4716465Z; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Name=External Public; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Application=Microsoft Azure Information Protection; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_ActionId=b59305bf-d467-43ca-bd2b-4b7073ec8351; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Extended_MSFT_Method=Manual
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_6c4e528d002c4dc0b5828b53ccc50fbax13pwdurdag1001AMERDELL_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687 definitions=2020-06-25_16:2020-06-25, 2020-06-25 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1015 mlxscore=0 adultscore=0 lowpriorityscore=0 priorityscore=1501 malwarescore=0 impostorscore=0 phishscore=0 mlxlogscore=999 bulkscore=0 spamscore=0 cotscore=-2147483648 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2006250120
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 spamscore=0 phishscore=0 mlxlogscore=999 adultscore=0 bulkscore=0 suspectscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2006250120
Archived-At: <>
Subject: Re: [nfsv4] FW: New Version Notification for draft-faibish-nfsv4-data-reduction-attributes-03.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NFSv4 Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 25 Jun 2020 20:34:05 -0000

From: nfsv4 <> On Behalf Of David Noveck
Sent: Thursday, June 25, 2020 6:13 AM
To: faibish, sorin
Cc: NFSv4
Subject: Re: [nfsv4] FW: New Version Notification for draft-faibish-nfsv4-data-reduction-attributes-03.txt


On Wed, Jun 24, 2020, 4:01 PM <<>> 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.
[sf] and drop David Black from the authors.

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. ???
[sf] Correct.

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.
[sf] Yes please plan for 15 min slot.

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.
[sf] Yes, I will include the proposed attributes in the slides that I will present for discussions and agreement.

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.
[sf] I don’t disagree and this is what I intent to include in the plan as well.

Also, you agreed to work on the nvme/pNFS document and we will need a progress report on that effort.
[sf] We made some progress and Christophe did a first review and started a git where we checked the document and started the review. I am still waiting for a last review of David Black. I might post the draft as it is now (needs more cleanup) so the WG can start a review. In any case we intent to get a spot to present the progress made since 107. We need a slot for this, maybe 20min. thank you


Thank you

Sorin Faibish, SDE, DellEMC Midrange Division

-----Original Message-----
From:<> <<>>
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


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

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

The IETF Secretariat

nfsv4 mailing list<>