Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01

"John Levine" <johnl@taugh.com> Thu, 14 February 2019 23:16 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6785B12F1A5 for <iasa20@ietfa.amsl.com>; Thu, 14 Feb 2019 15:16:54 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=OY+qzeoj; dkim=pass (1536-bit key) header.d=taugh.com header.b=joFwr/Gu
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 Oyzk9XGQHQAg for <iasa20@ietfa.amsl.com>; Thu, 14 Feb 2019 15:16:53 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 02BE71289FA for <iasa20@ietf.org>; Thu, 14 Feb 2019 15:16:52 -0800 (PST)
Received: (qmail 12681 invoked from network); 14 Feb 2019 23:16:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=3187.5c65f6e3.k1902; bh=cEKImBYsjyF/wgGrBSEyxgEXpOs81VNb+Zk90vtNi18=; b=OY+qzeojp5Sx0VgHNkqoPiU0It5PmY7YZ1rjI4c61UjFRdzJdB4e8ZCyiJkAz8VxKIlUjqBz29w2vqu2Jatbbs6d7Kbal923zYGllJ4g8fYedgaFcoPlkNPY2ikeIX5judjnY+xBEah7dPSzx4pzE7lsByOvyPBXZHnG5Uc3gObww3OgnCmEJ8eHsXxUfLqSlWRYS9iorIe5XTwLtG7GH1IMGVXQKiTgpp43h6kcoyck5k3wZ83MAa2SstUzKWhC
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=3187.5c65f6e3.k1902; bh=cEKImBYsjyF/wgGrBSEyxgEXpOs81VNb+Zk90vtNi18=; b=joFwr/GuwmRPPT2uNrtMCAIgDi3PRk1b1pp45pNyz4Hp+2BQiNPhuop1fK2y5Rl/o5pbVUxkWqqr6WEwm3SC4Eg57Rs5GKD30+GMqMRDBMxHBhbxlIURWoIWzOPuUoXzitJkW0adWtaWRYS6J0Gzn4xQ1qtZVW1F/891i2C9f3qvwLPdqxr/dkjWA5mq1k+mtlCOz+Q6x34fgRuZPYamuniB1smLIhjAWUCG8Kw0VrP3FOJ8rIVzIJVdi5BSqhGs
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 14 Feb 2019 23:16:51 -0000
Received: by ary.qy (Postfix, from userid 501) id 7CA52200E5487E; Thu, 14 Feb 2019 18:16:51 -0500 (EST)
Date: 14 Feb 2019 18:16:51 -0500
Message-Id: <20190214231651.7CA52200E5487E@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: iasa20@ietf.org
Cc: john-ietf@jck.com
In-Reply-To: <29B3755DB6957C26A8D3DAA6@PSB>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/4gl6DLQyGNNkguIl528AfFG5fMU>
Subject: Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2019 23:16:54 -0000

In article <29B3755DB6957C26A8D3DAA6@PSB> you write:
>Under the new model, at least as I understand it, the LLC
>Directors could, in principle, decline to be recalled -- the
>community's only recourse would be to decline to reappoint them
>when their terms ran out.

No, the IETF can recall the IETF appointed directors, which is all but
one of the LLC directors.  The other one is ISOC appointed, subject to
the whims of the ISOC board.

See section 7 of draft-ietf-iasa2-rfc7437bis

R's,
John