Re: [Anima] Ben Campbell's No Objection on draft-ietf-anima-reference-model-08: (with COMMENT)

Ben Campbell <ben@nostrum.com> Thu, 25 October 2018 20:35 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16765130E67; Thu, 25 Oct 2018 13:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=unavailable 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 qOOrfFQcKMiO; Thu, 25 Oct 2018 13:35:09 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 992CC130DC3; Thu, 25 Oct 2018 13:35:09 -0700 (PDT)
Received: from [10.0.1.27] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9PKY0mR006770 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 25 Oct 2018 15:35:00 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.27]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <91FB1474-0A4D-4A5B-9588-7A81B21208FB@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_CE954BBA-EF3A-43BB-88FC-B2CF6990F8E8"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Thu, 25 Oct 2018 15:35:00 -0500
In-Reply-To: <d17bd732-6059-40db-7c2d-6de0d30969da@gmail.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, The IESG <iesg@ietf.org>, Toerless Eckert <tte+anima@cs.fau.de>, anima-chairs@ietf.org, anima@ietf.org, draft-ietf-anima-reference-model@ietf.org, Sheng Jiang <jiangsheng@huawei.com>
To: "Michael H. Behringer" <michael.h.behringer@gmail.com>
References: <154042252127.6853.18391573929277125477.idtracker@ietfa.amsl.com> <1db87d2f-6709-2613-0422-182989531701@gmail.com> <CE5C5C5B-5811-4825-AD6E-5F076C386A9E@nostrum.com> <d13fc74a-e61e-ca63-3283-5ce1be247966@gmail.com> <9E85B59E-93AF-4225-B143-DC56796FCB67@nostrum.com> <d17bd732-6059-40db-7c2d-6de0d30969da@gmail.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/oeol-ZRVeWLFnrhbPFZfbgczHEY>
Subject: Re: [Anima] Ben Campbell's No Objection on draft-ietf-anima-reference-model-08: (with COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2018 20:35:11 -0000

""This section discusses a topic for further research” sounds good to me.

Thanks!

Ben.

> On Oct 25, 2018, at 2:47 PM, Michael H. Behringer <michael.h.behringer@gmail.com> wrote:
> 
> Ah, now I understand. Thanks for clarifying. Yes, we really used it as sort of a "boiler plate" for topics that are not part of this phase of ANIMA work. I guess we just introduced (informational)^2.
> 
> I'm happy to change that "boiler plate" text.  What about "This section discusses a topic for further research".
> 
> I guess we can edit that when we get to the RFC Editor queue.
> 
> Michael
> 
> On 25/10/2018 17:18, Ben Campbell wrote:
>> Hi Michael,
>> 
>> My real concern is that “informational” is a term of art in the IETF, and the use of it to label “later phase” sections is a different use than that.
>> 
>> I will leave it to the authors to decide if that would be confusing to the target audience.
>> 
>> Thanks!
>> 
>> Ben.
>> 
>>> On Oct 25, 2018, at 3:43 AM, Michael H. Behringer <michael.h.behringer@gmail.com> wrote:
>>> 
>>> Hi Ben, thanks for your review!
>>> 
>>> Yes, we're a bit "verbose" with those topics. There was a consistent worry all through our work to distinguish phase 1 and phase 2 work, and to not let phase 2 work creep into phase 1. So we probably erred on the more "explicit" wording, trying to make REALLY sure everybody understands what's in scope for phase 1 or not.
>>> 
>>> Unless you have a real concern at some specific points, I would prefer to not open those debates again. Yes, from a language point of view there is redundancy, but at least we're being very clear.
>>> 
>>> Michael
>>> 
>>> 
>>> On 25/10/2018 04:33, Ben Campbell wrote:
>>>>> On Oct 24, 2018, at 8:10 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>>> 
>>>>> Hi Ben,
>>>>> 
>>>>> On 2018-10-25 12:08, Ben Campbell wrote:
>>>>> ....
>>>>> 
>>>>>> Thanks for the work on this. I just have one editorial comment:
>>>>>> 
>>>>>> - Several sections describe themselves as being for "informational purposes".
>>>>>> Given that this is an informational document, isn't that true of all sections?
>>>>> Those sections are among the ones tagged (*) as per:
>>>>> 
>>>>>>>   Some topics are considered architecturally
>>>>>>>   in this document, but are not yet reflected in the implementation
>>>>>>>   specifications.  They are marked with an (*).
>>>>> Possibly the (*) is sufficient and the phrase you mention can be removed.
>>>> I think that could help. Or alternatively, put a few extra words in the (*) sections to remind people what it means :-)
>>>> 
>>>> Thanks!
>>>> 
>>>> Ben.
>