IETF Logo Mail Archive

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

Russ Housley <housley@vigilsec.com> Wed, 20 April 2016 18:18 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39A9E12DF7D; Wed, 20 Apr 2016 11:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 NqQujU6OETuO; Wed, 20 Apr 2016 11:18:53 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 75BDB12E2FC; Wed, 20 Apr 2016 11:18:42 -0700 (PDT)
Received: from localhost (ronin.smetech.net [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 27E2EF2402A; Wed, 20 Apr 2016 14:18:42 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id doprNttL2y6a; Wed, 20 Apr 2016 14:03:14 -0400 (EDT)
Received: from [192.168.2.100] (pool-108-51-128-219.washdc.fios.verizon.net [108.51.128.219]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 72E2D9A4001; Wed, 20 Apr 2016 14:18:41 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu>
Date: Wed, 20 Apr 2016 14:18:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu>
To: Scott Bradner <sob@harvard.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/architecture-discuss/qJwS0rKIiy5JRafoTOsnhx6-YyE>
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Subject: Re: [arch-d] [IAB] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 20 Apr 2016 18:18:55 -0000

Scott:

I cannot see how the change that you are proposing to the ISOC Bylaws has any impact on the content of rfc3677bis.  What am I missing?

If I am not missing anything, then it seems to me that waiting to move forward on this is counter to may of the other comments that we got about acting promptly to keep our document in sync with the current bylaws.

Russ

On Feb 25, 2016, at 7:27 AM, Bradner, Scott <sob@harvard.edu> wrote:

> re section 3.5 mid-term vacancies
> 
> please hold off on this particular section for a bit - I am in the middle of proposing some changes 
> to the ISOC bylaws - mostly to clear up some confusions - and one of these changes concerns IETF vacancy appointments
> 
> the current bylaws do not limit when the IETF can appoint someone to fill a vacancy but do limit when such an
> appointment can take office to the start of the ISOC mid year meeting, when all new trustees take office - which might
> be a bit frustrating to the appointee
> 
> I am proposing a bylaws update that will put the IETF appointment t fill a vacancy to be the same
> as it is for the chapters & org members - with until the next appointment cycle (to do otherwise
> provided unequal treatment for the IETF)
> 
> in any case some change is needed to clarify the existing situation
> 
> Scott
> 
>> On Feb 24, 2016, at 12:59 PM, IAB Executive Administrative Manager <execd@iab.org> wrote:
>> 
>> This is an announcement of an IETF-wide Call for Comment on
>> draft-iab-rfc3677bis-00.
>> 
>> The document is being considered for publication as a Best Current 
>> Practice RFC within the IAB stream, and is available for inspection 
>> here: https://datatracker.ietf.org/doc/draft-iab-rfc3677bis/
>> 
>> The Call for Comment will last until 2016-03-23. Please send comments to
>> architecture-discuss@ietf.org and iab@iab.org.
>> 
>> 
>> Abstract
>> 
>>  This memo, which obsoletes RFC3677, outlines the process by which the
>>  IETF makes a selection of an Internet Society (ISOC) Board of
>>  Trustees appointment.
>> 
>

v2.23.0 | Report a Bug | By Email