< draft-cel-nfsv4-rpcrdma-version-two-08.txt   draft-cel-nfsv4-rpcrdma-version-two-09.txt >
Network File System Version 4 C. Lever, Ed. Network File System Version 4 C. Lever, Ed.
Internet-Draft Oracle Internet-Draft Oracle
Intended status: Standards Track D. Noveck Intended status: Standards Track D. Noveck
Expires: May 12, 2019 NetApp Expires: November 7, 2019 NetApp
November 8, 2018 May 6, 2019
RPC-over-RDMA Version 2 Protocol RPC-over-RDMA Version 2 Protocol
draft-cel-nfsv4-rpcrdma-version-two-08 draft-cel-nfsv4-rpcrdma-version-two-09
Abstract Abstract
This document specifies a new version of the transport protocol that This document specifies a new version of the transport protocol that
conveys Remote Procedure Call (RPC) messages on physical transports conveys Remote Procedure Call (RPC) messages on physical transports
capable of Remote Direct Memory Access (RDMA). The new version of capable of Remote Direct Memory Access (RDMA). The new version of
this protocol is extensible. this protocol is extensible.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 12, 2019. This Internet-Draft will expire on November 7, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 48 skipping to change at page 4, line 48
header whose job it is to describe the RPC message and its associated header whose job it is to describe the RPC message and its associated
memory resources. In that regard, the reader is assumed to memory resources. In that regard, the reader is assumed to
understand how RDMA is used to transfer chunks between client and understand how RDMA is used to transfer chunks between client and
server, the use of Position-Zero Read chunks and Reply chunks to server, the use of Position-Zero Read chunks and Reply chunks to
convey Long RPC messages, and the role of DDP-eligibility in convey Long RPC messages, and the role of DDP-eligibility in
constraining how data payloads are to be conveyed. constraining how data payloads are to be conveyed.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119] [RFC8174] "OPTIONAL" in this document are to be interpreted as described in BCP
when, and only when, they appear in all capitals, as shown here. 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. RPC-over-RDMA Version 2 Headers and Chunks 3. RPC-over-RDMA Version 2 Headers and Chunks
Most RPC-over-RDMA version 2 data structures are derived from Most RPC-over-RDMA version 2 data structures are derived from
corresponding structures in RPC-over-RDMA version 1. As is typical corresponding structures in RPC-over-RDMA version 1. As is typical
for new versions of an existing protocol, the XDR data structures for new versions of an existing protocol, the XDR data structures
have new names and there are a few small changes in content. In some have new names and there are a few small changes in content. In some
cases, there have been structural re-organizations to enabled cases, there have been structural re-organizations to enabled
protocol extensibility. protocol extensibility.
 End of changes. 5 change blocks. 
8 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/