Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00.txt
"Spencer Shepler" <spencer.shepler@gmail.com> Wed, 20 October 2010 03:59 UTC
Return-Path: <spencer.shepler@gmail.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3C063A699E for <nfsv4@core3.amsl.com>; Tue, 19 Oct 2010 20:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level:
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxEF8vJ4brLH for <nfsv4@core3.amsl.com>; Tue, 19 Oct 2010 20:59:27 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id CA3C73A6997 for <nfsv4@ietf.org>; Tue, 19 Oct 2010 20:59:26 -0700 (PDT)
Received: by yxk30 with SMTP id 30so1538652yxk.31 for <nfsv4@ietf.org>; Tue, 19 Oct 2010 21:00:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=JKGP7TWY1RN+LHqVdQF3BNX+dMB0uGE8d861JtLPvDM=; b=rOswSDQMnFhwwtN8XQEmsjxNdhh9Wn+Mgfa3c52w/SPyWU6neV89x+h4j2J6D/km3P SEyBfyBkCuNxeFrWUcxrELpaxk+6RGOkp4F/fq9pc/nEbN4n+4d14OMS7JALTZrqzCZH 6J0izeGUedRCF2OQwgRlVim6aikEKAmdvOAqo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=xJuGR5IQvfVlzSjh6eceKMNEP5x69gThxXIJ3jNelH8vD4/vp5HFvCBnt+xP+pv6ZZ Au6jadkgsfZNwZDb/q/b+fdv1G1JcrDC8qTnjmt+PJbxQ5BC61uKDebtzKE/yfXO/MFJ qHZfdM0xlwzF38FUa3Bs3K3c51pTSVSb731d8=
Received: by 10.150.194.20 with SMTP id r20mr329979ybf.330.1287547253999; Tue, 19 Oct 2010 21:00:53 -0700 (PDT)
Received: from ssheplermobile (tide504.microsoft.com [131.107.0.74]) by mx.google.com with ESMTPS id t4sm6450190ybe.1.2010.10.19.21.00.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 19 Oct 2010 21:00:51 -0700 (PDT)
From: Spencer Shepler <spencer.shepler@gmail.com>
To: 'sfaibish' <sfaibish@emc.com>, 'Thomas Haynes' <thomas@netapp.com>
References: <20101018174520.EB8BA3A6B8B@core3.amsl.com> <C9B236F2-1F42-4070-A083-1A776B5C9C92@netapp.com> <op.vksebcc4unckof@usensfaibisl2e.eng.emc.com> <06d701cb6efe$f3f688c0$dbe39a40$@gmail.com> <op.vksfptzuunckof@usensfaibisl2e.eng.emc.com>
In-Reply-To: <op.vksfptzuunckof@usensfaibisl2e.eng.emc.com>
Date: Tue, 19 Oct 2010 21:00:48 -0700
Message-ID: <035d01cb700b$62bf5a90$283e0fb0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIzdGqWOIx8jR55+6waG0HPdrT6LwHp+dzcAVD0JQEB6JrQzQH4fKuykkBNh3A=
Content-Language: en-us
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Oct 2010 03:59:31 -0000
I believe that Sorin and I sorted this out off-list. There are separate issues/items and I believe I have the WG agenda updated to reflect this fact. If not, please let me know. Spencer > -----Original Message----- > From: sfaibish [mailto:sfaibish@emc.com] > Sent: Monday, October 18, 2010 1:12 PM > To: Spencer Shepler; 'Thomas Haynes' > Cc: nfsv4@ietf.org > Subject: Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00.txt > > I had the intention to start a discussion and there it is a WG draft > before I had the chance to post the discussion we had at BAT. > I want to be sure that we all understand and address the same issue. > Thanks > > /Sorin > > On Mon, 18 Oct 2010 15:59:17 -0400, Spencer Shepler > <spencer.shepler@gmail.com> wrote: > > > > > Sorin, > > > > Is the information or position you plan to present unsuitable for > > the initial discussion via the WG alias? My preference is that > > we start here and finish at the WG meeting to trim a few weeks > > from closing on these items. > > > > Spencer > > > >> -----Original Message----- > >> From: nfsv4-bounces@ietf.org [mailto:nfsv4-bounces@ietf.org] On Behalf > >> Of > >> sfaibish > >> Sent: Monday, October 18, 2010 12:41 PM > >> To: Thomas Haynes > >> Cc: nfsv4@ietf.org > >> Subject: Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00.txt > >> > >> Tom and Spencer, > >> > >> > >> I propose to have a discussion on this topic at the IETF meeting. 10 > >> minutes should be enough. I have a problem with pushing this to 4.2 > when > >> we may need to address the issue sooner. > >> > >> /Sorin > >> > >> On Mon, 18 Oct 2010 15:28:05 -0400, Thomas Haynes <thomas@netapp.com> > >> wrote: > >> > >> > Minor nits: > >> > > >> > Page 7: > >> > > >> > same server identifier. An example of well generated server > >> > identifier can be the one that includes the following: > >> > (c) > >> > (a) a) MAC address > >> > (b) b) Machine serial number > >> > > >> > I would expect these items to be part of (b) above (The ':' gives me > >> > that expectation). > >> > > >> > I find the (a) a) to be confusing. > >> > > >> > ---- > >> > > >> > Page 10: > >> > > >> > instead of the client IP address, for the indexing, as explained > >> here > >> > - > >> > > >> > As mentioned in Client Identification (Section 6) - > >> > > >> > The client SHOULD always send the same client string, irrespective > >> > of I can't tell if this is bad formatting or if two paragraphs are > >> missing. > >> > > >> > > >> > ---- > >> > > >> > There are scenarios where NFS implementations need to store IP > >> > addresses in persistent storage, like - > >> > > >> > NSM monitor/notify database. > >> > > >> > persistent reply cache. > >> > > >> > I believe you want this lettered. > >> > > >> > ------- > >> > > >> > A larger question on the draft as a whole would be whether we could > >> > add some additional operations to NFSv4.2 to get rid of the guessing. > >> > I.e., could a client send a server a list of IPv4 and IPv6 addresses > >> > that it is using and in return the server respond with the > equivalence > >> > addresses that it is using? > >> > > >> > One issue I can see is that the machines might be on different > subnets > >> > that use the same IP addresses. I.e., 192.168.2.14 on the filer's e0a > >> > might be a different private subnet than the 192.168.2.15 on the > >> > client's e1. > >> > > >> > --------- > >> > > >> > Finally, it is understated, so I think you should bring more > attention > >> > to it, but the problem you deal with in Section 6 applies to > symmetric > >> > single stack mode topologies as well. I.e., all current multi-homed > >> > IPv4 deployments. > >> > > >> > >> > >> > >> -- > >> Best Regards > >> > >> Sorin Faibish > >> Corporate Distinguished Engineer > >> Unified Storage Division > >> EMC² > >> where information lives > >> > >> Phone: 508-249-5745 > >> Cellphone: 617-510-0422 > >> Email : sfaibish@emc.com > >> _______________________________________________ > >> nfsv4 mailing list > >> nfsv4@ietf.org > >> https://www.ietf.org/mailman/listinfo/nfsv4 > > > > > > > > > > -- > Best Regards > > Sorin Faibish > Corporate Distinguished Engineer > Unified Storage Division > EMC² > where information lives > > Phone: 508-249-5745 > Cellphone: 617-510-0422 > Email : sfaibish@emc.com
- [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00.txt Internet-Drafts
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Thomas Haynes
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… sfaibish
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Trond Myklebust
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Spencer Shepler
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… sfaibish
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Nicolas Williams
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Trond Myklebust
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Thomas Haynes
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Thomas Haynes
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… dhawal bhagwat
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… dhawal bhagwat
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Spencer Shepler
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… dhawal bhagwat
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Trond Myklebust
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… Trond Myklebust
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… dhawal bhagwat
- Re: [nfsv4] I-D Action:draft-ietf-nfsv4-ipv4v6-00… dhawal bhagwat