IETF Logo Mail Archive

Re: [Last-Call] [nfsv4] Genart last call review of draft-ietf-nfsv4-rpc-tls-07

worley@ariadne.com Thu, 28 May 2020 03:05 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8449E3A0B5E for <last-call@ietfa.amsl.com>; Wed, 27 May 2020 20:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Level:
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 R9LPAV7UHeku for <last-call@ietfa.amsl.com>; Wed, 27 May 2020 20:05:32 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (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 A45F23A0B53 for <last-call@ietf.org>; Wed, 27 May 2020 20:05:32 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-02v.sys.comcast.net with ESMTP id e8jwjwSR5joMle8rLjXfEU; Thu, 28 May 2020 03:05:31 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1590635131; bh=rIizx90bk8MH5Ep/VwMo6KaQJ7M8NW/aVx5Snkc90M0=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=AurunU4sKfpwIUzsoRcU48tDHkLSfIX2S2599SRoHh4C2ZicUWwG5LU6xfgYKNRPB nAQQaUu44lfP6Ucl/3+gXeOB+uBYP3gyV/5speIQK/z/km9E1IgGREuqrdCYagloQq W1954cjRmaeoTfhVd7U7i159okIq6+PYXDGtNnmn6Wk6aM7BD2NoyMtCHqmETBWkjY 3qR2Y/veUaBjXGqV5GtzJprHhejZQMfUUsni7qgh5VpPFeDu1NgzM7AEHRsEP/ohJx I732d3gwsUYX+a2owv6vHcpwgXL6JjTRtE5nN1cj5vo03X290hDx4zpnrTzfz6SPZW IXM9mtT3dpdvQ==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-10v.sys.comcast.net with ESMTPA id e8rJj8EEVWhYwe8rKjueHC; Thu, 28 May 2020 03:05:31 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 04S35TFW025305; Wed, 27 May 2020 23:05:29 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 04S35T24025302; Wed, 27 May 2020 23:05:29 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Chuck Lever <chuck.lever@oracle.com>
Cc: davenoveck@gmail.com, gen-art@ietf.org, last-call@ietf.org, nfsv4@ietf.org, draft-ietf-nfsv4-rpc-tls.all@ietf.org
In-Reply-To: <0AA91E8D-A743-4730-A319-10A556C985C5@oracle.com> (chuck.lever@oracle.com)
Sender: worley@ariadne.com
Date: Wed, 27 May 2020 23:05:28 -0400
Message-ID: <87mu5siwsn.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/VKJA2l9WGdW3mZo9R3niE6cF6JA>
Subject: Re: [Last-Call] [nfsv4] Genart last call review of draft-ietf-nfsv4-rpc-tls-07
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2020 03:05:34 -0000

Chuck Lever <chuck.lever@oracle.com> writes:
> I'm not comfortable citing an NFSv4 document to define a term used in
> a document that discusses a generic RPC transport. To me that feels an
> awful lot like a layering violation.

If doing that would be a layering violation, then this passage is also a
layering violation:

   To protect backchannel operations, an RPC server uses the
   existing TLS session on that connection to send backchannel
   operations.  The server does not attempt to establish a TLS session
   on a TCP connection for backchannel operation.

Dale

v2.23.0 | Report a Bug | By Email