IETF Logo Mail Archive

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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 01 February 2019 21:08 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 1F9D0130E8F; Fri, 1 Feb 2019 13:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 aL30NN-6prf8; Fri, 1 Feb 2019 13:08:52 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EB23124408; Fri, 1 Feb 2019 13:08:52 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id q2-v6so6952846lji.10; Fri, 01 Feb 2019 13:08:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Mo/XlVjvHh6evjZuR3qlFZamItaYa84BO/2lRzieazI=; b=PdR6Tz43OdAd+lEIyQdlmzUrHFS6qXbiUEyapr/7bDuN2mnEPWaxx+qIUmEbWpwJeo 7IlY249BmotxMTcnMLu5xEt7ZGWxjMuyz6Nt8ColXfkNgIOt1lCn0sMsh934rF8XVXmp St+OgGhw77utrtVGANIX/+EqSH52egXnUCcDfDfP6LZ1K+YAa2dhGb19xe/yk+lhfPTu FM97HE3WNxlYT2Y+r9qI/JaoaJEWtgb7Av0tcAe9KxgQwX2T9erSNDMdjQv1CZLFO/7C eRMfrTdFNVHQOQxXMwy49ND9swJW2H9ZWIqpleSyzVW9YRk9Iv5iNxFEcNEjgAQmUVF0 OSfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Mo/XlVjvHh6evjZuR3qlFZamItaYa84BO/2lRzieazI=; b=oWQ6GyB56PPC2N9l8QL+FkRCdNuqRsx9+i+sKeKb6xrcet+wo8nEoVPUD9dPljrsiO UlKnKwvQUUmv2Z5dwIZWMga4TJkLx/+i7iLxza9zwoLqHeb9lLQ8Z8Q1+FSeVQviIwu7 0wOkuqJrHKVJs1jQymcgVXfiP7GUxPq1cQRT9JEnK4q6VXGnVaEq8fXstk/AZ3cs4FEF Ot3jbHQ4CRJpUda4KU9qvNimObJcT9zzlS1yM99A7sinkEzJHgh9VPWb2QrRlP9cWSki spZ4hb6RymAJ4NAaThSbnd0UTPQOt8JVNrew7g0TW/8IfOmP8vqONaSLb6TMmximcYMV +yHA==
X-Gm-Message-State: AHQUAuYxCXRbCw+sxnsbFFrEN5VF8NYqa+DUWoz8JP6PRDUdT8IVOnbT cZyY55cm3mC8bRwyk2CLw7E9GpteAD06sH6HihI=
X-Google-Smtp-Source: AHgI3Ibk/wOOLD51xVyMpjg5c/9plTKbVoGJ6Sqp2tMTBzWPsyb/EBM2wbUSNs592PZZ6djHysD5KKmP2oibeSxjbwE=
X-Received: by 2002:a2e:8596:: with SMTP id b22-v6mr6429250lji.122.1549055330546; Fri, 01 Feb 2019 13:08:50 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <A0090122-B1D9-4C27-8C5A-9F2F511418A6@oracle.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 01 Feb 2019 15:08:38 -0600
Message-ID: <CAKKJt-e7NDj9_7idq=s97xczp7oTRg820-xUx8bieGbwkQOT6Q@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
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-Type: multipart/alternative; boundary="000000000000b6f9e60580db8c6b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Eb_4sdQHrx_ECXazCXVOE_zHlRQ>
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:08:55 -0000

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.

Thanks!

Spencer

v2.23.0 | Report a Bug | By Email