Re: [nfsv4] NFSv4 Charter change proposal

Tom Talpey <tom@talpey.com> Tue, 07 July 2020 13:09 UTC

Return-Path: <tom@talpey.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 0A3CF3A0C6D for <nfsv4@ietfa.amsl.com>; Tue, 7 Jul 2020 06:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Av02WFTyDBVh for <nfsv4@ietfa.amsl.com>; Tue, 7 Jul 2020 06:09:41 -0700 (PDT)
Received: from p3plsmtpa12-01.prod.phx3.secureserver.net (p3plsmtpa12-01.prod.phx3.secureserver.net [68.178.252.230]) (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 2B5CE3A0C5E for <nfsv4@ietf.org>; Tue, 7 Jul 2020 06:09:33 -0700 (PDT)
Received: from [192.168.0.78] ([24.218.182.144]) by :SMTPAUTH: with ESMTPSA id snLnjDBWWJN6DsnLojzpHu; Tue, 07 Jul 2020 06:09:32 -0700
X-CMAE-Analysis: v=2.3 cv=BZGmLYl2 c=1 sm=1 tr=0 a=ugQcCzLIhEHbLaAUV45L0A==:117 a=ugQcCzLIhEHbLaAUV45L0A==:17 a=IkcTkHD0fZMA:10 a=48vgC7mUAAAA:8 a=vw26ufmLKCC1ENfUmxYA:9 a=QEXdDO2ut3YA:10 a=w1C3t2QeGrPiZgrLijVG:22
X-SECURESERVER-ACCT: tom@talpey.com
To: nfsv4@ietf.org
References: <1c46b13053661a78fb69ee8783f29130447eff63.camel@ericsson.com> <CADaq8jdubM5JoyKf3xM5Uis1OpBgDnBXPuAxSsQ-CKwUfM5obg@mail.gmail.com>
From: Tom Talpey <tom@talpey.com>
Message-ID: <aa03c2a0-e7ce-0207-9002-03853db82c0f@talpey.com>
Date: Tue, 7 Jul 2020 09:09:32 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CADaq8jdubM5JoyKf3xM5Uis1OpBgDnBXPuAxSsQ-CKwUfM5obg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfP41MU5p1EteOwMEcYKJQ6wVLdlBLdAJIXBCmO1v7e11OECCQ1QvzEwVPN9h7pTs24SUqjPpF4pTKtr76l8Eg49+/TQrv/HZIUptBrsMxml+tYVPafy9 efGgwLpZuI7afir9sH+mUNWj/z2hRw+fK1I6Pg/bZumbOeIpLfVVnLZ2
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/a3IzULrtNPGUrKml4eVRu3H2yU8>
Subject: Re: [nfsv4] NFSv4 Charter change proposal
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: Tue, 07 Jul 2020 13:09:43 -0000

On 7/7/2020 4:18 AM, David Noveck wrote:
> 
> 
> On Mon, Jul 6, 2020 at 7:44 AM Magnus Westerlund 
> <magnus.westerlund=40ericsson.com@dmarc.ietf.org 
> <mailto:40ericsson.com@dmarc.ietf.org>> wrote:
> 
>  ...
> You've made that clear but I want us to focus on how we can most 
> expeditiously enable Tom to proceed on the push-mode draft about which 
> there seems to be no debate as to the suitability of the v4 wg as a home.
> 
>     Sorry if I am missing any context here, but if this is to enable a
>     mapping to QUIC. 
> 
> 
> I don't think it is.

Just to confirm, no, there is no linkage at all to QUIC from Push Mode.
It is a straight-up RDMA extension, with no transport implication on
TCP, QUIC, or any other lower layer.

Tom.