Re: [nfsv4] rfc5666bis and rpcrdma-bidirection progress update
Chuck Lever <chuck.lever@oracle.com> Tue, 25 October 2016 16:59 UTC
Return-Path: <chuck.lever@oracle.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 31E98129695 for <nfsv4@ietfa.amsl.com>; Tue, 25 Oct 2016 09:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.132
X-Spam-Level:
X-Spam-Status: No, score=-4.132 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.431, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 RFMDVz2DHz4P for <nfsv4@ietfa.amsl.com>; Tue, 25 Oct 2016 09:59:43 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95C66129484 for <nfsv4@ietf.org>; Tue, 25 Oct 2016 09:59:43 -0700 (PDT)
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u9PGxgMx003129 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 25 Oct 2016 16:59:43 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id u9PGxgLP008027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 25 Oct 2016 16:59:42 GMT
Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u9PGxeXh009572; Tue, 25 Oct 2016 16:59:41 GMT
Received: from anon-dhcp-171.1015granger.net (/68.46.169.226) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 25 Oct 2016 09:59:40 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <MWHPR03MB289336B4D7E04D053D27D225C7A80@MWHPR03MB2893.namprd03.prod.outlook.com>
Date: Tue, 25 Oct 2016 12:59:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4958FA14-2C47-4AEA-A72F-1C83F92DB4BE@oracle.com>
References: <6ED97840-F1BF-4BBC-9C01-7F0A8943CB78@oracle.com> <MWHPR03MB289336B4D7E04D053D27D225C7A80@MWHPR03MB2893.namprd03.prod.outlook.com>
To: Spencer Shepler <sshepler@microsoft.com>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Hf_mMjE1jPosNwhtciBZmaftNMc>
Cc: NFSv4 <nfsv4@ietf.org>
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: Tue, 25 Oct 2016 16:59:45 -0000
Thanks for the update! Good to see a constructive outcome for RPCGSSv3. Authors should plan accordingly: A reminder that the I-D submission tool will close on Oct 31, 2016 before IETF 97 next week. This might make it challenging to immediately address requested changes to I-Ds in WGLC until the tool opens again. > On Oct 25, 2016, at 12:48 PM, Spencer Shepler <sshepler@microsoft.com> wrote: > > > Chuck, > > The GSSv3 has been going through changes because of the addition of a new IANA registry. See the email below that Spencer Dawkins sent last Friday to the IETF for feedback on the changes made to the GSSv3 I-D. > > For the I-Ds that are "waiting for write-up", those are on my to-do list and will be out in the next week. > > For the I-Ds that are awaiting working-group last call - will start those to run concurrently in the next day or two: > > draft-ietf-nfsv4-umask-02 Allowing inheritable NFSv4 ACLs to override the umask > draft-ietf-nfsv4-versioning-07 Rules for NFSv4 Extensions and Minor Versions. > draft-ietf-nfsv4-xattrs-03 File System Extended Attributes in NFSv4 > > -----Original Message----- > From: Chuck Lever [mailto:chuck.lever@oracle.com] > Sent: Tuesday, October 25, 2016 8:07 AM > To: Spencer Shepler <sshepler@microsoft.com> > Cc: NFSv4 <nfsv4@ietf.org> > Subject: rfc5666bis and rpcrdma-bidirection progress update > > Hi Spencer- > > Trying to ascertain the status of rfc5666bis and friends. They've been in "Waiting for Write-up" for some time now, according to the datatracker. > > The NFSv4.2 documents, RPCGSSv3, and the multi-domain doc are all on the edge of publication, but they've been waiting there for over half a year. GSSv3 in particular has been in AUTH48 for quite some time. I assume my docs are waiting behind those. > > Please let me know if there's anything I can do to help move this process forward. Thanks! > > > -- > Chuck Lever > > [Spencer] ------- > [Spencer] > From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> > Date: Fri, Oct 21, 2016 at 12:54 PM > Subject: Checking for objections - adding an IANA registry to draft-ietf-nfsv4-rpcsec-gssv3 > To: "ietf@ietf.org" <ietf@ietf.org> > Cc: "iesg@ietf.org" <iesg@ietf.org>, nfsv4-chairs@ietf.org > > To the IETF community, > > draft-ietf-nfsv4-rpcsec-gssv3 is in the RFC Editor queue, in AUTH48. > > During AUTH48 discussions between the authors, they convinced each other, the document shepherd, and me, that this document needed a new registry for "RPCSEC_GSS Structured Privilege Names" that were being defined in the document, and they added one, as Section 5.2. > > Here's the diff that shows you the new Section 5.2: > > https://www.rfc-editor.org/authors/rfc7861-lastdiff.html > > The working group has seen the change, and the working group chairs believe the working group has consensus to make the change. > > IANA has reviewed the proposed registry instructions and provided comments, and now has no more questions. > > I believe this is the Right Thing To Do. > > This is a post-IESG evaluation technical change to draft-ietf-nfsv4-rpcsec-gssv3, so I've discussed this with the rest of the IESG, and they agreed that that IETF community should see this change before publication as an RFC. > > I plan to approve this document with the RFC Editor on October 28, one week from today, unless I hear objections from the community. > > Feedback can be sent to iesg@ietf.org, or directly to me. > > Spencer > -- Chuck Lever
- [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