[nfsv4] Fwd: RFC 5531 on RPC: Remote Procedure Call Protocol Specification Version 2
Spencer Shepler <shepler@storspeed.com> Tue, 05 May 2009 02:16 UTC
Return-Path: <shepler@storspeed.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A4D93A6A7F for <nfsv4@core3.amsl.com>; Mon, 4 May 2009 19:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wWXw15HCXRZ for <nfsv4@core3.amsl.com>; Mon, 4 May 2009 19:16:43 -0700 (PDT)
Received: from mail.storspeed.com (mail.storspeed.com [209.163.168.123]) by core3.amsl.com (Postfix) with ESMTP id 658513A6A13 for <nfsv4@ietf.org>; Mon, 4 May 2009 19:16:43 -0700 (PDT)
Received: from [192.168.0.5] (adsl-75-60-183-96.dsl.austtx.sbcglobal.net [75.60.183.96]) (authenticated bits=0) by mail.storspeed.com (8.14.3/8.14.3) with ESMTP id n452Hkh7078027 for <nfsv4@ietf.org>; Mon, 4 May 2009 21:18:05 -0500 (CDT) (envelope-from shepler@storspeed.com)
Message-Id: <5C031F78-8FDB-4501-8629-6726FFC3B021@storspeed.com>
From: Spencer Shepler <shepler@storspeed.com>
To: nfsv4@ietf.org
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 04 May 2009 21:17:40 -0500
References: <20090504234403.C89DE29B2B2@bosco.isi.edu>
X-Mailer: Apple Mail (2.930.3)
Subject: [nfsv4] Fwd: RFC 5531 on RPC: Remote Procedure Call Protocol Specification Version 2
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 05 May 2009 02:16:44 -0000
Yeah! Thanks for following through with this, Rob! Spencer Begin forwarded message: > From: rfc-editor@rfc-editor.org > Date: May 4, 2009 6:44:03 PM CDT > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: nfsv4@ietf.org, rfc-editor@rfc-editor.org > Subject: [nfsv4] RFC 5531 on RPC: Remote Procedure Call Protocol > Specification Version 2 > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5531 > > Title: RPC: Remote Procedure Call Protocol > Specification Version 2 > Author: R. Thurlow > Status: Standards Track > Date: May 2009 > Mailbox: robert.thurlow@sun.com > Pages: 63 > Characters: 161720 > Obsoletes: RFC1831 > > I-D Tag: draft-ietf-nfsv4-rfc1831bis-13.txt > > URL: http://www.rfc-editor.org/rfc/rfc5531.txt > > This document describes the Open Network Computing (ONC) Remote > Procedure Call (RPC) version 2 protocol as it is currently > deployed and accepted. This document obsoletes RFC 1831. > [STANDARDS TRACK] > > This document is a product of the Network File System Version 4 > Working Group of the IETF. > > This is now a Draft Standard Protocol. > > 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 Internet > Official Protocol Standards (STD 1) 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 > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html > . > For downloading RFCs, see http://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 > USC/Information Sciences Institute > > > _______________________________________________ > nfsv4 mailing list > nfsv4@ietf.org > https://www.ietf.org/mailman/listinfo/nfsv4
- [nfsv4] RFC 5531 on RPC: Remote Procedure Call Pr… rfc-editor
- [nfsv4] Fwd: RFC 5531 on RPC: Remote Procedure Ca… Spencer Shepler