Re: [nfsv4] Fwd: New Version Notification for draft-dnoveck-nfsv4-internationalization-02.txt

bfields@fieldses.org Thu, 10 September 2020 15:58 UTC

Return-Path: <bfields@fieldses.org>
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 A5C893A0B38 for <nfsv4@ietfa.amsl.com>; Thu, 10 Sep 2020 08:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fieldses.org
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 IgUdLR2nRweS for <nfsv4@ietfa.amsl.com>; Thu, 10 Sep 2020 08:58:10 -0700 (PDT)
Received: from fieldses.org (fieldses.org [IPv6:2600:3c00:e000:2f7::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 917EF3A0B2C for <nfsv4@ietf.org>; Thu, 10 Sep 2020 08:58:10 -0700 (PDT)
Received: by fieldses.org (Postfix, from userid 2815) id B81FDAB6; Thu, 10 Sep 2020 11:58:08 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 fieldses.org B81FDAB6
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fieldses.org; s=default; t=1599753488; bh=jPCKd+D/XVcZ/72kmaBQsbviQ8XFpIrEg0t7Hk4UF0k=; h=Date:To:Cc:Subject:References:In-Reply-To:From:From; b=O8jyKoEct8nGXsu9ZzAWSJMFE+QlgK3FIp9t96sTiMHeS0AzQM/bpZxC8EW0WD+LP utc7+eTAmoTPaOD37rjyJ6rNplRYip81fBujfamofvsRcvUG1lfkRYvj3Oud2bNg1G cW2XTGK1t0s6zwMfMhAO6jzHmJ2r5RRmhIAtKsGc=
Date: Thu, 10 Sep 2020 11:58:08 -0400
To: David Noveck <davenoveck@gmail.com>
Cc: NFSv4 <nfsv4@ietf.org>
Message-ID: <20200910155808.GA28793@fieldses.org>
References: <159940402257.7572.11894435711259208477@ietfa.amsl.com> <CADaq8jcBidNH9qRobnP5YZuwV7Lmv-uFTcazMzrv0rBn7cdO4A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CADaq8jcBidNH9qRobnP5YZuwV7Lmv-uFTcazMzrv0rBn7cdO4A@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
From: bfields@fieldses.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/k-ggApKfCDxv_VHciX6L2xo5NXA>
Subject: Re: [nfsv4] Fwd: New Version Notification for draft-dnoveck-nfsv4-internationalization-02.txt
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: Thu, 10 Sep 2020 15:58:12 -0000

On Sun, Sep 06, 2020 at 11:18:05AM -0400, David Noveck wrote:
> In particular, given the confusing description of this attribute (see
> section 7.1), I'd like to know how this attribute has been implemented and
> used, if at all, to make sure that my attempt to guess at what was really
> intended do not give rise to interoperability problems.

The fs_charset_cap attribute has never been used by the Linux kernel
client or server, for what it's worth.

--b.