Re: [nfsv4] IETF 98 - NFSv4 WG meeting (soliciting agenda items)
Benjamin Kaduk <kaduk@mit.edu> Sat, 08 April 2017 18:17 UTC
Return-Path: <kaduk@mit.edu>
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 E342E129455 for <nfsv4@ietfa.amsl.com>; Sat, 8 Apr 2017 11:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level:
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 hgdMY7HedE3d for <nfsv4@ietfa.amsl.com>; Sat, 8 Apr 2017 11:17:42 -0700 (PDT)
Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (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 97771126DEE for <nfsv4@ietf.org>; Sat, 8 Apr 2017 11:17:42 -0700 (PDT)
X-AuditID: 1209190d-dd3ff70000005ac2-f9-58e9294325f2
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 31.3D.23234.34929E85; Sat, 8 Apr 2017 14:17:40 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id v38IHcXg021293; Sat, 8 Apr 2017 14:17:38 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v38IHYta030303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 8 Apr 2017 14:17:36 -0400
Date: Sat, 08 Apr 2017 13:17:34 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: David Noveck <davenoveck@gmail.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Christoph Hellwig <hch@lst.de>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Message-ID: <20170408181733.GM30306@kduck.kaduk.org>
References: <CAFt6Ba=BaG3+MyGGF-=JOaGOzwKTMaudL2Wxzh1d-2bQPBjZZA@mail.gmail.com> <CADaq8jdqqUtUmkJUtTaobfczmdyovH4oViB2Aj67cTVmTz3cew@mail.gmail.com> <20170201150547.GA7561@lst.de> <CADaq8jfZRKLTmuzwq3VyUfCBQk1-fJPNDwHChf3-uqrRqSaGcQ@mail.gmail.com> <MWHPR03MB28936969C47DE5706C68572FC74D0@MWHPR03MB2893.namprd03.prod.outlook.com> <CADaq8jdk7QJoRieHYi2k755qJU5KE-smMVVSWMM09=mYjo_Rmw@mail.gmail.com> <20170301224100.GA21288@lst.de> <CAFt6Bakn7a3vwhr59W-BGUh1FPOko1kWpU7d85Yxygd4rzpN6A@mail.gmail.com> <CAFt6Ba=6JyZHGvUWQTOYtzUnYk8fUQr7R2aQOezuM+j81ejRGw@mail.gmail.com> <CADaq8jfcbtNe2aXqsbKLShSE85vj=7qrCFi5jOS+3+xLaJriig@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CADaq8jfcbtNe2aXqsbKLShSE85vj=7qrCFi5jOS+3+xLaJriig@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNIsWRmVeSWpSXmKPExsUixG6nruui+TLC4MEuDouzU7+xW6xcfZTJ Yvb7R6wWy6bsYXZg8dg56y67x5IlP5k8dt9sYAtgjuKySUnNySxLLdK3S+DKeLG1m6ngF0/F j4lrWRoY53B1MXJySAiYSHzeMoexi5GLQ0igjUni5oLJrBDOBkaJjc+OQWWuMElM/LSfpYuR g4NFQEXiWnskSDcbkNnQfZkZxBYRUJf48aCJDaSeWaCdUeLwtsvsIAlhAU+JdXensYLYvEDr 5lzdywQxdAKrxPJXLewQCUGJkzOfsIDYzAJaEjf+vWQCWcYsIC2x/B8HSJhTIFDi+/JWRhBb VEBZomHGA+YJjAKzkHTPQtI9C6F7ASPzKkbZlNwq3dzEzJzi1GTd4uTEvLzUIl0jvdzMEr3U lNJNjKAw5pTk3cH4767XIUYBDkYlHt4K9ZcRQqyJZcWVuYcYJTmYlER5WWtfRAjxJeWnVGYk FmfEF5XmpBYfYpTgYFYS4Y1lBirnTUmsrEotyodJSXOwKInzims0RggJpCeWpGanphakFsFk ZTg4lCR4f4DsESxKTU+tSMvMKUFIM3FwggznARreClLDW1yQmFucmQ6RP8WoKCXOGwWSEABJ ZJTmwfWC0oxE9v6aV4ziQK8I89poAFXxAFMUXPcroMFMQIN9bj0FGVySiJCSamA8+N9BrF01 Pv7QxscqGWGMj/5Y/6gudL/htKfm0ttFpTsKp5Y1pxrvmXKi54Kv5YZPu3YbxD1re3fk1vSd ngtSu7Z5CN7/0y8olB+zlM1i383Aq+E3Jy2R29R8w7ex+uy8FfFbi44s0Hrbk/WOnUFr7TWG y1FWasnNqf7K/cuqvl9afOfWZkNtJZbijERDLeai4kQAt7jYIA4DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/NehUSe7kB0FC2sKdBZZ54dhse-Y>
Subject: Re: [nfsv4] IETF 98 - NFSv4 WG meeting (soliciting agenda items)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 08 Apr 2017 18:17:44 -0000
On Fri, Apr 07, 2017 at 02:21:33PM -0400, David Noveck wrote: > > The RFC Editor has responded and the I-D will be moving to AUTH48 within > the next week. > > It is now five weeks later and we've heard nothing to suggest AUTH48 is > any closer. I'm > > assuming that Spencer S. meant to put quote marks around the RFC Editor's > prediction. > > Is here any way to get a reliable ETA on this, or at least some sort of No. > explanation for this > extraordinary delay? After all, RFC 5661, which was over 600 pages long, Maybe, eventually. > got through this > process in one month. The RFC Editor function has a fixed set of staff (on the order of 5, if I understand correctly), and each proto-RFC gets assigned to one of them for the initial/"mundane" editing. If there's a large collection of documents that hits the RFC Editor all at once, some of them will get delays, even beyond the expected service level specified in the contract for the RFC Editor function, though the last I heard, the RFC Editor team was doing better at this after a rough couple of years. The actual named RFC Editor (Heather Flanagan) does still make a final check over all RFCs, as I understand it, so there is still a potential single point of failure. It's generally not easy to get great visibility into the holdups of a specific document. The triannual RFC Editor's report presented (or emailed) at each IETF meeting generally includes statistics on number of things published and conformance to the SLA, though I either don't remember the numbers from the most recent one in Chicago or didn't actually read it. -Ben
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… Benjamin Kaduk
- [nfsv4] IETF 98 - NFSv4 WG meeting (soliciting ag… spencer shepler
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… David Noveck
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… Christoph Hellwig
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… David Noveck
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… Spencer Shepler
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… Chuck Lever
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… David Noveck
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… Thomas Haynes
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… David Noveck
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… J. Bruce Fields
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… David Noveck
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… spencer shepler
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… David Noveck
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… Christoph Hellwig
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… David Noveck
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… spencer shepler
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… spencer shepler
- Re: [nfsv4] IETF 98 - NFSv4 WG meeting (solicitin… David Noveck