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

Bob Hinden <bob.hinden@gmail.com> Thu, 28 February 2019 21:36 UTC

Return-Path: <bob.hinden@gmail.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 E221B13103A for <iasa20@ietfa.amsl.com>; Thu, 28 Feb 2019 13:36:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 b1K9WGm8T49i for <iasa20@ietfa.amsl.com>; Thu, 28 Feb 2019 13:36:44 -0800 (PST)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 1E93F131036 for <iasa20@ietf.org>; Thu, 28 Feb 2019 13:36:44 -0800 (PST)
Received: by mail-wr1-x42e.google.com with SMTP id w2so23605972wrt.11 for <iasa20@ietf.org>; Thu, 28 Feb 2019 13:36:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/aaVGvzCKZYx44tLP+d7Y6uRctCBNgKKF7BLgGf/mf0=; b=pv5daEc/IOoiDTUSxe5e9ifqpUDObgDmza9gZBax28JcNla396Mpx4J2bEOUFsKvwO n9wOiGEKod661gWzPUi80AZcJVw+5BriL+X4n0nTAhe0przoXCIS8qlRIelO+KxhCJzF EgQW8f9AYHaXx5zpy8T0fY0aZgSA/gw4FPaTG6QpIMuTeHWZsTOzVRNAJNDbq7cmZ+NL guhcGXsd3A/+eXYtnL6nMHogCEua70Zh1DbTbmJsVRzTvRT76SXqTLnWpOPtJ61zh+d4 fDf8saQ0vxDbYEDvvMuqQ+NhdowP8Q5QCFLJKxBf3tpGtwdLK5hK357JSjLH32BMrnX8 FiYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/aaVGvzCKZYx44tLP+d7Y6uRctCBNgKKF7BLgGf/mf0=; b=rU4bJcag84ugSNKw+2jawy34DOTNHliip5cpJ1fDTlj8qGqtO5BKqXAkBYO3kfZMxS J+hcDIrKE++gSdCrhlI26QvGUFMI3u7GxJshDkgB8h5DXvM6gVc+9LN1mSDrBwZDb6Qg TfMng3y0Che4WO+pt5rxcWYV0BGHNwec4aryeAZp7PAhZZxPuLmV+Yvs/PGJaEecRiMR fDCbPYI+uMjxjtW66OZDPUIn+t8EXdQe8eXEX07e/S8GVuvyEeSxKBhyl3HhWCKW7+8t eHJ4HLuRwozEIC1o0IbVQ2OWQmm6/TMWaxB/esqyEowMRPLDd6zZ2Vfhdbw1KaUrDaTW j+Tw==
X-Gm-Message-State: APjAAAW805/XwucWTHL09xwfcQOEsYfvY0GBOCZlFPjdA86yQVyuFmm/ N9cLIl9arSv0c3V1Q8gGt64=
X-Google-Smtp-Source: APXvYqxAOijt5WpHRUOzYHbZu2Mp0LlCEnSnakpQ2OdAYpS+GK2rVbb97Cz8bAOtfv0DuOlyoKzn2A==
X-Received: by 2002:adf:8273:: with SMTP id 106mr1077772wrb.34.1551389802451; Thu, 28 Feb 2019 13:36:42 -0800 (PST)
Received: from ?IPv6:2601:647:4d01:f3a:156c:6370:41f1:793b? ([2601:647:4d01:f3a:156c:6370:41f1:793b]) by smtp.gmail.com with ESMTPSA id v20sm4089754wmj.2.2019.02.28.13.36.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Feb 2019 13:36:41 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <0030789F-6FBC-4600-B33B-4F20BB8B8475@cooperw.in>
Date: Thu, 28 Feb 2019 13:36:40 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, IASA 2 WG <iasa20@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1AA4E4E-F151-41F9-B607-FC2385D30C13@gmail.com>
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> <98795E4E-D0A1-475B-AEA5-3013C94EE758@cooperw.in> <8B43D76D-E0CF-4548-9244-943FB81AF24D@gmail.com> <0030789F-6FBC-4600-B33B-4F20BB8B8475@cooperw.in>
To: Alissa Cooper <alissa@cooperw.in>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/vDzfskU0dnZcdX41ZVBRMElRxqs>
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 21:36:47 -0000

Alissa,

> On Feb 28, 2019, at 10:11 AM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> Hi Bob,
> 
>> On Feb 28, 2019, at 5:32 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>> 
>> Alissa,
>> 
>> 
>>> On Feb 28, 2019, at 5:15 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>>> 
>>> 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.
>> 
>> I should have been clearer.   In Section 4.4 it says:
>> 
>>   o  Unification: The IETF LLC is responsible for providing unified
>>      legal, financial, and administrative support for operation of the
>>      IETF, IAB, and IRTF, and financial support for the operation of
>>      the RFC Editor.
>> 
>> I am suggesting that the text in the Abstract and Introduction (same text) mirror that.  I propose:
>> 
>> CURRENT:
>> 
>>        The IETF LLC provides the corporate legal home for the IETF, the	
>> 	Internet Architecture Board (IAB), and the Internet Research Task	
>> 	Force (IRTF).	
>> 	                     
>> NEW:
>> 
>>        The IETF LLC provides the corporate legal home for the IETF, the	
>> 	Internet Architecture Board (IAB), and the Internet Research Task	
>> 	Force (IRTF), and financial support for the operation of
>>        the RFC Editor.	
>> 	                     
> 
> WFM.

Good, thanks.

> 
>> 
>>> 
>>>> 
>>>> ----------
>>>> 
>>>> 
>>>> 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.
>> 
>> People are going to use it the way they use it.  
> 
> I meant in our other process documents. There was an opportunity to not use it this way, but the WG wanted to use it this way.
> 
>> Putting this test in the document won’t change that.
> 
> I agree (assuming you meant text, not test). Since one of the objectives of this whole exercise is to provide clarity over who is responsible for what and “IASA” when used as a proper noun is vague by its nature, I think this extra bit of explanation is important.

OK.

Bob

> 
> Alissa
> 
>> 
>> Bob
>> 
>> 
>>> 
>>> 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
>