IETF Logo Mail Archive

Re: [nfsv4] I-D Action: draft-ietf-nfsv4-mv0-trunking-update-04.txt

Chuck Lever <chuck.lever@oracle.com> Fri, 01 February 2019 21:19 UTC

Return-Path: <chuck.lever@oracle.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 4C9E9130E8F; Fri, 1 Feb 2019 13:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.853
X-Spam-Level:
X-Spam-Status: No, score=-8.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.com
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 KdB8OCmKyLVu; Fri, 1 Feb 2019 13:19:03 -0800 (PST)
Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) (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 11AF1124408; Fri, 1 Feb 2019 13:19:03 -0800 (PST)
Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id x11LJ1fJ137991; Fri, 1 Feb 2019 21:19:01 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2018-07-02; bh=cOahHsEMccRBjN1Jc3D2hDyVytxxPvd0hCsS3Br1/5Q=; b=khYiiyc8W/DwZdfPW0qICjiFlI7ad6VtTK+0SxhR33xdvMg3zFvjMLcBk6ooEqQ108hh OP0hnkW3eHv9/U8EvQb5JbTHqzrs+k6oUuBRHq7NUx3OwMfmzb5VAehQI+AgKrClxseM JdryHmW2r0WifCUV0qWRGoE+qqZOqiaXvqM2ruFhqhd67iqFux8c/45XiLGZfgjiR1nu 2fUcGggHIZDLqJlKfVls32pQV+dgOPB77UxiclNzX9Ks8MNjdSpigzcZPLBUfM76WgEh T8zqfiViU01CbIBk0WzPAEq+3R8DHV8GMDCqioS7H2GUhEII7+iWo7hJysTb4mMqoQm9 wg==
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2130.oracle.com with ESMTP id 2q8eyv0wqh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 01 Feb 2019 21:19:01 +0000
Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id x11LJ043002357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 1 Feb 2019 21:19:00 GMT
Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id x11LIxUi027031; Fri, 1 Feb 2019 21:18:59 GMT
Received: from anon-dhcp-171.1015granger.net (/68.61.232.219) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 01 Feb 2019 13:18:59 -0800
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <CAKKJt-e7NDj9_7idq=s97xczp7oTRg820-xUx8bieGbwkQOT6Q@mail.gmail.com>
Date: Fri, 01 Feb 2019 16:18:56 -0500
Cc: Benjamin Kaduk <kaduk@mit.edu>, draft-ietf-nfsv4-mv0-trunking-update@ietf.org, Ben Campbell <ben@nostrum.com>, nfsv4-chairs@ietf.org, NFSv4 <nfsv4@ietf.org>, The IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <889431F6-4822-4C51-9020-36E3B1F78E32@oracle.com>
References: <154903185895.28504.17927048108992520591@ietfa.amsl.com> <06AE6508-A280-418C-81E3-EEA0EF961627@oracle.com> <20190201170533.GJ93251@kduck.mit.edu> <A0090122-B1D9-4C27-8C5A-9F2F511418A6@oracle.com> <CAKKJt-e7NDj9_7idq=s97xczp7oTRg820-xUx8bieGbwkQOT6Q@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9154 signatures=668682
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=787 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1902010150
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/MvSVipvdV5KpPq1-wUE94OptDTk>
Subject: Re: [nfsv4] I-D Action: draft-ietf-nfsv4-mv0-trunking-update-04.txt
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: Fri, 01 Feb 2019 21:19:05 -0000

Hi Spencer (D) -

> On Feb 1, 2019, at 4:08 PM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
> 
> Hi, Chuck, 
> 
>> On Fri, Feb 1, 2019 at 11:09 AM Chuck Lever <chuck.lever@oracle.com> wrote:
>> 
>> 
>> > On Feb 1, 2019, at 12:05 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:
>> > 
>> > On Fri, Feb 01, 2019 at 09:44:11AM -0500, Chuck Lever wrote:
>> >> 
>> >> 
>> >> Revision -04 attempts to address the outstanding DISCUSS and COMMENT
>> >> ballot positions. An XML comment requests RFC Editor attention to the
>> > 
>> > It does so [*], and I've cleared in the datatracker.
>> > 
>> >> concern about "this document" v. "the current document".
>> > 
>> > Excellent; thank you.
>> > 
>> > -Benjamin
>> > 
>> > 
>> > [*] I think Section 5.2.3 was going to go with "need to support multiple
>> > connection types" as well as the other changes made.
>> 
>> This sentence?
>> 
>>    Because of the need to support multiple connections, clients face the
>>    issue of determining the proper connection type to use when
>>    establishing a connection to a server network address.
>> 
>> I think you are correct, sorry for the oversight. I can either submit
>> another revision with this change or communicate the change to the RFC
>> Editor during AUTH48.
> 
> It would be fine with me if you could submit that revision. That's more reliable than remembering a change to be made in AUTH48, especially with your AD switching out in the middle of the process.

Done.


--
Chuck Lever

v2.23.0 | Report a Bug | By Email