IETF Logo Mail Archive

Re: [nfsv4] [RFD] How to interpret empty path components in fs_locations/fs_locations_info

Nicolas Williams <Nicolas.Williams@oracle.com> Tue, 19 October 2010 21:55 UTC

Return-Path: <Nicolas.Williams@oracle.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 7AED23A6860 for <nfsv4@core3.amsl.com>; Tue, 19 Oct 2010 14:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level:
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 xP4ThiGIoulF for <nfsv4@core3.amsl.com>; Tue, 19 Oct 2010 14:55:01 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 46D143A67B8 for <nfsv4@ietf.org>; Tue, 19 Oct 2010 14:55:01 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o9JLuT39012774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 19 Oct 2010 21:56:30 GMT
Received: from acsmt355.oracle.com (acsmt355.oracle.com [141.146.40.155]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o9JIRs7N026590; Tue, 19 Oct 2010 21:56:27 GMT
Received: from abhmt009.oracle.com by acsmt354.oracle.com with ESMTP id 698858321287525386; Tue, 19 Oct 2010 14:56:26 -0700
Received: from oracle.com (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 19 Oct 2010 14:56:25 -0700
Date: Tue, 19 Oct 2010 16:56:21 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Message-ID: <20101019215621.GE4106@oracle.com>
References: <1287523510.9356.38.camel@heimdal.trondhjem.org> <20101019215330.GL1635@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20101019215330.GL1635@oracle.com>
User-Agent: Mutt/1.5.20 (2010-03-02)
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] [RFD] How to interpret empty path components in fs_locations/fs_locations_info
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: Tue, 19 Oct 2010 21:55:03 -0000

Well, a server could accept empty components, and treat them as if they
are not there.

What must not be allowed is objects with empty names.

v2.23.0 | Report a Bug | By Email