Re: [nfsv4] New Version Notification for draft-myklebust-nfsv42-unstable-file-creation-00
Trond Myklebust <trond.myklebust@fys.uio.no> Sun, 17 October 2010 21:10 UTC
Return-Path: <trond.myklebust@fys.uio.no>
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 DADFF3A6C17 for <nfsv4@core3.amsl.com>; Sun, 17 Oct 2010 14:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.351
X-Spam-Level:
X-Spam-Status: No, score=-6.351 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Cg3nW9+80g-g for <nfsv4@core3.amsl.com>; Sun, 17 Oct 2010 14:10:53 -0700 (PDT)
Received: from mail-out2.uio.no (mail-out2.uio.no [129.240.10.58]) by core3.amsl.com (Postfix) with ESMTP id 3D3693A6B1D for <nfsv4@ietf.org>; Sun, 17 Oct 2010 14:10:52 -0700 (PDT)
Received: from mail-mx1.uio.no ([129.240.10.29]) by mail-out2.uio.no with esmtp (Exim 4.69) (envelope-from <trond.myklebust@fys.uio.no>) id 1P7aWg-0001ad-0D; Sun, 17 Oct 2010 23:12:18 +0200
Received: from c-68-40-206-115.hsd1.mi.comcast.net ([68.40.206.115] helo=[192.168.1.29]) by mail-mx1.uio.no with esmtpsa (SSLv3:CAMELLIA256-SHA:256) user trondmy (Exim 4.69) (envelope-from <trond.myklebust@fys.uio.no>) id 1P7aWf-0000dB-6l; Sun, 17 Oct 2010 23:12:17 +0200
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: nfsv4@ietf.org, Spencer Shepler <sshepler@microsoft.com>, Brian Pawlowski <Brian.Pawlowski@netapp.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sun, 17 Oct 2010 17:12:13 -0400
Message-ID: <1287349934.11725.4.camel@heimdal.trondhjem.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 (2.30.3-1.fc13)
Content-Transfer-Encoding: 7bit
X-UiO-Ratelimit-Test: rcpts/h 3 msgs/h 1 sum rcpts/h 4 sum msgs/h 1 total rcpts 1034 max rcpts/h 20 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: CB4EA2C5575405C08A1DB13EDDAB83D2098FD061
X-UiO-SPAM-Test: remote_host: 68.40.206.115 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 411 max/h 7 blacklist 0 greylist 0 ratelimit 0
Subject: Re: [nfsv4] New Version Notification for draft-myklebust-nfsv42-unstable-file-creation-00
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: Sun, 17 Oct 2010 21:10:57 -0000
Hi, I'd like to request 5-10 minutes at the Beijing meeting in order to discuss the following proposal. Cheers Trond > A new version of I-D, > draft-myklebust-nfsv42-unstable-file-creation-00.txt has been > successfully submitted by Trond Myklebust and posted to the IETF > repository. > > Filename: draft-myklebust-nfsv42-unstable-file-creation > Revision: 00 > Title: NFS Version 4 Minor Version 2 unstable file creation > and attribute update improvements > Creation_date: 2010-10-17 > WG ID: Independent Submission > Number_of_pages: 14 > > http://www.ietf.org/id/draft-myklebust-nfsv42-unstable-file-creation-00.txt > > Abstract: > This document describes an extension to the NFSv4 protocol to allow > clients to create and write files with greater efficiency. > > The first proposal allows the server to defer creating the file on > stable storage when replying to an OPEN call. The aim is to improve > server efficiency and scalability by reducing the number of required > disk accesses when writing a file from scratch. > > The second proposal allows the server to share information about the > implementation of its change attribute with the client. The aim is > to improve the client's ability to determine the order in which > parallel updates to the same file were processed.Keywords > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this > document are to be interpreted as described in [RFC2119].
- Re: [nfsv4] New Version Notification for draft-my… Trond Myklebust