draft-ietf-nfsv4-rfc5666bis-09.txt   draft-ietf-nfsv4-rfc5666bis-10.txt 
Network File System Version 4 C. Lever, Ed. Network File System Version 4 C. Lever, Ed.
Internet-Draft Oracle Internet-Draft Oracle
Obsoletes: 5666 (if approved) W. Simpson Obsoletes: 5666 (if approved) W. Simpson
Intended status: Standards Track DayDreamer Intended status: Standards Track DayDreamer
Expires: July 23, 2017 T. Talpey Expires: August 12, 2017 T. Talpey
Microsoft Microsoft
January 19, 2017 February 8, 2017
Remote Direct Memory Access Transport for Remote Procedure Call, Version Remote Direct Memory Access Transport for Remote Procedure Call, Version
One One
draft-ietf-nfsv4-rfc5666bis-09 draft-ietf-nfsv4-rfc5666bis-10
Abstract Abstract
This document specifies a protocol for conveying Remote Procedure This document specifies a protocol for conveying Remote Procedure
Call (RPC) messages on physical transports capable of Remote Direct Call (RPC) messages on physical transports capable of Remote Direct
Memory Access (RDMA). It requires no revision to application RPC Memory Access (RDMA). It requires no revision to application RPC
protocols or the RPC protocol itself. This document obsoletes RFC protocols or the RPC protocol itself. This document obsoletes RFC
5666. 5666.
Requirements Language Requirements Language
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 July 23, 2017. This Internet-Draft will expire on August 12, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 15, line 15 skipping to change at page 15, line 15
Offset Offset
The offset or beginning memory address of the RDMA segment's The offset or beginning memory address of the RDMA segment's
memory region. memory region.
See [RFC5040] for further discussion of the meaning and use of these See [RFC5040] for further discussion of the meaning and use of these
fields. fields.
3.4.4. Chunks 3.4.4. Chunks
In RPC-over-RDMA Version One, a "chunk" refers to a portion of the In RPC-over-RDMA Version One, a "chunk" refers to a portion of the
Payload stream that is moved independently of the the RPC-over-RDMA Payload stream that is moved independently of the RPC-over-RDMA
Transport header and Payload stream. Chunk data is removed from the Transport header and Payload stream. Chunk data is removed from the
sender's Payload stream, transferred via separate operations, and sender's Payload stream, transferred via separate operations, and
then re-inserted into the receiver's Payload stream to form a then re-inserted into the receiver's Payload stream to form a
complete RPC message. complete RPC message.
Each chunk consists of one or more RDMA segments. Each RDMA segment Each chunk consists of one or more RDMA segments. Each RDMA segment
represents a single contiguous piece of that chunk. A requester MAY represents a single contiguous piece of that chunk. A requester MAY
divide a chunk into RDMA segments using any boundaries that are divide a chunk into RDMA segments using any boundaries that are
convenient. The length of a chunk is the sum of the lengths of the convenient. The length of a chunk is the sum of the lengths of the
RDMA segments that comprise it. RDMA segments that comprise it.
 End of changes. 5 change blocks. 
5 lines changed or deleted 5 lines changed or added

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