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

Alissa Cooper <alissa@cooperw.in> Thu, 28 February 2019 13:15 UTC

Return-Path: <alissa@cooperw.in>
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 31073130E27 for <iasa20@ietfa.amsl.com>; Thu, 28 Feb 2019 05:15:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=FYD7yUCG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=aDU+UlBX
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 OFT3NHcSx1Wd for <iasa20@ietfa.amsl.com>; Thu, 28 Feb 2019 05:15:40 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1A39130E7F for <iasa20@ietf.org>; Thu, 28 Feb 2019 05:15:39 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id DE93821F40; Thu, 28 Feb 2019 08:15:38 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Thu, 28 Feb 2019 08:15:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=D DWThQqhAugTbLJfFV+alhHDGk3S/fkXsk+PHWcFMZw=; b=FYD7yUCGTm9e84Jv+ a1EHEqpFpW15v3RGwHgQqYMt9B1Pcdb/2+c3okr9pSiTWa01QTULo7+1cOaLJSMr X1HTdTvs8PCyQihPAdPYLwY7dc6xHnjjOvq1jOg/kPJhQZlT2M8MIhkwq6cB4KU0 ZaVPTgHOJ3u8cEs2EU9FNLaMc6VA3ZVVZP7alTIr7Y8jDIBuryxvzH49BtFtE9Do LmPbu7j+PJ5sMo2EUfuo6zcz9wtpDJ6Hed1PSoINwoCS01VqOzC+OsMtnBQ9ZtAx c7OEaEmM34uZ77Ei7oB7m1HPkqPGTizzPwQ5Prf7vpcLkn+81XQ8IrSLYGJ9luWv Pso4Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=DDWThQqhAugTbLJfFV+alhHDGk3S/fkXsk+PHWcFM Zw=; b=aDU+UlBXtWYdoSDK+36KST0aBVrOgsTqEsAM0jDZlvtnToqsztX2LQm51 q6yXjNOLhdaDZDZhE2J3ncJFt39Y9C4qgOTVhmSEyMTeVkcDWoqW+hwsXLe8ACpS /rmP/uooiyJ2OUeMG1frzilqg838hhnUmvyjZbk5k/uCzvfFU2D6OrGU00qTwyqY 1zyt6fDN2+HJ3kwENzpxlzXBzHGnxX+najgLC70G1xaOLDoqW6VV0Od3OzdsjKFE trQjCvJDn/MUEJh9Y9IO77d4qGKm7/+BnXG5CrOPdbsWoR8798fUYx6j8n5fRBIJ nlhtF9ontjO31XCthyq+NoYRNb6rg==
X-ME-Sender: <xms:-t53XB8A5ausnwDDCtX6dYqo5byoNW-3sEMk7eKt2KTCDi3pqOrq-w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrvdefgdehvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehivghtfhdrohhrghenucfkphepuddtgedrudehfedrvddvgedrudeiieenucfrrghr rghmpehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhush htvghrufhiiigvpedt
X-ME-Proxy: <xmx:-t53XGye4dTHNvBmrV3kSlKS8N-EnTxVL_apdqlSmpRK4zYaWXNOBA> <xmx:-t53XB9RfUIpK6H_1qC9Dkup4tu_Pf2Y2l_ki5xPlfLNFoAH9MMIPA> <xmx:-t53XDKqq-NzaRBsUTW66tLFRInrfE7nRJ8TnNLsiL-p0ExW-2HvzQ> <xmx:-t53XFQ_zrqCmmB8X-bLzFwqDC9E1XoF9sQN8-4wqbFPPPgNnIK7rQ>
Received: from [172.19.249.32] (unknown [104.153.224.166]) by mail.messagingengine.com (Postfix) with ESMTPA id 63D1210312; Thu, 28 Feb 2019 08:15:31 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <BDCD1EBD-3550-4ADF-9417-BFC55661DF6B@gmail.com>
Date: Thu, 28 Feb 2019 14:15:22 +0100
Cc: IASA 2 WG <iasa20@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <98795E4E-D0A1-475B-AEA5-3013C94EE758@cooperw.in>
References: <91A5EFAD-BD9F-435E-B01A-7091B263374D@cooperw.in> <967756CD-81E9-4F61-9153-C730C077A4F9@cooperw.in> <5A811FC8-4BC0-468C-9E16-9BBD093DED69@gmail.com> <AA35BBA1-F3EB-4DA4-8161-265869886FD9@cooperw.in> <61AC4384-1EBE-482D-95B0-3EB6B2CF3C2F@gmail.com> <BDCD1EBD-3550-4ADF-9417-BFC55661DF6B@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/onGoHbr8QQizo0oWZQ4SsLeJsIs>
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, 28 Feb 2019 13:15:42 -0000

