IETF Logo Mail Archive

[nfsv4] 4.0 trunking

bfields@fieldses.org (J. Bruce Fields) Wed, 07 September 2016 21:20 UTC

Return-Path: <bfields@fieldses.org>
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 5A3F812B0C7 for <nfsv4@ietfa.amsl.com>; Wed, 7 Sep 2016 14:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level:
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-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 3gOvK_tWNr0T for <nfsv4@ietfa.amsl.com>; Wed, 7 Sep 2016 14:20:39 -0700 (PDT)
Received: from fieldses.org (fieldses.org [IPv6:2600:3c00::f03c:91ff:fe50:41d6]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB8D12B10C for <nfsv4@ietf.org>; Wed, 7 Sep 2016 14:20:39 -0700 (PDT)
Received: by fieldses.org (Postfix, from userid 2815) id 09F2123C9; Wed, 7 Sep 2016 17:20:39 -0400 (EDT)
Date: Wed, 07 Sep 2016 17:20:39 -0400
To: David Noveck <davenoveck@gmail.com>
Message-ID: <20160907212039.GA6847@fieldses.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
From: bfields@fieldses.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/sjJg8jnI0-ZsIQepJZWvSNyfxxM>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: [nfsv4] 4.0 trunking
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: Wed, 07 Sep 2016 21:20:41 -0000

In
https://tools.ietf.org/html/draft-ietf-nfsv4-migration-issues-10#section-5.4.2

	In the face of possible trunking of server IP addresses, the
	client will use the receipt of the same clientid4 from multiple
	IP-addresses, as an indication that the two IP- addresses may be
	trunked and proceed to determine, from the observed server
	behavior whether the two addresses are in fact trunked.

But I can't find any further discussion of how a client might make that
determination.  Am I overlooking it?

(It appears that the Linux client is trying to do that by sending a
setclientid_confirm to server1 using the (clientid,verifier) returned
from a setclientid reply from server2.  That doesn't look correct to
me.)

--b.

v2.29.0 | Report a Bug | By Email | System Status