IETF Logo Mail Archive

Re: [nfsv4] Fwd: New Version Notification for draft-cel-nfsv4-rpc-over-quicv1-00.txt

David Noveck <davenoveck@gmail.com> Sat, 08 January 2022 11:58 UTC

Return-Path: <davenoveck@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 9C9643A1405 for <nfsv4@ietfa.amsl.com>; Sat, 8 Jan 2022 03:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9E_wJ3fsByly for <nfsv4@ietfa.amsl.com>; Sat, 8 Jan 2022 03:58:16 -0800 (PST)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21AD73A1404 for <nfsv4@ietf.org>; Sat, 8 Jan 2022 03:58:16 -0800 (PST)
Received: by mail-ed1-x52c.google.com with SMTP id u25so32690815edf.1 for <nfsv4@ietf.org>; Sat, 08 Jan 2022 03:58:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N9BQpLNrMwlROOnM66dAiag9JBV7uHLMzihfjiDYqTM=; b=Sqh/kBjukM/yFRYGETyZSPlBbDy0P7Dk3a43DyYTS8GxOTjQm9EOx3RDiPu9HpwEoi KleD7ryn4L07xJspyDBLdD0RLU224s7yOWTBDKnOmreL811Cpu+G3seKzRYajPZX/lqm uEJJcrh1TB3/seQcF8Qd/Edc0zRHIYVFr5TWyIk3mvjQQQMewtuwTo/tj36ze2UJhUjV aX/t4KQ5J3+IJ8PPLHSSEpVojpIkuxgHqVH9toY2np2dLVzNLQ/Qj+nrRqLIQbes3BR7 3u/PhbcXKlONsrgKUA3oVzoumZIyNBkCj3GH89VTAcxWSMxRYDIIgJzfZilbqgjqP6ft tHbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N9BQpLNrMwlROOnM66dAiag9JBV7uHLMzihfjiDYqTM=; b=NcTKR0PlHMEwtawQCUd1jJBogrQkYj4HGks/TUZmWmdV7GbTxypO4800BxS6zRtbCU 7ShB2FWG168Ak7sPXtkWq0gsUTwEL0nHdE8Tz6cmS22mDKL+KvqBpoxZ3I7vGiHRnMQu 6youIPEm9cj/CSGfP26Ai5bxwdvKR0HYn0HlEopgti8qtkN0waYkikIxB4EusuzoThYI LEVL5voQ0CTi4qbLS3vh35u31DA1MckPCqtdUIv/frvF7xQy3Pgwq7VdS488izN+yk69 SVb45Iyl4Jri7pFJZzRzkih8X4J/eFhvvOWW2ymHJsFzBXflPh3KL16+45tMEXSWuOFX O7Pw==
X-Gm-Message-State: AOAM532sZi98ux4DL+21+jeJP3p4TEUhkqKiQE35Nob6Jj/Rk7H0dDTF 6rV4sd5KqxRN8MHHB9X2zyKfYBc+VZWsyTp1gOPcQtTy
X-Google-Smtp-Source: ABdhPJymBwEJkhrzSz7o/9JpnLwg9j3U+4E2bWzC50RQAfYaRe/CQw17IwWXIyTAbOPrYjFri6VeYKupOqlfPm8QElo=
X-Received: by 2002:a17:906:7945:: with SMTP id l5mr52626033ejo.82.1641643092598; Sat, 08 Jan 2022 03:58:12 -0800 (PST)
MIME-Version: 1.0
References: <164157945469.28842.13842731936346376046@ietfa.amsl.com> <F42C3354-D12A-459E-8013-3C0F82E7DC81@oracle.com>
In-Reply-To: <F42C3354-D12A-459E-8013-3C0F82E7DC81@oracle.com>
From: David Noveck <davenoveck@gmail.com>
Date: Sat, 08 Jan 2022 06:58:00 -0500
Message-ID: <CADaq8jddbvDZaQpRHD6YowoFmjfw5bC-k0eUfefj4+rVTQH7EQ@mail.gmail.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: NFSv4 <nfsv4@ietf.org>, Bruce Fields <bfields@fieldses.org>
Content-Type: multipart/alternative; boundary="00000000000061e43c05d510d1a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/A74rsZ31UniX5v6-1AbvU8-bVx4>
Subject: Re: [nfsv4] Fwd: New Version Notification for draft-cel-nfsv4-rpc-over-quicv1-00.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: Sat, 08 Jan 2022 11:58:21 -0000

On Fri, Jan 7, 2022, 1:25 PM Chuck Lever III <chuck.lever@oracle.com> wrote:

>
> > Begin forwarded message:
> >
> > From: internet-drafts@ietf.org
> > Subject: New Version Notification for
> draft-cel-nfsv4-rpc-over-quicv1-00.txt
> > Date: January 7, 2022 at 1:17:34 PM EST
> > To: "Benjamin Coddington" <bcodding@redhat.com>, "Charles Lever" <
> chuck.lever@oracle.com>, "Chuck Lever" <chuck.lever@oracle.com>, "Scott
> Mayhew" <smayhew@redhat.com>
> >
> >
> > A new version of I-D, draft-cel-nfsv4-rpc-over-quicv1-00.txt
> > has been successfully submitted by Chuck Lever and posted to the
> > IETF repository.
>

Thanks for putting this together.

>
> > Name:         draft-cel-nfsv4-rpc-over-quicv1
> > Revision:     00
> > Title:                Remote Procedure Call over QUIC Version 1
> > Document date:        2022-01-07
> > Group:                Individual Submission
> > Pages:                8
> > URL:
> https://www.ietf.org/archive/id/draft-cel-nfsv4-rpc-over-quicv1-00.txt
> > Status:
> https://datatracker.ietf.org/doc/draft-cel-nfsv4-rpc-over-quicv1/
> > Html:
> https://www.ietf.org/archive/id/draft-cel-nfsv4-rpc-over-quicv1-00.html
> > Htmlized:
> https://datatracker.ietf.org/doc/html/draft-cel-nfsv4-rpc-over-quicv1
> >
> >
> > Abstract:
> >   This document specifies a protocol for conveying Remote Procedure
> >   (RPC) messages on QUIC version 1 connections.


This is not accurate.  I think it would be better if the abstract were
consistent with Chuck's description of this document later in his message.

It requires no
> >   revision to application RPC protocols or the RPC protocol itself.
>

It is anticipated that implementation of an eventual protocol would not
require ...


> During a recent nfsv4 working group meeting, the WG decided not to
> pursue RPC-over-QUIC until there was a clearer idea of its benefits
> relative to RPC on existing transports.
>
> This brief personal draft can act as a parking place for ideas and
> motivation for RPC-over-QUIC while implementations and rationale
> develop more fully.


I understand there are no implementations. When there is sufficient
interest to start on those, it will be time for the working group to pursue
this work with a document that seeks to specify an actual protocol.

In addition it can act as a reference when
> asked by external observers about our putative plans for RPC-over-
> QUIC.
>
> Please feel free to send comments or throw rotting fruit.
>

I'll be sending comments about the document in the next few days.

With regard to throwing rotting fruit, I have to note that it is probably
not possible to do that while being appropriately respectful of the
document authors, as IETF policies require.

>
> --
> Chuck Lever
>
>
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>

v2.23.0 | Report a Bug | By Email