RFC 7530 on Network File System (NFS) Version 4 Protocol

rfc-editor@rfc-editor.org Thu, 26 March 2015 18:35 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 4E1AB1B2A3C; Thu, 26 Mar 2015 11:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id M3DQ8kmUewcS; Thu, 26 Mar 2015 11:35:48 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id B8DC21A92EA; Thu, 26 Mar 2015 11:35:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 21F2B18020A; Thu, 26 Mar 2015 11:34:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7530 on Network File System (NFS) Version 4 Protocol
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150326183414.21F2B18020A@rfc-editor.org>
Date: Thu, 26 Mar 2015 11:34:14 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/YKYUfqoh4wOBvIA4yPhd7hTkWAA>
Cc: drafts-update-ref@iana.org, nfsv4@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2015 18:35:50 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7530

        Title:      Network File System (NFS) Version 4 Protocol 
        Author:     T. Haynes, Ed.,
                    D. Noveck, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2015
        Mailbox:    thomas.haynes@primarydata.com, 
        Pages:      323
        Characters: 724613
        Obsoletes:  RFC 3530

        I-D Tag:    draft-ietf-nfsv4-rfc3530bis-35.txt

        URL:        https://www.rfc-editor.org/info/rfc7530

The Network File System (NFS) version 4 protocol is a distributed
file system protocol that builds on the heritage of NFS protocol
version 2 (RFC 1094) and version 3 (RFC 1813).  Unlike earlier
versions, the NFS version 4 protocol supports traditional file access
while integrating support for file locking and the MOUNT protocol.
In addition, support for strong security (and its negotiation),
COMPOUND operations, client caching, and internationalization has
been added.  Of course, attention has been applied to making NFS
version 4 operate well in an Internet environment.

This document, together with the companion External Data
Representation (XDR) description document, RFC 7531, obsoletes RFC
3530 as the definition of the NFS version 4 protocol.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

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