Re: [nfsv4] rfc5666bis and rpcrdma-bidirection progress update
Spencer Shepler <sshepler@microsoft.com> Mon, 28 November 2016 22:33 UTC
Return-Path: <sshepler@microsoft.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF1D312A04E for <nfsv4@ietfa.amsl.com>; Mon, 28 Nov 2016 14:33:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level:
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 sxc76z-gBbf6 for <nfsv4@ietfa.amsl.com>; Mon, 28 Nov 2016 14:33:57 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0095.outbound.protection.outlook.com [104.47.36.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 927EB12A04F for <nfsv4@ietf.org>; Mon, 28 Nov 2016 14:33:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=iUyFM0mnXP4X4ALPmbzPKgZB7LEvqaPh6RgSIP/9C/M=; b=k57HEoA/BfSG0fIbew0TR9gH6VNWH8HJBSoGjbWGWHCTsWiFUdDlsVMkv3+L0z9M7n0eEuU14nH8f0XojDKbm1kgY80IuPMzpNt9C/DNJfkG4H9VAG5xnqf23DXeXnMc1APcwzfXWrZ3zdFkiB5wHcj4HQHRUelSnsT+xHAnQZY=
Received: from MWHPR03MB2893.namprd03.prod.outlook.com (10.175.136.10) by MWHPR03MB2893.namprd03.prod.outlook.com (10.175.136.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.747.13; Mon, 28 Nov 2016 22:33:51 +0000
Received: from MWHPR03MB2893.namprd03.prod.outlook.com ([10.175.136.10]) by MWHPR03MB2893.namprd03.prod.outlook.com ([10.175.136.10]) with mapi id 15.01.0747.015; Mon, 28 Nov 2016 22:33:51 +0000
From: Spencer Shepler <sshepler@microsoft.com>
To: Chuck Lever <chuck.lever@oracle.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Thread-Topic: [nfsv4] rfc5666bis and rpcrdma-bidirection progress update
Thread-Index: AQHSLtFppAwC81h0l0KannmYTOjwDqC5VR3QgAAPlwCAKqprAIAAA5CAgAjZ+oCAAeRw4IAADC8AgAAKCTCAABc5AIAAMf4g
Date: Mon, 28 Nov 2016 22:33:51 +0000
Message-ID: <MWHPR03MB28932EE72AB17813102AC8A3C78A0@MWHPR03MB2893.namprd03.prod.outlook.com>
References: <6ED97840-F1BF-4BBC-9C01-7F0A8943CB78@oracle.com> <MWHPR03MB289336B4D7E04D053D27D225C7A80@MWHPR03MB2893.namprd03.prod.outlook.com> <4958FA14-2C47-4AEA-A72F-1C83F92DB4BE@oracle.com> <a3368e2b-ae35-ddef-80b3-d33646e46d88@gmail.com> <F924E4D7-3E26-4BFA-A82E-3713CDBC560A@oracle.com> <CADaq8jduTgJCsdhVmDV0wiiuhf0fkJXYYbsJ0znibipqFuQOZw@mail.gmail.com> <MWHPR03MB28934787F990928A41E84830C78A0@MWHPR03MB2893.namprd03.prod.outlook.com> <CADaq8jdpMCuq5k+k_Gjj4rC6iOgCt5xjwjorcPakRgsbqOWfMg@mail.gmail.com> <MWHPR03MB2893DA050246297A8E362D92C78A0@MWHPR03MB2893.namprd03.prod.outlook.com> <5C52351B-09D7-4273-85E7-445B642FDDCC@oracle.com>
In-Reply-To: <5C52351B-09D7-4273-85E7-445B642FDDCC@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sshepler@microsoft.com;
x-originating-ip: [2001:4898:80e8:c::2c8]
x-ms-office365-filtering-correlation-id: 85de97b4-e6db-41a0-0d43-08d417dea0f9
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:MWHPR03MB2893;
x-microsoft-exchange-diagnostics: 1; MWHPR03MB2893; 7:hNZI5fEnPeswvCMO7/RiuEAcpsZP6w1xNT+ZmjY+Bh5vaePLjwe5W519M85bWXvUONQVLdNWWpbYGu5mt2F8QsQLR8D8/nU2rBghfXRRCm/jHWIUIj930w9mlpQVsNhbaTtsIWdvq+DJhHraIxtpCxUWUkOr82jVbcwKkKc2+6ExvI+wms0ZFHI9SzeP69HmCcrwMTLy/I2tmbJFttnua3qeChtJ2gEbSZSkGktmbDycujDprLFkXf4/no7nLj1JhamZaIsNImPKUUEpKqcazVvf+69UzjaX+OQc7VOrj+0HsP/jSBKEO6M6BSxGgpDS1Du6FGtEmf4aJZNvB4+hA+BUASK05XJjQZJCAxm8NIpngoMUXVQ+9vF70Z0hCDN3Z2zi9nXVTmbgAZG3lBPoPl2XgtN0uqnG00TwTH4rduQkbojEgX80OF9NDmukjuTm+DMwe2jV5lJRQtp4kFC/TcQ91SpP2X2c0DYz9h0od74=
x-microsoft-antispam-prvs: <MWHPR03MB28935E133DEE5A64F0BF0717C78A0@MWHPR03MB2893.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6060326)(6040361)(6045199)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026)(61426038)(61427038)(6046074)(6061324)(6041248)(20161123562025)(20161123564025)(20161123555025)(20161123560025)(6047074)(6042181)(6072148); SRVR:MWHPR03MB2893; BCL:0; PCL:0; RULEID:; SRVR:MWHPR03MB2893;
x-forefront-prvs: 01401330D1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(199003)(189002)(99286002)(106356001)(105586002)(101416001)(106116001)(54356999)(76176999)(2950100002)(33656002)(107886002)(97736004)(189998001)(50986999)(102836003)(74316002)(2501003)(10290500002)(5005710100001)(6116002)(5001770100001)(8990500004)(5660300001)(15650500001)(2906002)(10090500001)(3280700002)(7736002)(3660700001)(305945005)(7846002)(7696004)(122556002)(229853002)(93886004)(68736007)(92566002)(8936002)(77096006)(8676002)(81166006)(2900100001)(81156014)(38730400001)(6506003)(76576001)(9686002)(86612001)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR03MB2893; H:MWHPR03MB2893.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Nov 2016 22:33:51.3274 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR03MB2893
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/UQvbbMEqI5kd1TxZfH3PTA6DTps>
Subject: Re: [nfsv4] rfc5666bis and rpcrdma-bidirection progress update
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 28 Nov 2016 22:33:59 -0000
Chuck, You comment: "It would help to get regular status updates on the document pipeline, whether there are any hold-ups, and what the non-executive members of the WG can do about them. IESG review processes are managed off the WG mailing list, thus many of us are not privy to progress on individual I-Ds, nor do we have a sense of what tasks there are remaining to do. The chairs are usually copied on all of this. Perhaps they could monitor and periodically reflect a summary to the WG.[Spencer] " Sure, I can work to push out a summary for those time where documents are hung up on procedural or review comments, etc. For those that are interested to follow along, all document status for the WG can be found here: https://datatracker.ietf.org/group/nfsv4/documents/ Current state of the document, next steps, and what they mean are available via these pages. For an individual document that has been or is going through IESG the specific comments and feedback are captured. For example, the iSCSI layout document comments are listed here: https://datatracker.ietf.org/doc/draft-ietf-nfsv4-scsi-layout/ballot/ Spencer
- [nfsv4] rfc5666bis and rpcrdma-bidirection progre… Chuck Lever
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Spencer Shepler
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Chuck Lever
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… William Allen Simpson
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Chuck Lever
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… David Noveck
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Spencer Shepler
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… David Noveck
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Spencer Shepler
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… David Noveck
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Chuck Lever
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Spencer Shepler
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… William Allen Simpson
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… David Noveck
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Chuck Lever
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Benjamin Kaduk
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… David Noveck
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… William Allen Simpson
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… David Noveck
- Re: [nfsv4] rfc5666bis and rpcrdma-bidirection pr… Benjamin Kaduk