Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DE524C433E2 for ; Fri, 4 Sep 2020 00:53:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A8CC120709 for ; Fri, 4 Sep 2020 00:53:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="UVidnXkO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726489AbgIDAx2 (ORCPT ); Thu, 3 Sep 2020 20:53:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47788 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726397AbgIDAx0 (ORCPT ); Thu, 3 Sep 2020 20:53:26 -0400 Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 83F23C061244 for ; Thu, 3 Sep 2020 17:53:26 -0700 (PDT) Received: by mail-qk1-x72a.google.com with SMTP id d20so4973719qka.5 for ; Thu, 03 Sep 2020 17:53:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dWCn7QVi9rzgaST836cIIf5+YcLt/bpLVkDKh64fkgU=; b=UVidnXkOBTxYmihTRCnnfv8dMWwFIDgS8Hoa5gkhklyoSPylLN/S5bfj+4a3fc0Pxd wQtEaRYmHnX/thLACBj1Q9P4ExgauJjIgCqhnj9nGsD+eOmls+9Fku/jk0ucA21kb4Hv G7S0xW7EtbPZZF5J7DTep/FBltxnN85pPDpwC1eHarL8EJ7+bZx5u6kvRvVhwjtrStcg 1vr+KTrrnwsHrRjGvP9+2gi3WwsvoqfdKw4VnSmU97xkOx12artL2RrW2MxY7Uv47Sf8 nAkeze88eg3Ud3I339jGil4YANJTVQuXUjZQ3Ahfj9g6LGpBIOLAIq3M7xYnIaHwsNYP /a4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dWCn7QVi9rzgaST836cIIf5+YcLt/bpLVkDKh64fkgU=; b=EEFspvjDIEJbWKCguULgvgoQvnNRzSZj6eKKQCE+573man2BDFymHYe/XEYJpvpvU+ 0j13sJTzumAPwZOwRKNMxPy7AWtA6OKffy/A8oIT+3DKzKViJuUdDZwTSTFFrvr5IQx5 gHK8X4QNqugFazEaf3uC0AvUof37DDZZml37Hzih++chcA9rg1vrLYao5FhuSat7XjuZ o/LA+0hvBFvowLBnwDHPOUt3DtHr7oohyyp/Op9Ju5p8inQ0hE6tdc0gyfie4jd/Qnc5 K2BZk7/XQVKxDNBgcPIzXd2zzc/rLqx1SGDq/KOyFWejJHm5D9Q5t+mXv/Vc7kMrTzuU wqKA== X-Gm-Message-State: AOAM532T8A3xNiCcsHEFU7Ht58WXcP06XYjUcIx0V+xzpiHizEwXErk1 kTQcLiqU0EaOQDZNbecLApg= X-Google-Smtp-Source: ABdhPJwPcdtpCEJQCfBhBZzLSuiyPc6RPQXfzCKCn6SbNmhXqQ6vqDTTvITh1WKcUmS3NdvnuTm7dA== X-Received: by 2002:a37:64d4:: with SMTP id y203mr5849488qkb.359.1599180805501; Thu, 03 Sep 2020 17:53:25 -0700 (PDT) Received: from anon-dhcp-152.1015granger.net (c-68-61-232-219.hsd1.mi.comcast.net. [68.61.232.219]) by smtp.gmail.com with ESMTPSA id b13sm3459508qkl.46.2020.09.03.17.53.24 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2020 17:53:24 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) Subject: Re: [nfsv4] NFS over QUIC From: Chuck Lever In-Reply-To: <20200904003242.GB4788@fieldses.org> Date: Thu, 3 Sep 2020 20:53:23 -0400 Cc: Linux NFS Mailing List , NFSv4 , stfrench@microsoft.com Content-Transfer-Encoding: 7bit Message-Id: <064FD529-9526-4F34-BBE9-E9CDAC2EED5D@gmail.com> References: <20200903215242.GA4788@fieldses.org> <20200904003242.GB4788@fieldses.org> To: Bruce Fields X-Mailer: Apple Mail (2.3608.120.23.2.1) Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org > On Sep 3, 2020, at 8:32 PM, Bruce Fields wrote: > > On Thu, Sep 03, 2020 at 07:48:19PM -0400, Chuck Lever wrote: >> Hi Bruce- >> >>> On Sep 3, 2020, at 5:52 PM, J. Bruce Fields wrote: >>> >>> I've been thinking about what might be required for NFS to run over >>> QUIC. >>> >>> Also cc'ing Steve French in case he's thought about this for CIFS/SMB. >>> >>> I don't have real plans. For Linux, I don't even know if there's a >>> kernel QUIC implementation planned yet. >>> >>> QUIC uses TLS so we'd probably steal some stuff from the NFS/TLS draft: >>> >>> https://datatracker.ietf.org/doc/draft-cel-nfsv4-rpc-tls/ >> >> The link to the latest version of that document is >> >> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-rpc-tls/ >> >>> For example, section 4.3, which explains how to authenticate on top of >>> an already-encrypted session, should also apply to QUIC. >> >> Most of the document's content will be re-used for defining >> RPC-over-QUIC, for example the ALPN defined in Section 8.2. >> Lars Eggert, a chair of the QUIC WG, has been helping guide >> the RPC-over-TLS effort with an eye towards using QUIC for >> RPC when QUIC becomes more mature. >> >> I thought the plan was to write a specification of RPC-over- >> QUIC as a new RPC transport type with a netid and uaddr along >> with a definition of the transport semantics (a la TI-RPC). >> The document would need to explain record marking, peer >> authentication, how to use multi-path and multi-stream support, >> and so on. >> >> Making NFS work on that transport should then be straightforward >> enough that perhaps additional standards work wouldn't be >> necessary. > > Oh, OK, good. Sounds like you're way ahead of me, then, I didn't know > there was a plan. That's all there is for the moment! :-) > --b. > >>> QUIC runs over UDP, so I think all that would be required to negotiate >>> support would be to attempt a QUIC connection to port 2049. >>> >>> The "Transport Layers" section in the NFS RFCs: >>> >>> https://tools.ietf.org/html/rfc5661#section-2.9 >>> >>> requires transports support reliable and in-order transmission, forbids >>> clients from retrying a request unless a connection is lost, and forbids >>> servers from dropping a request without closing a connection. I'm still >>> vague on how those requirements interact with QUIC's connection >>> management and 0-RTT reconnection. >>> >>> https://www.ietf.org/id/draft-ietf-quic-applicability-07.txt looks >>> useful, as a guide for applications running over QUIC. It warns that >>> connections can time out fairly quickly. For timely callbacks over NFS >>> sessions, that means we need the client to ping the server regularly. >>> Sounds like that's what they do for HTTP/QUIC to make server push >>> notifications work: >>> >>> https://tools.ietf.org/html/draft-ietf-quic-http-09#section-5 >>> >>> HTTP clients are expected to use QUIC PING frames to keep >>> connections open. Servers SHOULD NOT use PING frames to keep a >>> connection open. A client SHOULD NOT use PING frames for this >>> purpose unless there are responses outstanding for requests or >>> server pushes. >>> >>> QUIC allows multiple streams per connection--I wonder how we might use >>> that. RFC 5661 justifies the requirement for an ordered transport with: >>> >>> Ordered delivery simplifies detection of transmit errors, and >>> simplifies the sending of arbitrary sized requests and responses >>> via the record marking protocol. >>> >>> So as long as we don't try to split a single RPC among streams, I think >>> we're OK. Would a stream per session slot be reasonable? I'm not sure >>> what the cost of a stream is. >>> >>> Do we need to add a new universal address type so the protocol can >>> specify QUIC endpoints when necessary? (For server-to-server-copy, pnfs >>> file layouts, fs_locations, etc.) All QUIC needs is an IP address and >>> maybe a port, so maybe the existing UDP/TCP addresses are enough? >> >> -- >> Chuck Lever >> chucklever@gmail.com -- Chuck Lever chucklever@gmail.com