[nfsv4] Re: Issue with rfc7530

"hch@lst.de" <hch@lst.de> Fri, 07 June 2024 15:35 UTC

Return-Path: <hch@lst.de>
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 3369DC14F6F2 for <nfsv4@ietfa.amsl.com>; Fri, 7 Jun 2024 08:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L5grPQYF6-1s for <nfsv4@ietfa.amsl.com>; Fri, 7 Jun 2024 08:35:46 -0700 (PDT)
Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE6DAC14E513 for <nfsv4@ietf.org>; Fri, 7 Jun 2024 08:34:06 -0700 (PDT)
Received: by verein.lst.de (Postfix, from userid 2407) id 46A8168BEB; Fri, 7 Jun 2024 17:34:02 +0200 (CEST)
Date: Fri, 07 Jun 2024 17:34:01 +0200
From: "hch@lst.de" <hch@lst.de>
To: Trond Myklebust <trondmy@hammerspace.com>
Message-ID: <20240607153401.GA9917@lst.de>
References: <CADaq8jeY5k5M8-t4+1g0Te-EXFR2bW4kXiuZ_Xt6xCn5XL7AVw@mail.gmail.com> <f89dbb09f25c4cf64cc53fea487836cf776dbb55.camel@hammerspace.com> <CADaq8jeSRrtJdkBMvd9YXEzRsau_F5GQgoVRd_+jSdWpMV7PGg@mail.gmail.com> <MN2PR19MB40450C2D0C8A880863A5BDD5831C2@MN2PR19MB4045.namprd19.prod.outlook.com> <20240507061242.GA959@lst.de> <CADaq8jeyqxYpG2S1wkWkSrpBTvTU98ZXcWH1JeK-Oc83uf043g@mail.gmail.com> <6e305f7848bfb20643ae67061caf597397752a7d.camel@hammerspace.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6e305f7848bfb20643ae67061caf597397752a7d.camel@hammerspace.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Message-ID-Hash: EJ6ERYNTNXCLYJ2FZXRV42KA627C4JEX
X-Message-ID-Hash: EJ6ERYNTNXCLYJ2FZXRV42KA627C4JEX
X-MailFrom: hch@lst.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "hch@lst.de" <hch@lst.de>, "David.Black=40dell.com@dmarc.ietf.org" <David.Black=40dell.com@dmarc.ietf.org>, "David.Black@dell.com" <David.Black@dell.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [nfsv4] Re: Issue with rfc7530
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/3SbMxZVSnFMSUsOSdQE0gluVMG8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>

It probably would be very useful to implementers to have information
on the valid characters, even if it is non-normative.  Note that for
Windows the low-level file system API actually allows a lot more
characters than the Win32 API.  So a windows based NFS server might
be able to allow a lot of those, but could not operate with Win32
applications either locally or remotely.