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

Bob Hinden <bob.hinden@gmail.com> Mon, 29 February 2016 15:47 UTC

Return-Path: <bob.hinden@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 F37E51B3496 for <ietf@ietfa.amsl.com>; Mon, 29 Feb 2016 07:47:03 -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=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 c1upcOOYs6WI for <ietf@ietfa.amsl.com>; Mon, 29 Feb 2016 07:47:02 -0800 (PST)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 C3CCF1B3495 for <ietf@ietf.org>; Mon, 29 Feb 2016 07:47:01 -0800 (PST)
Received: by mail-qg0-x22c.google.com with SMTP id y89so118213985qge.2 for <ietf@ietf.org>; Mon, 29 Feb 2016 07:47:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=gnzW9b/CkwV6LWcah9jJzBaarA/kHyzZMqWYrsDROVY=; b=uPNxfYafQRrz2Jp3HB38Nf2z5WpcyMlVIOkN6C7BZ5uu64P6+A8A7t37IDHq/AJ6ao p/ki/Cl9q/NHqyI5PXM1EFjO696wni2AF92Pi9YgIMEYuTouK1gNK1hjxjzyXBIphqtn CsJIpTl+t8FNRf1K7iyaCLOvHHQSxEk+SGkZfqsasrcdtkYuoTIZgaQkzTZ+OjwA0J7l g1pJWo0D81XT2SUe8s8JCf5rdztHHJzu7CyCMs74tMeo4RaP8ITX06u93c8A+Nm8qQc1 F9aIV+rXJa9HQ8bis/qEQLq2j+nDYyeOKSDEpgXtSFVehkeWX6ImuEFcMnpmI8qQsi+G J3WA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=gnzW9b/CkwV6LWcah9jJzBaarA/kHyzZMqWYrsDROVY=; b=iuYKw87NSzO/NPEnxVF6SYXXs/vCsSoEZi16NA3sGyGxaM6xex8HV+lLjf5ZqxfA0Y DWUFNUIXf/AnpUJ6fWuhX0LkOTqlvgO/EylB+fZHdem04VR6DLajc+nPW13I51dlFKiE n2QNKlX4Tt8BO/HslyAiGf42HmEeFZN0oGaoLGJdks67gVW9WXCOPWGgFKz2iMuRFpGz kQlUYCycsye6BtbUN97glsEZuV83dD/NN6uV4DJyrFNBzojsubiyhZN15JokH92GiCpu Z2lxV7AfvaSNeOB5I3Tnyb3o/UIXPlFGFQ09JP2Gpn1K39f9ce8f4pljv5CAnBa+t/+t GLbA==
X-Gm-Message-State: AD7BkJIUA85JSvZVZdm/KSLElT4XbSFODZWH0PWZrEnM0iYGY92w/FJpk2Kjf29UVcCjdg==
X-Received: by 10.140.28.133 with SMTP id 5mr19825422qgz.79.1456760820908; Mon, 29 Feb 2016 07:47:00 -0800 (PST)
Received: from ?IPv6:2601:647:4d00:abf0:851:f342:330d:f8f9? ([2601:647:4d00:abf0:851:f342:330d:f8f9]) by smtp.gmail.com with ESMTPSA id e127sm11166247qkb.34.2016.02.29.07.46.59 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 29 Feb 2016 07:47:00 -0800 (PST)
Subject: Re: [arch-d] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_484A987E-42BF-4F6E-BB0E-19011B21F46F"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <56D3534D.4040107@comcast.net>
Date: Mon, 29 Feb 2016 07:46:57 -0800
Message-Id: <8B06FABD-402A-4997-8908-7E4D8C9B8BAC@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> <A49865510140628ADEB3DCB6@JcK-HP8200.jck.com> <B5ECD878-81C0-42DE-9170-CAE0529402B6@gmail.com> <56D34119.2030806@gmail.com> <56D3534D.4040107@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9Dba6q7X-YotsGWGw0lWrMOZv7U>
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: <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: Mon, 29 Feb 2016 15:47:04 -0000

Mike,

After reading your email, I think Brian’s proposed text is fine.  I don’t think anything more is needed.

The IAB did the right thing when the ISOC bylaws changed the number of IETF appointed board members, and they are doing the right thing to update RFC3677.

Next.

Bob


> On Feb 28, 2016, at 12:06 PM, Michael StJohns <mstjohns@comcast.net> wrote:
> 
> On 2/28/2016 1:48 PM, Brian E Carpenter wrote:
>> 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
> 
> 
> 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?
> 
> The above is either too much or too little.  So if its too much then:
> 
> Replace 3.4.1 and 3.4.2 with:  "The IAB shall appoint the IETF-sourced members to the ISOC board with the terms and schedule for such members as described by the ISOC charter, and as they are notified by the ISOC board of IETF-sourced vacancies."
> 
> [I see no reason for the BCP to go into the details of which years as a) its not under the IETF's control, and b) it's subject to change if the ISOC board needs to move things around]
> 
> If its too little then:
> 
> replace 3.4.2 with the Brian's text (replacing "proposed" with "completed") and adding:  "If the IAB fails to complete a change to the BCP within 1 year, then their power to appoint the IETF-sourced members of the ISOC board shall lapse  and such power shall devolve upon the most recently seated IETF nominations committee. The confirmation of such appointments shall remain with the IESG.  The power to make such appointments shall revert to the IAB upon publication of the updated BCP."
> 
> [Basically, if the IAB doesn't have time to complete the BCP, then it probably doesn't have time to deal with the ISOC appointments]
> 
> 
> To be clear, I'd go with the "too much" alternative above and just say that the appointments are made on the schedule described by the ISOC.
> 
> On the other hand, noting that the language in the rationale section (1.2) is no longer a completely accurate statement of reality (cf appointment of IAOC members), it may make sense to re-address who should be doing these appointments.  Perhaps the IAOC is a better body?  Or this can be folded into the Nomcom process?   Not making any recommendations here, just noting that if we're updating this document, we should make sure it's all valid as of the date of publication.
> 
> Later, Mike
> 
> 
>> 
>> 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
>>> 
>>> 
>