Re: [nfsv4] [FedFS] XDR encoding of path "/"

"Spencer Shepler" <spencer.shepler@gmail.com> Wed, 13 October 2010 16:14 UTC

Return-Path: <spencer.shepler@gmail.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52FF13A6AFF for <nfsv4@core3.amsl.com>; Wed, 13 Oct 2010 09:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VpELXppXD2Sf for <nfsv4@core3.amsl.com>; Wed, 13 Oct 2010 09:14:20 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id B8DF33A69C5 for <nfsv4@ietf.org>; Wed, 13 Oct 2010 09:13:44 -0700 (PDT)
Received: by pvg16 with SMTP id 16so500429pvg.31 for <nfsv4@ietf.org>; Wed, 13 Oct 2010 09:14:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=MpMvSklOu75FSqu+W/18o8A+rIHkixfzXbxDpHQIez8=; b=mTFGtyqlHSU8fBPiJkquLTL4FTOcBVwczVkSqc7G/eBUvW7wYleLPQO8E3/wdpqFSL izSxv35knJksgimooODRbnmWOAn4hUc0QY3AYiUILhMsaP3bbHsmf9cZ9NuQ8JHJK/Xj SHvKxgfBd17vCrOS2AJXGZwBeVtglV9vzLpyk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; b=v6SML0ODsVQ2mZjrSznWkCDTQeit4/FmnmcpElyMuqOMqMgD58I6o+OCRRAwflXmcn 25cuvgO59gqV2NK10iu1Rci29wTnFmH1K9yNA+2qh0unKBsrGzU+Hn2x8xW5UOAw8R4G tBqjvPeZVxy8iNhrYqrGqsM4CY0JgsDft/1Tc=
Received: by 10.143.166.16 with SMTP id t16mr5119439wfo.52.1286986493382; Wed, 13 Oct 2010 09:14:53 -0700 (PDT)
Received: from ssheplermobile (tide40.microsoft.com [131.107.0.83]) by mx.google.com with ESMTPS id q13sm11691369wfc.17.2010.10.13.09.14.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 13 Oct 2010 09:14:51 -0700 (PDT)
From: "Spencer Shepler" <spencer.shepler@gmail.com>
To: "'James Lentini'" <jlentini@netapp.com>, <nfsv4@ietf.org>
References: <alpine.LFD.2.00.1010130934190.4707@jlentini-linux.nane.netapp.com>
In-Reply-To: <alpine.LFD.2.00.1010130934190.4707@jlentini-linux.nane.netapp.com>
Date: Wed, 13 Oct 2010 09:14:49 -0700
Message-ID: <026701cb6af1$c3c19f20$4b44dd60$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQHzFhZ9XQuROseVy1CgJIihDpkxKZLvtgXQ
Content-Language: en-us
Subject: Re: [nfsv4] [FedFS] XDR encoding of path "/"
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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>
X-List-Received-Date: Wed, 13 Oct 2010 16:14:27 -0000

> -----Original Message-----
> From: nfsv4-bounces@ietf.org [mailto:nfsv4-bounces@ietf.org] On Behalf Of
> James Lentini
> Sent: Wednesday, October 13, 2010 7:17 AM
> To: nfsv4@ietf.org
> Subject: [nfsv4] [FedFS] XDR encoding of path "/"
> 
> 
> At the BAT, Chuck Lever and I discussed what the pathname4 encoding of "/"
> should be.
> 
> In addition to being used by the fs_locations and fs_locations_info
> attributes, the pathname4 format is used by the fedfsNfsPath LDAP
> attribute (see Section 4.2.1.14 of draft-ietf-nfsv4-federated-fs-protocol-
> 09), and the FedFsPathName XDR type (see draft-ietf-nfsv4-federated-fs-
> admin-07).
> 
> I'm aware of two different approaches to encoding "/".
> 
> One interpretation is to encode an array with zero compnent4 values.
> This encoding is a single 32-bit field containing a 0. The Linux NFS
> server and the SNSDB tools use this format.
> 
> Another interpretation is to encode an array with one zero-length
> component4 value. The encoding of this is a 32-bit field containing a
> 1 followed by a 32-bit field containing a 0.
> 
> The Linux NFS client appears to accept both of these encodings for "/".
> 
> Are there any implementations using a different encoding than the ones
> above?
> 
> I'm thinking it would make sense to record these different formats or
> recommend the use of a specific format in one (or both) of the FedFS
> specifications.
>

Good point. FedFS specification is a good choice.  As to the specifics,
I would mildly prefer both be specified as acceptable encodings.

Spencer