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

"Livingood, Jason" <Jason_Livingood@comcast.com> Sun, 24 February 2019 21:44 UTC

Return-Path: <Jason_Livingood@comcast.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 41E7D126C15 for <iasa20@ietfa.amsl.com>; Sun, 24 Feb 2019 13:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 bt8AI21zO9yD for <iasa20@ietfa.amsl.com>; Sun, 24 Feb 2019 13:44:26 -0800 (PST)
Received: from copdcmhout02.cable.comcast.com (copdcmhout02.cable.comcast.com [96.114.158.212]) (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 8790A12D829 for <iasa20@ietf.org>; Sun, 24 Feb 2019 13:44:26 -0800 (PST)
X-AuditID: 60729ed4-2cdff700000044dc-2e-5c7310383efa
Received: from COPDCEXC40.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by copdcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id 65.15.17628.830137C5; Sun, 24 Feb 2019 14:44:25 -0700 (MST)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC40.cable.comcast.com (147.191.125.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Sun, 24 Feb 2019 16:44:24 -0500
Received: from COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94]) by COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1466.012; Sun, 24 Feb 2019 16:44:23 -0500
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Brad Biddle <brad@biddle.law>, Alissa Cooper <alissa@cooperw.in>
CC: IASA 2 WG <iasa20@ietf.org>
Thread-Topic: [Iasa20] AD review of draft-ietf-iasa2-rfc4071bis-04
Thread-Index: AQHUxAxZp52rFDuQIEOMm5D0cyMTz6Xf5EsAgA+n0oA=
Date: Sun, 24 Feb 2019 21:44:23 +0000
Message-ID: <0371EF9E-4091-4D34-AE92-E5EB71B86F28@cable.comcast.com>
References: <91A5EFAD-BD9F-435E-B01A-7091B263374D@cooperw.in> <429BC6CF-B3E9-40B2-9CD3-E09F649B04A2@biddle.law>
In-Reply-To: <429BC6CF-B3E9-40B2-9CD3-E09F649B04A2@biddle.law>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.15.0.190115
x-originating-ip: [68.87.29.7]
Content-Type: text/plain; charset="utf-8"
Content-ID: <086DD4F7000CE64C8B803AFBF1CA09DC@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHKsWRmVeSWpSXmKPExsWSUDRnsq6lQHGMwfnnUhbTz/xltHh9eCKT xZLpG5kcmD22N+5n9vjy5CWTx5IlP5kCmKMaGG1KMopSE0tcUtNS84pT7bgUMIBNUmpaflGq a2JRTmVQak5qInZlIJUpqTmZZalF+liN0cdqTkIXU8acGVwFW6wqzkyvbWD8YtHFyMkhIWAi 0fH9FCuILSSwi0li3i3BLkYuILuFSWLG6gXMEM5pRomVE08xglSxCZhJ3F14hRnEFhFwkehf upUFxGYWkJc4NukfG4gtLOAo0dPyBKrGSeLWwR6gGg4g20pizyRtkDCLgKrE16Yn7CBhXqAx F3cWQtxQKHFj+X2wTZwCdhLT5jWB2YwCYhLfT61hgtgkLnHryXwmiPsFJJbsOc8MYYtKvHz8 D+wXUQF9idbvP1gh4nISc1/fA7uAWUBTYv0ufYgxVhKP325ig7AVJaZ0P2QHsXkFBCVOznzC AtEqLnH4yA7WCYySs5BsnoUwaRaSSbOQTJqFZNICRtZVjHyWZnqGhiZ6hqYWekaGRpsYwalo 3pUdjJenexxiFOBgVOLh7WQsjhFiTSwrrsw9xCjBwawkwmvzrChGiDclsbIqtSg/vqg0J7X4 EKM0B4uSOC8XR36MkEB6YklqdmpqQWoRTJaJg1OqgTG6LNpULvzl/4htksEJN+RUNk5bXymi 3Pf6iuRvkzrbEzwntlf2T1pw4ZKAQpRXoteJJSx/vhyulnwj02giqZr74EW/3ZXkLPXXfNm7 tPS9euWjmA5tW5Eq3ONmcmva+Yel6Q5lb0NuSn/Mj7r2/9zd8ok21r4PFu34Nu155Lsne3KN 3KyiTimxFGckGmoxFxUnAgAhjSR8QQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/mPhJQymmr-wN4gLNpj4lmRLOEhM>
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: Sun, 24 Feb 2019 21:44:29 -0000

What I have tried to do for this section (board responsibilities) is to better align it with the LLC agreement. I also added an introductory statement to ensure that it is understood that the LLC Agreement is authoritative.

" This section is intended to provide a summary of key IETF LLC Board responsibilities, but 
the precise and legally binding responsibilities are defined in the LLC Agreement {{IETF-LLC-A}}. 
To the extent to which there are unintentional differences or other confusion between this 
document and the LLC Agreement, the LLC Agreement is in all cases authoritative. "

Brad - Please review this new section once the doc is updated and let me know if it is now better aligned with the LLC agreement. I will send you a copy of what I have for the new doc under separate cover.


JL

On 2/14/19, 12:40 PM, "iasa20 on behalf of Brad Biddle" <iasa20-bounces@ietf.org on behalf of brad@biddle.law> wrote:

    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) | 
    https://protect2.fireeye.com/url?k=48744dbd15e34664.48746a09-057a9abb268c2f17&u=http://biddle.law
    
    _______________________________________________
    iasa20 mailing list
    iasa20@ietf.org
    https://www.ietf.org/mailman/listinfo/iasa20