Hi Bob,

> On Feb 27, 2019, at 8:56 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> 
> I reviewed the Diff.  Overall looks good, a few comments below.
> 
> Bob
> 
> —————
> 
>   Abstract and Introduction
> 
>   The IETF LLC provides the corporate legal home for the IETF, the
>   Internet Architecture Board (IAB), and the Internet Research Task
>   Force (IRTF).
> 
> Should this also mention the RFC Editor (as is done later in the document)?

I’m not sure which place you are referring to, but my take is the IETF LLC is not the corporate legal home of the RFC Editor, in the same way it is not the corporate legal home for AMS. It just provides funding. The corporate legal home language comes from the LLC Agreement.

> 
> ----------
> 
> 
>   4.1.  Terminology
> 
>   ...Uses of the term 'IASA' as a proper noun may imply a subset of these roles, or all of them.
> 
> Is this sentence necessary?

I think it is, because in some places where it is used it implies responsibilities that do not apply to one of the parties (e.g., the board). If instead people want to stop using it as a proper noun, then this could be dropped.

Alissa

> 
> ----------
> 
>   6.9.  Quorum
> 
>   At all synchronous live meetings of the Board, two-thirds of the
> 
> What does “synchronous live meetings” mean?  Are there other kinds of meetings, for example, asynchronous dead meetings?  I find this confusing.   I think just saying “meetings” is fine.   Making decision via email are not meetings.
> 
> ----------
> 
>   7.7.  Focus of Funding Support
> 
>   The IETF LLC exists to support the IETF, IAB, and IRTF.  Therefore,
>   the IETF LLC's funding and all revenues, in-kind contributions, and
>   other income that comprise that funding shall be used solely to
>   support activities related to the IETF, IAB, and IRTF and for no
>   other purposes.
> 
> I think the RFC Editor should be included in this paragraph.
> 
> ----------
> 
> 
> 
>> On Feb 27, 2019, at 8:11 AM, Bob Hinden <bob.hinden@gmail.com> wrote:
>> 
>> 
>> Alissa,
>> 
>>> On Feb 27, 2019, at 12:06 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>>> 
>>> Hi Bob,
>>> 
>>>> On Feb 27, 2019, at 1:13 AM, Bob Hinden <bob.hinden@gmail.com> wrote:
>>>> 
>>>> Alissa, Jason,
>>>> 
>>>> Could we get a diff of all of the changes?  
>>> 
>>> rfcdiff between -04 and -06 shows them all.
>> 
>> Thanks, a URL for this diff is:
>> 
>> https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-iasa2-rfc4071bis-04.txt&url2=https://tools.ietf.org/id/draft-ietf-iasa2-rfc4071bis-06.txt
>> 
>> Hopefully useful for others.  I will review it later today.
>> 
>> Bob
>> 
>> 
>>> 
>>> Alissa
>>> 
>>>> As you said, there are a lot of changes.
>>>> 
>>>> Thanks,
>>>> Bob
>>>> 
>>>> 
>>>>> On Feb 26, 2019, at 4:11 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>>>>> 
>>>>> Thanks for the updates. I have just a few more edits to suggest. Since there were a lot of changes, I’ll give people in the WG a few days to review this and will issue the IETF LC next Monday unless there is ongoing discussion on the list at that point.
>>>>> 
>>>>> 
>>>>> = Please fix the I-D nits. =
>>>>> 
>>>>> = Section 4.1 =
>>>>> 
>>>>> "IASA: The IETF Administrative Support Activity, defined by [RFC4071] and updated by this document …”
>>>>> 
>>>>> I don’t think this is right since this document is obsoleting RFC 4071. I think you could say “The IETF Administrative Support Activity was originally defined in RFC 4071. As defined in this document, IASA consists of … .”Or just drop the first sentence of the definition altogether.
>>>>> 
>>>>> = Section 5.2 =
>>>>> 
>>>>> s/(or amending/(or amend/
>>>>> 
>>>>> = Section 7.5 =
>>>>> 
>>>>> s/other IETF staff/other IETF LLC staff/
>>>>> 
>>>>> s/and approval/with approval/
>>>>> 
>>>>> = Section 7.6 =
>>>>> 
>>>>> s/convey to donors/convey to sponsors and donors/
>>>>> 
>>>>> = Section 14.2 =
>>>>> 
>>>>> draft-ietf-iasa2-rfc7437bis needs to be normative, not informative
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> iasa20 mailing list
>>>>> iasa20@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/iasa20
>>>> 
>>> 
>> 
>