From: Marc Eshel <eshel@us.ibm.com>
Subject: XATTRs in NFS
Date: Mon, 28 Oct 2013 15:28:42 -0700
Message-ID: <OF9D091881.D4CDB064-ON88257C12.007629C1-88257C12.007B7AFE@us.ibm.com>
References: <1382920068.6932.46.camel@heisenberg.scientia.net>
	<2E672741-FE4F-4287-8D00-B7634A71709E@netapp.com>
	<526E8562.3040809@redhat.com>
	<1382976943.8774.10.camel@heisenberg.scientia.net>
	<FD29488A-348B-48BA-9B1D-4ACF997BC794@netapp.com>
	<526EA65A.7010209@redhat.com> <20131028180838.GG31322@fieldses.org>
	<526EAD86.6090507@redhat.com>
	<OFA4C7B613.86F16AC7-ON88257C12.006FE486-88257C12.0071EE79@us.ibm.com>
	<C2C70C2E-100E-40BD-A919-A4F649077059@netapp.com>
	<20131028210247.GM31322@fieldses.org>
	<6AB20096-3993-47DD-AB58-2CD25F8A75D8@oracle.com>
	<OF3A48E6D9.7BB93CB0-ON88257C12.0075527E-88257C12.0075F065@LocalDomain>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6378171371387283193=="
Cc: Mailing List Linux NFS <linux-nfs@vger.kernel.org>
To: nfsv4@ietf.org
Return-path: <nfsv4-bounces@ietf.org>
In-Reply-To: <OF3A48E6D9.7BB93CB0-ON88257C12.0075527E-88257C12.0075F065@LocalDomain>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>,
	<mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
Sender: nfsv4-bounces@ietf.org
Errors-To: nfsv4-bounces@ietf.org
List-ID: <linux-nfs.vger.kernel.org>

This is a multipart message in MIME format.
--===============6378171371387283193==
Content-Type: multipart/alternative; boundary="=_alternative 0077D55E88257C12_="

This is a multipart message in MIME format.
--=_alternative 0077D55E88257C12_=
Content-Type: text/plain; charset="US-ASCII"

This is a clean start to discuss extended attributes over NFS in the 
mailing list first. 

1. What are the requirements and why? which applications are using them 
and how. 
2. Why are current named attributes in NFS not the right answer.
3. What does the new protocol enhancements should look like? 

Marc.

--=_alternative 0077D55E88257C12_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2>This is a clean start to discuss extended attributes
over NFS in the mailing list first. </font></tt>
<br>
<br><tt><font size=2>1. What are the requirements and why? which applications
are using them and how. </font></tt>
<br><tt><font size=2>2. Why are current named attributes in NFS not the
right answer.</font></tt>
<br><tt><font size=2>3. What does the new protocol enhancements should
look like? </font></tt>
<br>
<br><tt><font size=2>Marc.<br>
</font></tt>
--=_alternative 0077D55E88257C12_=--


--===============6378171371387283193==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4

--===============6378171371387283193==--