IETF Logo Mail Archive

Re: [nfsv4] Extended Attributes NFSv4

Matt Benjamin <mbenjami@redhat.com> Fri, 02 August 2019 16:44 UTC

Return-Path: <mbenjami@redhat.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 2FF701206A9 for <nfsv4@ietfa.amsl.com>; Fri, 2 Aug 2019 09:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
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 aN34kFnp9mGA for <nfsv4@ietfa.amsl.com>; Fri, 2 Aug 2019 09:43:59 -0700 (PDT)
Received: from mail-io1-f52.google.com (mail-io1-f52.google.com [209.85.166.52]) (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 45BBF1206A5 for <nfsv4@ietf.org>; Fri, 2 Aug 2019 09:43:56 -0700 (PDT)
Received: by mail-io1-f52.google.com with SMTP id j5so149419922ioj.8 for <nfsv4@ietf.org>; Fri, 02 Aug 2019 09:43:56 -0700 (PDT)
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:content-transfer-encoding; bh=dxwISoQhRvYWJ8O7j7sM8ic7Lrv3Af7Uq3t+2Ao6eX0=; b=gN0xc4uDpf9pR826QLeuINdMtMJuqtdryzc2JAguGzi5Cd/aCJM/dTixsoZQ7kvVRb vdoSw1LqauLB5z79t5S1uVHkPhIMVKPAb47WcDUm/6YTGoUDW8ska9FMQdDcNP/Y2drB m330x0z7GIWi2ZNrZhOVU65JpSNBJwm5UcXXNjO9TeTSvYdYETBLPuBP1uNj1F1iWhtQ UfFV85G6a1ivAIC+KlFrZMHdPCt4q75lQxMP7horCoYNxU8XAf8T48yE7Fz5v0RiMh7v AMvbd2110qFAW7BmgDXYeSxM/xseXlNnh4yUn4POdOxKQXE0h1qCWDdDxwo8J54ejbra mPTA==
X-Gm-Message-State: APjAAAXjxQylXZkopDWb8Pew3K2cnh7OKbk1xmh0oG1vk0njZjtkndqn G6vPG/mIOKac65Jn2Zy9+rbwMQ8uU7TOGmzn1yWNqA==
X-Google-Smtp-Source: APXvYqwngt5Lm8F2j2S1kpnmNF6kDhKWmwx0kt4/H7QGOUr8ORu3CGdRoOdiqCP2P9ziK6nUTVWvyxOrXI/FrJk+MWc=
X-Received: by 2002:a05:6602:c7:: with SMTP id z7mr13181593ioe.130.1564764235417; Fri, 02 Aug 2019 09:43:55 -0700 (PDT)
MIME-Version: 1.0
References: <CADowLe+VaR15Bw49oNrZWtYLNcG6__kG2oD+yiOS07ON9mKTuQ@mail.gmail.com> <ecac6b1e73df449ea3b86f16c251aaa6@x13pwdurdag1001.AMER.DELL.COM> <CADaq8jeSmX1CyRK4ihuJ5eTcoAwdbm8CWO2_jBHNpkcDjx8sQQ@mail.gmail.com>
In-Reply-To: <CADaq8jeSmX1CyRK4ihuJ5eTcoAwdbm8CWO2_jBHNpkcDjx8sQQ@mail.gmail.com>
From: Matt Benjamin <mbenjami@redhat.com>
Date: Fri, 02 Aug 2019 12:43:43 -0400
Message-ID: <CAKOnarkoyCERM0AHsfamO509=UwsrpsGYXjoQvxWD0ePuk7CKw@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
Cc: "faibish, sorin" <Faibish.Sorin@dell.com>, Philip.Shilane@dell.com, victor.asencio@upr.edu, NFSv4 <nfsv4@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/b2Hw-9FrTaRctex2O3xxXWkycoY>
Subject: Re: [nfsv4] Extended Attributes NFSv4
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: Fri, 02 Aug 2019 16:44:02 -0000

I was not aware that this had been rejected?

Matt

On Fri, Aug 2, 2019 at 12:42 PM David Noveck <davenoveck@gmail.com> wrote:
>
> > The NFSv4 WG rejected the idea of using extended attributes that were specified in the rfc 8276.
>
> I don't'  think the working group considered and rejected the idea using extended attributes,   Making a decision like that is way to organized for an IETF working group, espec.
>
> Tha
> > It seems nobody implemented xattr per the rfc. If you have any plans for that please let the NFSv4 WG know sending this email to the nfsv4 list I added here. Thanks
>
> On Tue, Jul 30, 2019 at 11:47 AM <Faibish.Sorin@dell.com> wrote:
>>
>> Victor,
>>
>>
>>
>> Just to keep you expectations low, the NFSv4 WG rejected the idea of using extended attributes that were specified in the rfc 8276. It seems nobody implemented xattr per the rfc. If you have any plans for that please let the NFSv4 WG know sending this email to the nfsv4 list I added here. Thanks
>>
>>
>>
>> ./Sorin
>>
>>
>>
>>
>>
>> From: Victor A Asencio Casiano <victor.asencio@upr.edu>
>> Sent: Tuesday, July 30, 2019 10:43 AM
>> To: faibish, sorin; Shilane, Philip; Black, David
>> Cc: manoj.naik@nutanix.com; eshel@us.ibm.com
>> Subject: Extended Attributes NFSv4
>>
>>
>>
>> [EXTERNAL EMAIL]
>>
>> Good morning, I’m currently interested in adding extended attributes to NFSv4 and I would like if you can send me in the right direction. RFC 8276 and your draft (Support for Data Reduction Extended Attributes in nfsv4 Version 2) are the only serious documents that I found about this topic. I would like to know if Extended Attributes have been already implemented somewhere that I can test it out, or If someone try to implement this before or any source code that I can reach out or any draft code? Besides the code portions that appears on RFC 8276.
>>
>>
>>
>> Thanks for your help.
>>
>> _______________________________________________
>> 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



-- 

Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103

http://www.redhat.com/en/technologies/storage

tel.  734-821-5101
fax.  734-769-8938
cel.  734-216-5309

v2.23.0 | Report a Bug | By Email