Re: [Iasa20] AD review of draft-ietf-iasa2-rfc4071bis-04

"Brad Biddle" <brad@biddle.law> Thu, 14 February 2019 17:39 UTC

Return-Path: <brad@biddle.law>
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 1C259128CE4 for <iasa20@ietfa.amsl.com>; Thu, 14 Feb 2019 09:39:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=biddle-law.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 rjrQ0mp85b8j for <iasa20@ietfa.amsl.com>; Thu, 14 Feb 2019 09:39:53 -0800 (PST)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 B6CBE1200ED for <iasa20@ietf.org>; Thu, 14 Feb 2019 09:39:53 -0800 (PST)
Received: by mail-pf1-x42c.google.com with SMTP id z15so3450886pfa.2 for <iasa20@ietf.org>; Thu, 14 Feb 2019 09:39:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=biddle-law.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=h+V82L/QkYoB4HQ+0DaBxzvaPJfWLenxgXwYs1otX/4=; b=IZJd5YYO8PB8NBP9SWRy/sGD4ZtkOmyj6gynx/ET5tJqA5teiIrU9O4JpCFltHpQa/ jZTfXOlNNO2IBUFmq+JpP9hBvWoCRXz2XJSrWVW+TXswkom3xCHsVZzEsCLfm7B0vO7R J2U26Sfm1mEE+Yi7IpvVSBYaXwQB+Kn7rgMuWhob/om86jGrioBajHJ1L7dAlrqnhpIr Zog4ZogorCfhLXTjaIwEV7l6Bl9PHtoUs9LRTN8NI/ZMKuXnQPVSv3F+5gGhoU22sPYN 760Z3Oiv5SYQERoCwf7BomautivQmhM+OMmKxxtBERJ7xOhQSSY6lZ3KcANK2oSff3VE KHig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=h+V82L/QkYoB4HQ+0DaBxzvaPJfWLenxgXwYs1otX/4=; b=ApOvwjnmrmzavF9C7WPeHY1EVs8EiEYFLTN3YPaf1Ybhjsbtx2p2bsjLafdLL66Wa3 JrtTsoIhNgW/toBn/C1xNPQgVnCyGa7soD7xTysv1vgmTBZtoHlHAr9GhkvjvHPtGLaj o2KGMKxw1lxt+aXinksY48aS3biFKmVxuoy00RryUolTcoHippG6v+T4gXWJyGmfo3k6 P0eR6uSmKpAigTSIzO87dWxLp746lpsZbjF8pg3sb1wxJlccr+q6HdC1Addp7NvQfTee /pduCfGeU95Id7Fmw2wjUz2pnhZEc7fajuGO+8HNBhRBVkLWMXHNv6GSCTzNjEJ8w8GG Q3SA==
X-Gm-Message-State: AHQUAuYytWI6wmkrJU6CJHGoQ/7wxHbrRtrQ0COMBkiY49FCR+Tqphqm abH7OvMpcUdfyJjMvWE0pDukxw==
X-Google-Smtp-Source: AHgI3IaUpAU6hcrv7ia1fXsj666HBIG/YbWOHBVNIaN9StBWl3CxAuhgLNjTsYlbDXB1cWNDJzXlMg==
X-Received: by 2002:a63:d157:: with SMTP id c23mr982354pgj.170.1550165993047; Thu, 14 Feb 2019 09:39:53 -0800 (PST)
Received: from [192.168.86.28] (c-76-115-0-16.hsd1.or.comcast.net. [76.115.0.16]) by smtp.gmail.com with ESMTPSA id o2sm3681294pgq.90.2019.02.14.09.39.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Feb 2019 09:39:51 -0800 (PST)
From: Brad Biddle <brad@biddle.law>
To: Alissa Cooper <alissa@cooperw.in>
Cc: IASA 2 WG <iasa20@ietf.org>
Date: Thu, 14 Feb 2019 09:39:50 -0800
X-Mailer: MailMate (1.12.4r5594)
Message-ID: <429BC6CF-B3E9-40B2-9CD3-E09F649B04A2@biddle.law>
In-Reply-To: <91A5EFAD-BD9F-435E-B01A-7091B263374D@cooperw.in>
References: <91A5EFAD-BD9F-435E-B01A-7091B263374D@cooperw.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/uPUbHbBWG_ER9e6xF-2FpnLkDLI>
Subject: Re: [Iasa20] AD review of draft-ietf-iasa2-rfc4071bis-04
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <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 17:39:57 -0000

