Re: [arch-d] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)

John C Klensin <john-ietf@jck.com> Sun, 28 February 2016 20:19 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC311ACD02 for <ietf@ietfa.amsl.com>; Sun, 28 Feb 2016 12:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006] autolearn=ham
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 6XmFHsZRQWGc for <ietf@ietfa.amsl.com>; Sun, 28 Feb 2016 12:19:25 -0800 (PST)
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 CD2E71ACCFA for <ietf@ietf.org>; Sun, 28 Feb 2016 12:19:25 -0800 (PST)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aa7oK-00002d-6D; Sun, 28 Feb 2016 15:19:24 -0500
Date: Sun, 28 Feb 2016 15:19:19 -0500
From: John C Klensin <john-ietf@jck.com>
To: Michael StJohns <mstjohns@comcast.net>, ietf@ietf.org
Subject: Re: [arch-d] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
Message-ID: <666FB40E5CF981635792FE54@JcK-HP8200.jck.com>
In-Reply-To: <56D3534D.4040107@comcast.net>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <CAC4RtVDpMsFuSMHPvkT2vXngGJkNsWDqL-g1EipcCUNjqa2Ssg@mail.gmail.com> <56CDFF39.7000603@gmail.com> <4572E392-3E57-45C4-9CBF-86B3E2E0982A@cisco.com> <CALaySJJfyikA7o5CEiQvbjNF-d7EzUi-TTsTWnxo2yb_jBibag@mail.gmail.com> <56CE6E2B.6020903@gmail.com> <6CB3AE29-C0DD-45B3-858C-2C3A44106ED5@gmail.com> <56D1FDD2.5030906@gmail.com> <CAC4RtVDvN8fF4ZAH3-2MA4h3FTbUd37NQsy484eoCXy5MBhoGA@mail.gmail.com> <A49865510140628ADEB3DCB6@JcK-HP8200.jck.com> <B5ECD878-81C0-42DE-9170-CAE0529402B6@gmail.com> <56D34119.2030806@gmail.com> <56D3534D.4040107@comcast.net>
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: <http://mailarchive.ietf.org/arch/msg/ietf/q2Y9DMHomdgalDtzsSoAg1pVXbE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 28 Feb 2016 20:19:27 -0000


--On Sunday, February 28, 2016 15:06 -0500 Michael StJohns
<mstjohns@comcast.net> wrote:

> I'm always somewhat pained by toothless requirements.  E.g.
> what's the downside if the IAB fails propose an update, or if
> they drag out the completion of the update for several years
> because other things are more important?

So am I.  However, my pain level about toothless requirements is
exceeded by my pain level about making specific requirements for
the handling of unusual or edge-case situations, requirements
that may not be able to anticipate all possible cases and that
therefore may overreact or under-react.   I'd like to believe
that the community has ways to hold the IAB accountable for
failing, without good reason, to do things the community told
them to do.  I'd also like to believe that the vast majority of
the IAB takes community instructions seriously enough that those
instructions will, if clear, simply be followed in the
overwhelming percentage of circumstances.    If that turns out
to not be the case and accountability mechanisms prove necessary
but ineffective in practice, and the community actually cares,
the community has a much more serious problem than whether ISOC
BoT members are appointed or a specific BCP is updated.

    john