|
Internet Drafts - IDs for Dec/2008
Index - Month Index of IDs
All IDs - sorted by date)
23/12/2008
| |
|
| |
| | pNFS Block/Volume Layout |
| |
|
Parallel NFS (pNFS) extends NFSv4 to allow clients to directly access file data on the storage used by the NFSv4 server. This ability to bypass the server for data access can increase both performance and parallelism, but requires additional client functionality for data access, some of which is dependent on the class of storage used. The main pNFS operations draft specifies storage-class-independent extensions to NFS; this draft specifies the additional extensions (primarily data structures) for use of pNFS with block and volume based storage. |
19/12/2008
| |
|
| |
| | LDAP Transactions |
| |
|
Lightweight Directory Access Protocol (LDAP) update operations, such as Add, Delete, and Modify operations, have atomic, consistency, isolation, durability (ACID) properties. Each of these update operations act upon an entry. It is often desirable to update two or more entries in a single unit of interaction, a transaction. Transactions are necessary to support a number of applications including resource provisioning. This document extends LDAP to support transactions. |
15/12/2008
| |
|
| |
| | NFS Version 4 Minor Version 1 |
| |
|
This document describes NFS version 4 minor version one, including features retained from the base protocol (NFS version 4 minor version zero which is specified in RFC3530) and protocol extensions made subsequently. Major extensions introduced in NFS version 4 minor version one include: Sessions, Directory Delegations, and parallel NFS (pNFS). NFS version 4 minor version one has no dependencies on NFS version 4 minor version zero, and is considered a separate protocol. Thus this document neither updates nor obsoletes RFC3530. NFS minor version one is deemed superior to NFS minor version zero with no loss of functionality, and its use is preferred over version zero. Both NFS minor version zero and one can be used simultaneously on the same network, between the same client and server. |
| | Object-based pNFS Operations |
| |
|
Parallel NFS (pNFS) extends NFSv4 to allow clients to directly access file data on the storage used by the NFSv4 server. This ability to bypass the server for data access can increase both performance and parallelism, but requires additional client functionality for data access, some of which is dependent on the class of storage used, a.k.a. the Layout Type. The main pNFS operations and data types in NFSv4 Minor Version 1 specify a layout-type-independent layer; layout-type-specific information is conveyed using opaque data structures which internal structure is further defined by the particular layout type specification. This document specifies the NFSv4.1 Object-based pNFS Layout Type in companion with the main NFSv4 Minor Version 1 specification. |
| | NFSv4 Minor Version 1 XDR Description |
| |
|
This Internet-Draft provides the XDR description for NFSv4 minor version one. |
04/12/2008
| |
|
| |
| | Remote Direct Memory Access Transport for Remote Procedure Call |
| |
|
A protocol is described providing Remote Direct Memory Access (RDMA) as a new transport for Remote Procedure Call (RPC). The RDMA transport binding conveys the benefits of efficient, bulk data transport over high speed networks, while providing for minimal change to RPC applications and with no required revision of the application RPC protocol, or the RPC protocol itself. |
01/12/2008
| |
|
| |
| | WiMAX Forum/3GPP2 Proxy Mobile IPv4 |
| |
|
Mobile IPv4 is a standard mobility protocol that enables IPv4 device to move among networks while maintaining its IP address. The mobile device has the Mobile IPv4 client function to signal its location to the routing anchor, known as the Home Agent. However, there are many IPv4 devices without such capability due to various reasons. This document describes Proxy Mobile IPv4 (PMIPv4), a scheme based on having the Mobile IPv4 client function in a network entity to provide mobility support for an unaltered and mobility-unaware IPv4 device. This document also describes a particular application of PMIPv4 as specified in the WiMAX Forum and another application that is to be adopted in 3GPP2 |
|