Some thoughts on the question Alissa posed to me…

On 13 Feb 2019, at 18:23, Alissa Cooper wrote:

> I have reviewed draft-ietf-iasa2-rfc4071bis-04 in preparation for IETF 
> LC. I have some substantive comments and questions as well as some 
> nits that should be resolved before IETF LC.

[ . . .]

> == Section 4.2 ==
>
> I'm wondering about how the first section of this text squares with 
> what is in the LLC Agreement, in a couple of ways:
>
> (1) The LLC Agreement does not state that the board has duties of 
> loyalty, care, and good faith. I don't know if these are implied, but 
> I think we should hesitate to try to establish these kinds of duties 
> in the RFC if they aren't established in the legal agreements. Would 
> be interested in Brad's opinion on this.

I agree with the general principle that this document should not assert 
that any legal duties or obligations exist that aren’t clearly 
established in the legal agreements. In this particular case however, 
I’m OK with making the statement we have here even though those exact 
words don’t appear in the LLC Agreement. Those duties are imposed by 
Delaware law. I don’t think there is harm — and there may be some 
benefit of clearer expectations and understandings — in explicitly 
stating those duties in this document.

(Possibly of interest: while those duties have long been established as 
applying to directors of traditional corporations, there was a degree of 
uncertainty about if and how they applied to managers of LLCs up until 
2013. Delaware then amended their applicable statutes to clarify that 
these duties do apply to LLC managers, as a default rule. See 
<https://www.dlapiper.com/en/us/insights/publications/2013/08/delaware-amends-its-llc-act--managers-and-contro__/> 
for a short summary.)


> (2) The first bulleted list of responsibilities is overlapping but not 
> the same as the board responsibilities described in 5(d) of the LLC 
> Agreement. That list is:
>
> "The Board will set broad strategic direction for the Company, and 
> will be responsible for adopting an annual budget, hiring or 
> terminating an Executive Director (or amending the terms of their 
> engagement), adopting any employee benefit plans, consulting the 
> relevant IETF communities on matters related to the Company as 
> appropriate, approving any changes to the LLC governance structure, 
> incurring any debt, and approving entering into agreements that that 
> meet a significant materiality threshold to be determined by the 
> Board."
>
> I can understand that there may be additional responsibilities that 
> the community expects of the board that aren't listed in the LLC 
> Agreement (i.e., recruiting new directors). But for the ones that are 
> listed in the LLC Agreement, I think it would be clearer to use the 
> exact same phrasing in both places rather than talking about the same 
> ideas using different words. There is additional wording about 
> transparency in Exhibit A, Section 13.
>
> Similarly, the second bulleted list of responsibilities is a subset of 
> the obligations in Section 11(a) of the LLC Agreement, using slightly 
> different words. I don't understand the motivation for including this 
> list this way. It seems like a reference to 11(a) would be more 
> appropriate.

I agree that tracking to the language in the LLC Agreement, when 
relevant language exists, is the right practice to avoid creating 
ambiguities. While likely not a huge risk — odds of problems arising 
at all are likely low, and the LLC Agreement terms should always be 
definitive when applicable — it’s conceivable that these kinds of 
potential ambiguities could create unnecessary disputes about the scope 
of legal obligations.

Thanks,
Brad
(IETF legal counsel)


Brad Biddle | brad@biddle.law | +1.503.502.1259 (mobile) | 
http://biddle.law