Re: Updating BCP 10 -- some minor bits

joel jaeggli <joelja@bogus.com> Sat, 10 January 2015 19:27 UTC

Return-Path: <joelja@bogus.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 02C991A6FCB for <ietf@ietfa.amsl.com>; Sat, 10 Jan 2015 11:27:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 vBzWmX_4LJkB for <ietf@ietfa.amsl.com>; Sat, 10 Jan 2015 11:27:15 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 346AC1A0233 for <ietf@ietf.org>; Sat, 10 Jan 2015 11:27:15 -0800 (PST)
Received: from mbp.local ([172.56.17.5]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id t0AJRC1J086409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 10 Jan 2015 19:27:14 GMT (envelope-from joelja@bogus.com)
Message-ID: <54B17D0B.1080107@bogus.com>
Date: Sat, 10 Jan 2015 11:27:07 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:34.0) Gecko/20100101 Thunderbird/34.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Updating BCP 10 -- some minor bits
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <3764.1420828464@sandelman.ca> <634EBCDC-0C29-4B04-9510-ADE7BE0B3DDB@vigilsec.com>
In-Reply-To: <634EBCDC-0C29-4B04-9510-ADE7BE0B3DDB@vigilsec.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rUlfWeICuIkJ1ETqmfvKJaB5eefn9sd0q"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/r3wa4_dhR6U0qEhPHBV0beP16nY>
Cc: ietf <ietf@ietf.org>
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: <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: Sat, 10 Jan 2015 19:27:17 -0000

On 1/9/15 1:46 PM, Russ Housley wrote:
> Michael:
>
>> 2) several of us suggest that the Chair for year X, be appointed prior to the
>>   the beginning of the Third IETF of year X-1.  This permits the
>>   chair-elect/future-chair, to participate and learn about the process prior
>>   to starting.  While this adds about 4 months to the duration of the chair
>>   duties, it probably reduces their stress sufficiently that they will live
>>   an extra year longer.
> Allison made this suggestion in her report in March 2014.
>
> It is already too late for the NomCom Chair for appointments in 2016 to be trained by watching the appointment process for this year.

this also increases the duration of the commitment as nomcom chair,
which imho is not ideal.
>
> If this idea is agreeable to the community, we have much less than a year to approve an update to BCP 10 to for this to happen for the 2017 leadership appointments.  I heard Allison offer to provide some text.  I think that would be the next step.
>
> Russ
>
>