Re: [nfsv4] I-D Action: draft-ietf-nfsv4-flex-files-13.txt

Thomas Haynes <> Tue, 15 August 2017 16:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AD0CD132256 for <>; Tue, 15 Aug 2017 09:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AIJVnDB7Fowq for <>; Tue, 15 Aug 2017 09:20:22 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 58DF0132191 for <>; Tue, 15 Aug 2017 09:20:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=mimecast20170802; t=1502814021; h=from:subject:date:message-id:to:cc:mime-version:content-type:in-reply-to:references; bh=gK4tgf1WTcgDOgQhEdWbhitjNENHM7Dec/6OiO/VKxo=; b=Y/sWQuBPEzF/iOmNfZRYzoqychxJ7hBK9Ey0lwu1jBMKopq2lU18nKo2pgf/NplkLowJd1vMD6Y4OhbWzc9daNC9K8xU2XNPgrSdsKrvRYcnRoeougC5XK6tpV58zWlXjLfx941qvHaWa8ajNOLTfwk28dsvFO1N4xwO2nRp+fc=
Received: from ( []) (Using TLS) by with ESMTP id us-mta-101-xIHSfNjwPwm0-A51SOIpiQ-1; Tue, 15 Aug 2017 12:20:17 -0400
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1341.21; Tue, 15 Aug 2017 16:20:11 +0000
Received: from ([]) by ([]) with mapi id 15.01.1341.020; Tue, 15 Aug 2017 16:20:11 +0000
From: Thomas Haynes <>
To: Dave Noveck <>
CC: Spencer Shepler <>, "" <>
Thread-Topic: [nfsv4] I-D Action: draft-ietf-nfsv4-flex-files-13.txt
Thread-Index: AQHTD9D0BrU7fFXJW0yjXv1DRi/8k6J5lYoAgACpqQCAAIkAgIAKg5EAgABZVoA=
Date: Tue, 15 Aug 2017 16:20:11 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR1101MB1093; 20:UzkRsZQ95tsDe2UV2dYnyvxwFmk+TIibJrz3Sc36k8Fi2AwaTZZh0+UWWU6cXtLhQjM73Fm6iuCq8p7O3N1Y6SdnyMSVA2qGslyMMGUVsFTGq6bpl4bbNIx3NUVMhTyOfV/eXNn24AjfWa4dXLwamB4/FrYzGnIR8cSN6nYHTt0=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 91bcc17d-c973-4f21-cea4-08d4e3f980fb
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(2017082002075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BY2PR1101MB1093;
x-ms-traffictypediagnostic: BY2PR1101MB1093:
x-exchange-antispam-report-test: UriScan:(158342451672863)(120809045254105)(192374486261705);
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123558100)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123555025)(2016111802025)(6072148)(6043046)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BY2PR1101MB1093; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2PR1101MB1093;
x-forefront-prvs: 04004D94E2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400002)(51914003)(24454002)(189002)(199003)(377454003)(377424004)(86362001)(2900100001)(3660700001)(8676002)(2906002)(189998001)(3280700002)(25786009)(6512007)(4326008)(7736002)(97736004)(99286003)(6306002)(606006)(54906002)(54896002)(83716003)(68736007)(230783001)(36756003)(236005)(93886004)(77096006)(39060400002)(76176999)(50986999)(5660300001)(54356999)(6486002)(14454004)(6916009)(6506006)(53936002)(2950100002)(1411001)(53546010)(478600001)(6436002)(966005)(101416001)(110136004)(229853002)(102836003)(6116002)(106356001)(105586002)(33656002)(82746002)(81156014)(81166006)(66066001)(8936002)(3846002)(6246003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR1101MB1093;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Aug 2017 16:20:11.4555 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 03193ed6-8726-4bb3-a832-18ab0d28adb7
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR1101MB1093
X-MC-Unique: xIHSfNjwPwm0-A51SOIpiQ-1
Content-Type: multipart/alternative; boundary="_000_11E1F7531A14439ABE4F25FF044BA35Bprimarydatacom_"
Archived-At: <>
Subject: Re: [nfsv4] I-D Action: draft-ietf-nfsv4-flex-files-13.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 Aug 2017 16:20:26 -0000

On Aug 15, 2017, at 4:00 AM, David Noveck <<>> wrote:

There is a need to adress the issue of a last call for flex-files-13.

I previously suggested extending the -12 LC to encompass the -13 and ending on 8/21, but Spencer on 8/8 responded:.

> Thanks for the suggestion, Dave.  However, we will let the timer run on the current last call (ends on Friday).

> Once that is complete, we will start another last call on the version of the I-D that is available then.

Since that last call ended on 8/11, the version available now is we have to start that new last call.

Wait, I would have held off shipping a v-13 if I had known it reset the last call.

I sent out v-13 as a courtesy to the reviewers.

> Note that this is always the case - if there has been enough change during a last call to warrant another round, then we do another last call.  Not a big deal.

I think it is pretty clear that there has been enough change.  If there is anyone who disagrees, please speak up..

The only remaIning issue is the the end date.  I previously proposed a two-week last call period to enable me to do
a comprehensive review.  Others might want to focus on the security changes in -13 but I skipped a comprehensive
review of -12 because it was always pretty clear there would have to be a -13.

Two weeks from today would be 8/29.  However, it may be simpler to make the end date the following Fridiay, which is 9/1.
Is Tom and the rest of the working group OK with that end date for the -13 WGLC?

On Tue, Aug 8, 2017 at 2:26 PM, spencer shepler <<>> wrote:

Thanks for the suggestion, Dave.  However, we will let the timer run on the current last call (ends on Friday).

Once that is complete, we will start another last call on the version of the I-D that is available then.

Note that this is always the case - if there has been enough change during a last call to warrant another round, then we do another last call.  Not a big deal.


On Tue, Aug 8, 2017 at 3:16 AM, David Noveck <<>> wrote:
I can't see reviewing this by 8/11.  I think we will need to reset the WGLC clock.

I thibk it should be extended  to 8/21 to give us two weeks to review the new draft.  Other opinions?

In any case, Spencer S should announce a new date, so everybody is in sync.

On Mon, Aug 7, 2017 at 8:09 PM, Thomas Haynes <<>> wrote:
This is a result of the earlier reviews in the WGLC and a desire for an update by said reviewers.

> On Aug 7, 2017, at 4:00 PM,<> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network File System Version 4 WG of the IETF.
>        Title           : Parallel NFS (pNFS) Flexible File Layout
>        Authors         : Benny Halevy
>                          Thomas Haynes
>       Filename        : draft-ietf-nfsv4-flex-files-13.txt
>       Pages           : 40
>       Date            : 2017-08-07
> Abstract:
>   The Parallel Network File System (pNFS) allows a separation between
>   the metadata (onto a metadata server) and data (onto a storage
>   device) for a file.  The flexible file layout type is defined in this
>   document as an extension to pNFS which allows the use of storage
>   devices in a fashion such that they require only a quite limited
>   degree of interaction with the metadata server, using already
>   existing protocols.  Client side mirroring is also added to provide
>   replication of files.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at<>.
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> nfsv4 mailing list

nfsv4 mailing list<>

nfsv4 mailing list<>