IETF Logo Mail Archive

Re: [nfsv4] Comments on minutes of wg meeting at IETF114

Trond Myklebust <trondmy@gmail.com> Sun, 02 October 2022 15:16 UTC

Return-Path: <trondmy@gmail.com>
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 C37E9C14F720 for <nfsv4@ietfa.amsl.com>; Sun, 2 Oct 2022 08:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WxEWlpA7qMEX for <nfsv4@ietfa.amsl.com>; Sun, 2 Oct 2022 08:16:43 -0700 (PDT)
Received: from mail-oa1-x36.google.com (mail-oa1-x36.google.com [IPv6:2001:4860:4864:20::36]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B3F3C14F719 for <nfsv4@ietf.org>; Sun, 2 Oct 2022 08:16:43 -0700 (PDT)
Received: by mail-oa1-x36.google.com with SMTP id 586e51a60fabf-1321a1e94b3so4810790fac.1 for <nfsv4@ietf.org>; Sun, 02 Oct 2022 08:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=lvwMY3eF385JlrAOgq7+/fiSzI/ZZ3BRGagL22JUgFs=; b=miLQlNjaMWApptJQ0sKWh0rU+YIrkQL5F82tufBDYAN0mREdXQ3EZ0lWl2yE3Ag11F 6a+TXO+GXFJmk+E72flXndeQInG4brGpFQb2LrCxXyiuGeQ2qG0zYb3+JBw6cPza51uj 8FWPLo6mvAz+XsPGX6pzUnpUFKRGfMIGUSWw4J/UufsSxgs4R0aCsGuPLAEinKK+Lo0F BC7vnqDl/84UvgQChYFGlfx8Unb32I4W9EzXZjPYb02w9pBIcYXI9mfBdpAJl66FqVmV VDy8MGx9yDmXYkzOnFT1AgK3H4U7VWaMV4PjVTezZqUMz+zHxq70QJaO7AUxXMCVFCie zFLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=lvwMY3eF385JlrAOgq7+/fiSzI/ZZ3BRGagL22JUgFs=; b=nV6x9qjbveGJV1JZCf6AGf23MFeMdwXs4+PV+rsobnZBC0Zj9y+WhOgZFsC2X0Iyku ON5iCxm7OXoZ0a6QLy/sNclpJbC3PCwVxudURYY7oEJy+vunFX8uZQBF/p725FtIo42b /27qe68W2FePmTOXqcp6IK1ypU9Z+vx5wjVA1r2Czd0sl4KNxICpgfb3h9VggQQ1AWJl SPAqNe+EBiBxcvGHKayV1IPw0d8qKjD4Yl+uFae/vkZtjObAfRXQc9YArBl69SYl8o9H 3qBWTJyi+rG5IFV8x0g1bwEQQZwn7mslYgpN13e7L+ctpVKgPFFSN2WJbgMuWglcMk8f Tg0g==
X-Gm-Message-State: ACrzQf1U07XV2kbr0FCqgvwnxxQAT6PUImLsBLRM8ct1elijIJ6mLDKL WdLaojRRPetIdL7zvz6p4EWm0B3ATJxtZljid4wheIo=
X-Google-Smtp-Source: AMsMyM79HbDsruzItnXzELlAJ8mmYuXRMIJP6QnWGxGHzEXuJpQ7VAxjX5wY1vVay/5/8onF9xWS1fe/x9L3goa/0F0=
X-Received: by 2002:a05:6870:6488:b0:131:a45b:a8ca with SMTP id cz8-20020a056870648800b00131a45ba8camr3326781oab.260.1664723802016; Sun, 02 Oct 2022 08:16:42 -0700 (PDT)
MIME-Version: 1.0
References: <CADaq8jd4+FPhH0m5AuBgop_xJiYMjrRKva8mX0A-gioW_8b+5A@mail.gmail.com> <2CCC6B48-118F-48C3-A764-1380BAB72066@oracle.com> <CADaq8jeoyLbC_cFd8FwSzuSGFZAi9r3UsTGAxx5KykW+-99Jmg@mail.gmail.com> <606B4B27-0DC1-4215-987F-D97A37C4C278@oracle.com> <YQXPR01MB41506E793FF6F63EC6B1E185DD469@YQXPR01MB4150.CANPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <YQXPR01MB41506E793FF6F63EC6B1E185DD469@YQXPR01MB4150.CANPRD01.PROD.OUTLOOK.COM>
From: Trond Myklebust <trondmy@gmail.com>
Date: Sun, 02 Oct 2022 11:16:30 -0400
Message-ID: <CAABAsM7j_DAqBz0heGA4fGyF=wFfWJEyGY=d+pOv96zJ5P=nnQ@mail.gmail.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Cc: Chuck Lever III <chuck.lever@oracle.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de50a105ea0eb672"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/XCdEY9alSiG00LfvoQcRboMANrM>
Subject: Re: [nfsv4] Comments on minutes of wg meeting at IETF114
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 02 Oct 2022 15:16:43 -0000

On Tue, Sep 13, 2022 at 10:10 PM Rick Macklem <rmacklem@uoguelph.ca> wrote:

> Chuck Lever III wrote:
> > Trond stated that the proposed mechanism is a hack, which I take to mean
> > he will not accept it in the Linux client.
> It would be nice to find out what he thinks is appropriate?
>
>
Do it the same way we've already proposed to advertise other transport
mechanisms: use the fs_locations mechanism.
NFSv3 doesn't have a way to advertise mechanisms such as RDMA, so just
forget about it. It's not a concern for this working group anyway.

v2.23.0 | Report a Bug | By Email