Subject: RFC 7862 on Network File System (NFS) Version 4 Minor Version 2 Protocol

From: [email-masked]
Date: Thu, 10 Nov 2016 13:41:20 -0800 (PST)

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:    [email-masked]
        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 [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC