Re: [nfsv4] Benjamin Kaduk's No Objection on draft-ietf-nfsv4-rpcrdma-cm-pvt-data-07: (with COMMENT)

Chuck Lever <chuck.lever@oracle.com> Sun, 01 March 2020 18:14 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 1E8603A0A5D; Sun, 1 Mar 2020 10:14:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level:
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 9wDdzGG-3Bh7; Sun, 1 Mar 2020 10:14:14 -0800 (PST)
Received: from userp2120.oracle.com (userp2120.oracle.com [156.151.31.85]) (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 19F173A0AAC; Sun, 1 Mar 2020 10:14:08 -0800 (PST)
Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 021ICpYp048875; Sun, 1 Mar 2020 18:14:02 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-2020-01-29; bh=COX5W6BNrz1i+7qWkvDgen5gOn0qGdDXRSHxUYrw9M4=; b=oVLKufzOmszS7cABPFLpJkStbry2MtZRVjxI+/OCZR4xjmsgGtS9yKWGSsxXrW47jv4/ xBrKiv6kjgWJSvQOh25bvGZGf22vWYr6YydkeOytdYd/vtK0rMRlZP3ZmlRPp//xAO9I Hns0FmMOhgCG5amxQIurCPKZzPkQSSSYehje7JBZflaHOHZ8ZhEtnEQZAGzhUZOUnFcU hJkQjCAxI5Qm/VAOogI58gLBg8KZnWV5s/vNSE68ZeID0pAmtPiTbvFtGARC7UeOC8iq GlwzmBd4q50ks1golxQvPO+H60e19QFNTFGbkTJRLPtzgPPH/pf9qQfRsknCEAKD+mCO ZQ==
Received: from userp3030.oracle.com (userp3030.oracle.com [156.151.31.80]) by userp2120.oracle.com with ESMTP id 2yghn2r1q1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 01 Mar 2020 18:14:01 +0000
Received: from pps.filterd (userp3030.oracle.com [127.0.0.1]) by userp3030.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 021ICwmZ073809; Sun, 1 Mar 2020 18:14:01 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userp3030.oracle.com with ESMTP id 2yg1ef1331-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 01 Mar 2020 18:14:01 +0000
Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id 021IE0AP023515; Sun, 1 Mar 2020 18:14:00 GMT
Received: from anon-dhcp-153.1015granger.net (/68.61.232.219) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 01 Mar 2020 10:14:00 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <e74002a7-e1f1-a738-20d4-fa7d3395dd66@talpey.com>
Date: Sun, 1 Mar 2020 13:13:59 -0500
Cc: Benjamin Kaduk <kaduk@mit.edu>, nfsv4-chairs@ietf.org, nfsv4@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-nfsv4-rpcrdma-cm-pvt-data@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE0ECB52-596B-467C-BEB4-D76319016E32@oracle.com>
References: <158216101788.17661.6926758160404035704.idtracker@ietfa.amsl.com> <E718C1B8-B96B-4A64-8B92-C4ABEC7B5E5F@oracle.com> <20200220195155.GJ97652@kduck.mit.edu> <e74002a7-e1f1-a738-20d4-fa7d3395dd66@talpey.com>
To: Tom Talpey <tom@talpey.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9547 signatures=668685
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 suspectscore=0 spamscore=0 mlxlogscore=999 malwarescore=0 bulkscore=0 mlxscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2003010143
X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9547 signatures=668685
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 phishscore=0 spamscore=0 impostorscore=0 mlxscore=0 adultscore=0 mlxlogscore=999 lowpriorityscore=0 priorityscore=1501 bulkscore=0 clxscore=1011 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2003010143
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/_Mlxwi6MKX0YEElN8t8WnavKBcA>
Subject: Re: [nfsv4] Benjamin Kaduk's No Objection on draft-ietf-nfsv4-rpcrdma-cm-pvt-data-07: (with COMMENT)
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: Sun, 01 Mar 2020 18:14:26 -0000


> On Mar 1, 2020, at 12:24 PM, Tom Talpey <tom@talpey.com> wrote:
> 
> On 2/20/2020 11:51 AM, Benjamin Kaduk wrote:
>> Hi Chuck,
>> On Thu, Feb 20, 2020 at 10:13:26AM -0500, Chuck Lever wrote:
>>> Hi Ben, thanks for your comments! Responses and questions below.
>>> 
>>> 
>>>> On Feb 19, 2020, at 8:10 PM, Benjamin Kaduk via Datatracker <noreply@ietf.org> wrote:
>>>> 
>>>> Benjamin Kaduk has entered the following ballot position for
>>>> draft-ietf-nfsv4-rpcrdma-cm-pvt-data-07: No Objection
>>>> 
>>>> When responding, please keep the subject line intact and reply to all
>>>> email addresses included in the To and CC lines. (Feel free to cut this
>>>> introductory paragraph, however.)
>>>> 
>>>> 
>>>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>> 
>>>> 
>>>> The document, along with other ballot positions, can be found here:
>>>> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-rpcrdma-cm-pvt-data/
>>>> 
>>>> ...
>>>> Section 6
>>>> 
>>>>   The RPC-over-RDMA version 1 protocol framework depends on the
>>>>   semantics of the Reliable Connected (RC) queue pair (QP) type, as
>>>>   defined in Section 9.7.7 of [IBA].  The integrity of CM Private Data
>>>> 
>>>> It's interesting to see such a reference to [IBA], when IIUC the RFC
>>>> 8166 protocol is not limited to Infiniband as the underlying transport.
>>> 
>>> Correct, RPC/RDMA can operate on iWARP and RoCE as well. However:
>>> 
>>>  - both of those RDMA fabric types also support RC QPs, and
>>>  - [IBA] appears to be the only publication where "RC QP type"
>>>    is defined, though I could be wrong.
>>> 
>>> I don't read this text as suggesting that RPC/RDMA cannot operate
>>> on those alternate fabrics, but perhaps I am "too close to the
>>> code".
>> I don't read it that way, either; I was just noting that it was surprising
>> that this is the only reference available.  If it is, then it is, though,
>> so no need to change anything.
> 
> The term "RC" or "Reliable Connected" is an InfiniBand-specific term.
> The iWARP protocol has neither a datagram nor unreliable mode, therefore
> it is an "RC" transport by definition, in InfiniBand-speak.
> 
> I do agree that referring normatively to the IB Architecture is odd,
> and perhaps unnecessary. Alternatively, the sentence could be relaxed
> to avoid this IB-specific term, and describe the situation in an
> informative way. "Supports RC-type Infiniband and iWARP Queue Pairs."

No objection to that phrasing, and that certainly explains why RFC 8166
does not refer directly to RC.


> There is a document describing the iWARP consumer-visible semantics,
> in 2003's https://tools.ietf.org/html/draft-hilland-rddp-verbs-00
> However, this document was never adopted as an RDDP work item, and
> was not developed further. It is nonetheless an excellent reference
> and is frequently referred to.
> 
> Tom.

--
Chuck Lever