RFC 8000 on Requirements for NFSv4 Multi-Domain Namespace Deployment
rfc-editor@rfc-editor.org Wed, 30 November 2016 23:52 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA8DA129BDF; Wed, 30 Nov 2016 15:52:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.098
X-Spam-Level:
X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, 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 9IJfIpinzHRm; Wed, 30 Nov 2016 15:51:59 -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 4C19F129BE3; Wed, 30 Nov 2016 15:51:52 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 02ACDB808AF; Wed, 30 Nov 2016 15:51:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8000 on Requirements for NFSv4 Multi-Domain Namespace Deployment
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161130235152.02ACDB808AF@rfc-editor.org>
Date: Wed, 30 Nov 2016 15:51:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/zIQVKzA1vLQ0bvYf3RrEyCyfuRQ>
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.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 30 Nov 2016 23:52:04 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8000 Title: Requirements for NFSv4 Multi-Domain Namespace Deployment Author: A. Adamson, N. Williams Status: Standards Track Stream: IETF Date: November 2016 Mailbox: andros@netapp.com, nico@cryptonector.com Pages: 17 Characters: 39064 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nfsv4-multi-domain-fs-reqs-11.txt URL: https://www.rfc-editor.org/info/rfc8000 DOI: 10.17487/RFC8000 This document presents requirements for the deployment of the NFSv4 protocols for the construction of an NFSv4 file namespace in environments with multiple NFSv4 Domains. To participate in an NFSv4 multi-domain file namespace, the server must offer a multi-domain-capable file system and support RPCSEC_GSS for user authentication. In most instances, the server must also support identity-mapping services. 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