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

Richard Barnes <rlb@ipv.sx> Fri, 15 February 2019 03:11 UTC

Return-Path: <rlb@ipv.sx>
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 2A5D1130E91 for <iasa20@ietfa.amsl.com>; Thu, 14 Feb 2019 19:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
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 a-gac4kUKtgr for <iasa20@ietfa.amsl.com>; Thu, 14 Feb 2019 19:11:09 -0800 (PST)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 2752C130E7D for <iasa20@ietf.org>; Thu, 14 Feb 2019 19:11:09 -0800 (PST)
Received: by mail-ot1-x32e.google.com with SMTP id u16so14256855otk.8 for <iasa20@ietf.org>; Thu, 14 Feb 2019 19:11:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iE/3LcqefihkUDPkMhe7jLpnxYZDE7QdVdLgZWwbQxI=; b=zK3hhs6oaHFt+KZIQtDF7LohV/V3QFWOw9XLvpRH3+cXcvvDL87rI8Dljwayu6Zliy /GjVTTV+y4SuHs1mJhpyYxXD35OgvgEh9gJHPKgVOeAcoR6MjiKGxn7lu4iufCCjOQgk 4mJHngvSec8lwrz28Tk38PPttaaHVEOyYKpZ/iC49FsszkEOmrNYmgI1sQc7XqM7qUb1 gJNy5wn0nWpoXVw941PRpmbv8BWRg0E6U+kSOF6G89MB4pQLRsPwGvTMRUqM6tiFp/Si 4pRv9l3cLcMjAaNs2zkBtDlA09Je7MRRGQF5KMGZIWAWl05JOESn+yqRMxnnvZdOgWW0 sErQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iE/3LcqefihkUDPkMhe7jLpnxYZDE7QdVdLgZWwbQxI=; b=mpqO7BjWmctARpNnIsu8egAoOwhqa/K01gQuKeYSPI8u4zJRpeFiD96beyxt0Zp68T cZbRPSK8T4YNYSRkchh7nxpo5Y2unlWmKscvW9tw56vN47O0VuWVfBrMyBaOvcFPNFVs iguC+jrtyJ2AhiQotEJdEuLX8Wrv3ImtZSQyD2SDjKFWRccBtAkEg3q/6FHV4TmiptBY HFFFDXymcRJsIyQC9oJWLkJC3giveiiyiZwPaNs2CzevgmYu0nBvYZ5MZf1ZHYrxKbyY ATDDQKtCyWULcQYaYFLaNZE+IM4p3AgWxMSk4DnqCQvAFFq7zy0Kpu4jUPxaaMBeRo5k Sx9Q==
X-Gm-Message-State: AHQUAuasUAZlBCMOcYw4Lz3NrZoospP3C+edQ2o/qrOcNOwS1L5tSa8e Q8QdD3PfOID+2LeoBpLD9HCMd+R9alLGefT5cu5hEA==
X-Google-Smtp-Source: AHgI3IbIOyiOnEIGpC83ljEDMxlakKyL54Upud6XAErIgP1VEYhzWptbT12HrKFDSHSDL+oxpk0aZp6Wpai9bd0sCno=
X-Received: by 2002:a9d:6a92:: with SMTP id l18mr4772963otq.81.1550200268016; Thu, 14 Feb 2019 19:11:08 -0800 (PST)
MIME-Version: 1.0
References: <29B3755DB6957C26A8D3DAA6@PSB> <20190214231651.7CA52200E5487E@ary.qy>
In-Reply-To: <20190214231651.7CA52200E5487E@ary.qy>
From: Richard Barnes <rlb@ipv.sx>
Date: Thu, 14 Feb 2019 19:10:51 -0800
Message-ID: <CAL02cgRJTduLrBeGaAqpGRN8DE37hQpDbRRVYVMfg4TWCybQbw@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IASA 2 WG <iasa20@ietf.org>, John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary="0000000000004e61980581e6207a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/jG3-Wuvg7zlAdCPLWEk8n87TaeI>
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: Fri, 15 Feb 2019 03:11:11 -0000

On Thu, Feb 14, 2019 at 18:17 John Levine <johnl@taugh.com> wrote:

> 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.


Also, note that this gives the community strictly more control than they
had before.

Contrary to JCK's assertion, even if the NOMCOM were to appoint "IAOC
members who would agree to overrule or fire the IAD", they would not
actually be able to fire the IAD (since the IAD is an employee of ISOC),
nor "overrule" the IAD in the sense of compelling ISOC to enter into a
contract with DD.  Their recourse in such an extreme case would be either
to (a) replace the IAB-appointed ISOC board members (comprising a minority
of the ISOC board) or failing that (b) sever the relationship with ISOC and
make alternative arrangements to fund the RSE.

As you note, with the new arrangement, the community has the more gentle
option of replacing almost the whole board of the LLC.

--Richard



>
> See section 7 of draft-ietf-iasa2-rfc7437bis
>
> R's,
> John
>
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>