Re: [nfsv4] AD Evaluation for draft-ietf-nfsv4-rpcrdma-bidirection-05

Tom Talpey <tom@talpey.com> Tue, 10 January 2017 22:13 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 D408D129585 for <nfsv4@ietfa.amsl.com>; Tue, 10 Jan 2017 14:13:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 FiXvvut71aM1 for <nfsv4@ietfa.amsl.com>; Tue, 10 Jan 2017 14:13:52 -0800 (PST)
Received: from p3plsmtpa08-10.prod.phx3.secureserver.net (p3plsmtpa08-10.prod.phx3.secureserver.net [173.201.193.111]) (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 5BCC91293E8 for <nfsv4@ietf.org>; Tue, 10 Jan 2017 14:13:52 -0800 (PST)
Received: from [192.168.0.61] ([24.218.182.144]) by :SMTPAUTH: with SMTP id R4fQcueYN9jIhR4fRcCMnt; Tue, 10 Jan 2017 15:13:21 -0700
To: nfsv4@ietf.org
References: <CAKKJt-fuKMwX06PerWzxBdBqQ_=eMvhQKUdSDb5xLsSX47q=yw@mail.gmail.com> <6ED233CF-5ED5-4C64-B9BD-F04E0BED0445@oracle.com>
From: Tom Talpey <tom@talpey.com>
Message-ID: <a9645e3e-3ddf-6ea7-bb92-9ef12345f1cc@talpey.com>
Date: Tue, 10 Jan 2017 17:13:19 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <6ED233CF-5ED5-4C64-B9BD-F04E0BED0445@oracle.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfEuE54ZkKVYQi5foZiO2F8nzgizqc7AX6RWCJn27oAbAXEfhtNJU7faevpxnGCSk7PmijWlE9BqAR5Pt77e0jaKiRMWv2wSEoLn/ivCC0W+DpOTnzYR/ ryacMeXIE+Z+5WwRIEsMfANCeIcCZ4XxUzKOq8h0TTyc356+S3dB/Hqr
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/asBAJ2hJW_66WYW8X4foEhDcTmI>
Subject: Re: [nfsv4] AD Evaluation for draft-ietf-nfsv4-rpcrdma-bidirection-05
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Jan 2017 22:13:54 -0000

On 1/10/2017 4:47 PM, Chuck Lever wrote:
>> Probably just for my benefit, but since you mention NAT routers in this text,
>>
>>    To facilitate operation through NAT routers, all NFSv4.1 transport
>>    connections are initiated by NFSv4.1 clients.  Therefore NFSv4.1
>>    servers send callbacks to clients in the backward direction on
>>    connections established by NFSv4.1 clients.
>>
>> is it obvious which end has responsibility for NAT binding keep-alives? I'm guessing that's a client responsibility, but that's just a guess.
>
> I don't understand what NAT binding keep-alive means, exactly, but
> based on a naive assumption, I think the client is responsible here.
> If anyone knows of a cite-able summary of the NFSv4.1 backchannel
> redesign goals, I can reference it here.

I think the reference to NAT is a red herring and should be deleted,
or at the very least demoted to an example. The goal of the client-
initiated backchannel was much more general; it included traversing
firewalls but it was not an explicit goal of the 4.1 backchannel to
interoperate through NAT (although it certainly does).

There was some language in the original RFC5661 sections 1.4, 2.10.1,
2.10.3.1 and 2.10.8.1 on this, but RFC5661 specifically never mentioned
NAT.

Tom.