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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 28 February 2016 18:48 UTC

Return-Path: <brian.e.carpenter@gmail.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 888161A8AC2; Sun, 28 Feb 2016 10:48:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=unavailable
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 ZgASggZzjRxm; Sun, 28 Feb 2016 10:48:46 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB7FB1A8AB7; Sun, 28 Feb 2016 10:48:46 -0800 (PST)
Received: by mail-pa0-x22a.google.com with SMTP id fl4so78962709pad.0; Sun, 28 Feb 2016 10:48:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=qxB3b8Lm12ZpwRc1AGD8qmwD/2EFP9TzB1XDPikEluE=; b=iZ45L7tWvoBZBJ8sk1GfiU0gh/y31tpLszdZV6FzgMRrUR2b1m/tAnoppKe2EP0+pi n3BVah54ePjdYDKBkici251+4/etRWIDz68Px5l8EUAW7FLfKgrdHPplAMmwokeM9K2d TcgSeHJlM8FmK8B4VGXIPIkOEAyLg+dwWfUBDBGUbhVYlD2R8mZAMpSHCN/LzSQSqhBd wAPwNi6b7GVmqnHLXJKHT+ehND+rqBg2pvTTEH4icI1LnLL1Xm3/cWSHe5VVHmVrWdmb NjogS1VYHw73OEd9YhSa+iUyyGXmr+OWZNPdPCPyQeeLcMBZ9Ds5XizpXO8rocU3+xS9 5U/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=qxB3b8Lm12ZpwRc1AGD8qmwD/2EFP9TzB1XDPikEluE=; b=gphQxvNlie3psMT2mO7i3Ib1EXeptrXO0Ifq7bFjFGB16YMQxMUO3D5EyrAqn144Oj kp7fcgTb2v5531jxOaWPfcxzc6nhVQr0/DWX1r+jRxPem6jxAYdzGla1JdseTlbjScQ5 QVWrIAlmBG5s7hpbABytHIqel/gOc62I62mlb9X+eRPVTx9qSs7iLC2Ip59HCtmQvtZA kFTiBl9AoE00fMxUqidNy75nDDNFnvM9vvWtYwf9oGzfdJs+3Ew6N7jIHyW2ZSheBVjk ZmVobY+OoavaAjCeRhgioQ/4kGdDLHH0Em/dk4O1kmplxjfC6+dVJgew8/WZmtLZ0Nr2 uQKw==
X-Gm-Message-State: AD7BkJLx3BvAjf0ilRGvZ77FiqjMPDabA7CCzHA7gzOm3SyBUWSvTnR0YuljYOKf2tS9HQ==
X-Received: by 10.67.23.161 with SMTP id ib1mr16438346pad.156.1456685326264; Sun, 28 Feb 2016 10:48:46 -0800 (PST)
Received: from [192.168.178.22] ([118.148.66.206]) by smtp.gmail.com with ESMTPSA id ko9sm32708019pab.37.2016.02.28.10.48.41 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Feb 2016 10:48:44 -0800 (PST)
Subject: Re: [arch-d] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
To: Bob Hinden <bob.hinden@gmail.com>, John C Klensin <john-ietf@jck.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> <A49865510140628ADEB3DCB6@JcK-HP8200.jck.com> <B5ECD878-81C0-42DE-9170-CAE0529402B6@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56D34119.2030806@gmail.com>
Date: Mon, 29 Feb 2016 07:48:57 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <B5ECD878-81C0-42DE-9170-CAE0529402B6@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mYh6g0OM-v5tlhTNNCV3_dHPZho>
Cc: architecture-discuss@ietf.org, Barry Leiba <barryleiba@computer.org>, IETF <ietf@ietf.org>, IAB <iab@iab.org>, "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>
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 18:48:48 -0000

Well, OK.

NEW 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. Such changes will
  be announced via an IAB statement. The IAB must then
  propose a corresponding update to this document within
  one year.

Regards
   Brian

On 29/02/2016 05:11, Bob Hinden wrote:
> 
>> On Feb 27, 2016, at 12:39 PM, John C Klensin <john-ietf@jck.com> wrote:
>>
>>
>>
>> --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.
> 
> I agree.  The IAB shouldn’t delay it’s board appointment until this document is updated, but it should do an update in a reasonable amount of time.
> 
> Thanks,
> Bob
> 
>