IETF Logo Mail Archive

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

John C Klensin <john-ietf@jck.com> Sat, 27 February 2016 20:40 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC6F1AD2F6; Sat, 27 Feb 2016 12:40:01 -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 qkxwCqHOBo_L; Sat, 27 Feb 2016 12:39:59 -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 CC3EB1AD151; Sat, 27 Feb 2016 12:39:59 -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 1aZlec-000NTy-V0; Sat, 27 Feb 2016 15:39:54 -0500
Date: Sat, 27 Feb 2016 15:39:49 -0500
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <A49865510140628ADEB3DCB6@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVDvN8fF4ZAH3-2MA4h3FTbUd37NQsy484eoCXy5MBhoGA@mail.gmail.com>
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>
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/architecture-discuss/jSTWoeWlmxRDkcTIf8B3PP63Vac>
X-Mailman-Approved-At: Mon, 29 Feb 2016 09:27:33 -0800
Cc: IAB <iab@iab.org>, Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>, architecture-discuss@ietf.org
Subject: Re: [arch-d] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2016 20:40:01 -0000


--On Saturday, February 27, 2016 12:35 -0800 Barry Leiba
<barryleiba@computer.org> wrote:

>> NEW:
>>    If ISOC further modifies [ISOC-By-Laws] concerning the
>>    number of IETF appointments to the ISOC Board or the
>>    timing thereof, the IAB may make corresponding
>>    modifications to the frequency and the timing of the
>>    processes embodied in this document, pending any
>>    modification to this document. Such changes will be
>>    announced via an IAB statement.
> 
> I think a change such as that would be good.

I agree but, if the intent is that the IAB modifications and
statement are a stopgap, to avoid discontinuities, etc., but
that the IAB is still expected to move expeditiously to get the
BCP updated, that could be said a lot more clearly.

   john

v2.23.0 | Report a Bug | By Email