Re: Planned changes to registration payments & deadlines
John C Klensin <john-ietf@jck.com> Tue, 24 April 2018 01:03 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA3F712DB71 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 18:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 35fetfj19fPm for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 18:03:25 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4350D126FDC for <ietf@ietf.org>; Mon, 23 Apr 2018 18:03:25 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1fAmMd-000O03-Iv; Mon, 23 Apr 2018 21:03:23 -0400
Date: Mon, 23 Apr 2018 21:03:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <E3942A1DBD7E232532060E6F@PSB>
In-Reply-To: <9954.1524528938@obiwan.sandelman.ca>
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <49c1c20d-000c-9664-d998-cace737704d8@gmail.com> <9954.1524528938@obiwan.sandelman.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hTZCe31R-caSrSpt_qJCXbhzHVg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2018 01:03:27 -0000
--On Monday, April 23, 2018 20:15 -0400 Michael Richardson <mcr+ietf@sandelman.ca> wrote: > I haven't worked in an organization big enough to need travel > approvals in 20 years. If it takes 5 weeks to get approval to > go, it seems that someone should simply say to their manager: > "If you can approve this by Feb 1, it's gonna be $700. > If you can't approve it that fast, then it's gonna be > $175 more. Or, I can register and pay now, and take a $70 > risk that you won't approve me going." Based on dealing with similar issues in a different setting, for working meetings like the IETF (rather than "conferences" or various [other] professional development activities, some companies have fairly firm "don't bother asking for approval for meeting N+1 before you have submitted a travel report and documentation on meeting N". For those organizations (and I have absolutely no idea how many IETF participants have to interact with them), consider that * The cutoff for submitting minutes is typically three weeks from the last day of the relevant meeting * The cutoff for corrections to the minutes, i.e., the date on which minutes can be assumed to be final, is a bit over another three weeks, i.e., six weeks out. If one ends up on a position in which a travel request cannot be submitted after that and one assumes a four month cycle, that implies that the request can't go in until around nine or ten weeks before the next meeting. Is that too close if the "early" cutoff is 7 weeks before? Maybe not... depends on the organization. Or try the other end. For IETF-type meetings, it is not unusual for a travel-approver to want to see at least a preliminary agenda along with the travel request. On our current schedule, the preliminary agenda shows up about four weeks before the meeting and the nominally final one shows up a week later, but before the "early" registration cutoff. If that boundary is moved back, than no one who needs an agenda to make a decision, or to persuade someone else to make a positive decision, then it is all over for "early" and the window before "standard" is not available is rather short. Maybe that is still ok, but I think we should be sure we understand what we are doing and, as Brian suggests, avoid making decisions on the basis of false comparisons to, e.g., annual conference-type events. john
- Planned changes to registration payments & deadli… Andrew Sullivan
- Re: Planned changes to registration payments & de… Stephen Farrell
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Eric Rescorla
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Adam Roach
- RE: Planned changes to registration payments & de… Roni Even (A)
- Re: Planned changes to registration payments & de… Spencer Dawkins at IETF
- Re: Planned changes to registration payments & de… Stewart Bryant
- Re: Planned changes to registration payments & de… Spencer Dawkins at IETF
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Dhruv Dhody
- Re: Planned changes to registration payments & de… Nick Hilliard
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Matthew Pounsett
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Dhruv Dhody
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Jonathan Lennox
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… John Levine
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- RE: Planned changes to registration payments & de… Roni Even (A)
- Re: Planned changes to registration payments & de… Stephen Farrell
- Re: Planned changes to registration payments & de… Stewart Bryant
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Yoav Nir
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Bob Hinden
- Re: Planned changes to registration payments & de… Vinayak Hegde
- Re: Planned changes to registration payments & de… John R Levine
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan