[nfsv4] RFC 7862 on Network File System (NFS) Version 4 Minor Version 2 Protocol
rfc-editor@rfc-editor.org Thu, 10 November 2016 21:41 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 1D0681297FE; Thu, 10 Nov 2016 13:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level:
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 68hCcojnx703; Thu, 10 Nov 2016 13:41:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B5BD1296EC; Thu, 10 Nov 2016 13:41:20 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4BA66B80108; Thu, 10 Nov 2016 13:41:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161110214120.4BA66B80108@rfc-editor.org>
Date: Thu, 10 Nov 2016 13:41:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/_HSjG0b7WjBgMvurOn3yImC4_Gs>
Cc: drafts-update-ref@iana.org, nfsv4@ietf.org, rfc-editor@rfc-editor.org
Subject: [nfsv4] RFC 7862 on Network File System (NFS) Version 4 Minor Version 2 Protocol
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 10 Nov 2016 21:41:32 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7862
Title: Network File System (NFS) Version 4
Minor Version 2 Protocol
Author: T. Haynes
Status: Standards Track
Stream: IETF
Date: November 2016
Mailbox: thomas.haynes@primarydata.com
Pages: 104
Characters: 237870
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-nfsv4-minorversion2-41.txt
URL: https://www.rfc-editor.org/info/rfc7862
DOI: http://dx.doi.org/10.17487/RFC7862
This document describes NFS version 4 minor version 2; it describes
the protocol extensions made from NFS version 4 minor version 1.
Major extensions introduced in NFS version 4 minor version 2 include
the following: Server-Side Copy, Application Input/Output (I/O)
Advise, Space Reservations, Sparse Files, Application Data Blocks,
and Labeled NFS.
This document is a product of the Network File System Version 4 Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC