Re: Revised IAOC Administrative Procedures draft
Steve Crocker <steve@shinkuro.com> Mon, 13 September 2010 17:31 UTC
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 513E53A6A2C for <ietf@core3.amsl.com>; Mon, 13 Sep 2010 10:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.019
X-Spam-Level:
X-Spam-Status: No, score=0.019 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_DSL=1.129]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPu5+Nlm6zTn for <ietf@core3.amsl.com>; Mon, 13 Sep 2010 10:31:57 -0700 (PDT)
Received: from execdsl.com (mail.shinkuro.com [216.194.124.237]) by core3.amsl.com (Postfix) with ESMTP id ACF813A69F7 for <ietf@ietf.org>; Mon, 13 Sep 2010 10:31:52 -0700 (PDT)
Received: from [66.92.164.104] (HELO dynamic120.shinkuro.com) by execdsl.com (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 18908586 for ietf@ietf.org; Mon, 13 Sep 2010 11:31:53 -0600
Message-Id: <00476A60-5455-4089-8BE8-A638C90C873D@shinkuro.com>
From: Steve Crocker <steve@shinkuro.com>
To: IETF discussion list <ietf@ietf.org>
In-Reply-To: <8200C754-B1DD-49A5-BA62-1E7DA3CC2496@americafree.tv>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Revised IAOC Administrative Procedures draft
X-Priority: 3
Date: Mon, 13 Sep 2010 13:32:16 -0400
References: <3D5CA93C-1A93-4AEA-B679-C15E6FCBC26D@gmail.com> <F1BD8DF0-6511-4A59-B3D5-8276FA4A6351@gmail.com> <A852AD08368B4F6B949E88DEEB02EF2C@your029b8cecfe> <4C8E515A.5060608@dcrocker.net> <EE763784C948455D9CCBA01D363F3D73@your029b8cecfe> <8200C754-B1DD-49A5-BA62-1E7DA3CC2496@americafree.tv>
X-Mailer: Apple Mail (2.936)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 13 Sep 2010 17:32:02 -0000
I've generally stayed out of this discussion, but let me offer a word of support to Bob, et al re maintaining some flexibility. There are two very strong protections already in place in this system. First, the operation of the IAOC -- and IASA -- are fully documented and visible. If the IAOC does something inappropriate, it will become visible and everyone will learn from it. Second, bills get paid through ISOC's normal processes. ISOC has a set of controls in place to document expenses and make sure they follow the expected set of rules. In addition to these strong protections, a questionable expenditure, even if it's several thousand dollars, isn't going to go irreparable harm to the IETF or ISOC. Trying to prescribe a strict set of rules in addition to these protections is counterproductive and may remove flexibility that's needed for the benefit of the IETF at some future time. The IETF's success, and, indeed, the success of the whole Internet, has come from maximum flexibility and minimum a priori rules and permissions. We can easily afford to wait for the IAOC to screw up in some egregious fashion before we have to draft and administer rules to prevent subsequent abuses. In the meantime, let the IAOC do its job on behalf of the community. Steve Full disclosure: I was on the committee that formulated the IAOC and I served on the IAOC for a period of time. On Sep 13, 2010, at 1:16 PM, Marshall Eubanks wrote: > > On Sep 13, 2010, at 12:39 PM, Adrian Farrel wrote: > >> Several interesting responses, thanks. >> >> I agree that detailed rules would be onerous and unable to cope >> with the exceptional circumstances that the condition is intended >> to cover. >> >> On the other hand BCP101 does seem to require some rules. >> >> Dave said: >> >>> There are enough hassles for the IAOC tasks; let's wait to impose >>> stricter rules until we see clear evidence they are needed. >> >> OK, I think that provides a way forward. Let's put in place a >> mechanisms that allows the flexibility (i.e., not change to the >> "under exceptional circumstances" and "with agreement of the IAOC >> chair or the IAOC"), but remove the risk of surprise by inserting >> "with prior agreement", > > I am not sure that the prior agreement is a good idea. What may > trigger this is something like > > IAOC member shows up for IAOC event at X, finds that the room > reservation (or breakfast or projector or ...) has been canceled (or > is for the wrong date or ...) and that this problem can be fixed if > they put down a payment immediately. Most of the rest of the IAOC is > in transit, and prior agreement in terms of a vote cannot possibly > be obtained until it may be too late. The missing item in the normal > course of events would be paid for out of the IASA budget. > > If I were to be placed in that situation, I would go ahead, put the > money down, and hope to be reimbursed, prior authorization or no. > > >> and supply a way of determining whether stricter rules are needed >> by requiring "annual reporting of expenses paid". >> > > I have no problem with that. As a suggestion, let's leave the text > alone, and add > > Any reimbursement of expenses to IAOC members for IAOC expenses will > be reported in the minutes and in the annual reports by the IAOC > Chair. > > (Such reports are required, and have been given in plenary.) > > Marshall > > > Marshall > > >> Cheers, >> Adrian >> _______________________________________________ >> Ietf mailing list >> Ietf@ietf.org >> https://www.ietf.org/mailman/listinfo/ietf >> > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf
- Revised IAOC Administrative Procedures draft Bob Hinden
- Re: Revised IAOC Administrative Procedures draft Bob Hinden
- Re: Revised IAOC Administrative Procedures draft Adrian Farrel
- Re: Revised IAOC Administrative Procedures draft Henk Uijterwaal
- Re: Revised IAOC Administrative Procedures draft Brian E Carpenter
- Re: Revised IAOC Administrative Procedures draft Ole Jacobsen
- Re: Revised IAOC Administrative Procedures draft Bob Hinden
- Re: Revised IAOC Administrative Procedures draft Adrian Farrel
- Re: Revised IAOC Administrative Procedures draft Bob Hinden
- Re: Revised IAOC Administrative Procedures draft Marshall Eubanks
- Re: Revised IAOC Administrative Procedures draft Steve Crocker
- Re: Revised IAOC Administrative Procedures draft Dave CROCKER