IETF Logo Mail Archive

RE: A question regarding IETF appointments

"Yaakov Stein" <yaakov_s@rad.com> Wed, 21 September 2005 13:03 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EI4G0-0007HN-8C; Wed, 21 Sep 2005 09:03:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EI4Fx-0007H9-RD; Wed, 21 Sep 2005 09:03:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17442; Wed, 21 Sep 2005 09:03:23 -0400 (EDT)
Received: from radmail2.rad.co.il ([80.74.100.136] helo=antivir1.rad.co.il) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EI4Lw-0000vG-84; Wed, 21 Sep 2005 09:09:39 -0400
Received: from antivir1.rad.co.il (localhost [127.0.0.1]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j8LD0NYL005101; Wed, 21 Sep 2005 16:00:23 +0300 (IDT)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j8LD0NLx005093; Wed, 21 Sep 2005 16:00:23 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Sep 2005 16:04:50 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A5205555030@exrad2.ad.rad.co.il>
Thread-Topic: A question regarding IETF appointments
Thread-Index: AcW+Hbyw5/PfP54aQWWsioxcMt8YzAAlikfA
From: Yaakov Stein <yaakov_s@rad.com>
To: ietf@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: quoted-printable
Cc: IAB <iab@ietf.org>
Subject: RE: A question regarding IETF appointments
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

 
> In addition, BCP 10 (RFC 3777) in no way limits the 
> NomCom from selecting sitting ISOC Board members to be on the 
> IAB or IESG.

I think it would be best to avoid having ADs on the BoT,
as they are overworked already, and (should be) focused on producing
the protocols we need now.

However, there is substantial overlap between the functions
of IAB and BoT members. Both need to be concerned with maintenance
and growth of the Internet, evolution of its basic architecture,
and cooperation with other SDOs. Having IAB members on the ISOC
BoT furthermore ensures someone is looking after the IETF's interests
(e.g. standardization and openess of protocols).

So I recommend restricting IESG members but encouraging
the appointment of IAB members.

Y(J)S

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email