Re: [Anima] Martin Vigoureux's Block on charter-ietf-anima-01-05: (with BLOCK and COMMENT)

Toerless Eckert <tte@cs.fau.de> Wed, 01 May 2019 14:14 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 896D61200CE; Wed, 1 May 2019 07:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 NqIfqWOHnOXU; Wed, 1 May 2019 07:14:43 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD20D12013A; Wed, 1 May 2019 07:14:42 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 8BEB8548874; Wed, 1 May 2019 16:14:37 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 77F7E440041; Wed, 1 May 2019 16:14:37 +0200 (CEST)
Date: Wed, 01 May 2019 16:14:37 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Vigoureux, Martin (Nokia - FR/Paris-Saclay)" <martin.vigoureux@nokia.com>
Cc: Barry Leiba <barryleiba@computer.org>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, The IESG <iesg@ietf.org>, "anima@ietf.org" <anima@ietf.org>
Message-ID: <20190501141437.tedkbtbcp5seapco@faui48f.informatik.uni-erlangen.de>
References: <155655905154.15849.12085215696912730275.idtracker@ietfa.amsl.com> <CALaySJJOAHN+VM6gvr1hYKyeHqsqBfrVCzomjJr5bpzBhPB5tQ@mail.gmail.com> <DB7PR07MB4999351F158AC55DFB9270938C390@DB7PR07MB4999.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DB7PR07MB4999351F158AC55DFB9270938C390@DB7PR07MB4999.eurprd07.prod.outlook.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/i1xuSGr_7aRu1zrAHx_I5uuWvLc>
Subject: Re: [Anima] Martin Vigoureux's Block on charter-ietf-anima-01-05: (with BLOCK and 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: Wed, 01 May 2019 14:14:44 -0000

Thanks, Martin, inline

On Mon, Apr 29, 2019 at 08:50:16PM +0000, Vigoureux, Martin (Nokia - FR/Paris-Saclay) wrote:
> Hi Barry,
> 
> I had reached the same conclusion, but I think not everyone might and as you highlight it shouldn't be difficult to make sure that there is no misunderstanding of what is in scope and out of scope of the charter.

On the first item, would Barry's rewrite proposal resolve your concern ?
If not, do you have a specific textual suggestion ?

> On the second item, I am afraid that this charter might be setting expectations on the pace (though not quantified) at which documents will be processed between adoption and LC.

Yes, although i would call it more "preference" than "expectation".

We had from day 1 of ANIMA expectations from our ADs for speedy delivery
of implementable results helping operators (rightfully so given how
ANIMA is in OPS) versus an ongoing influx of more researchy participants
(rightfully so given ANIMA was created from NMRG output).

In this context we felt it to be useful to emphasise to both 
constituents (OPS/IESG and participants) how we need to manage our
process to meet expecations.

Cheers
    Toerless

> -m
> 
> -----Original Message-----
> From: Barry Leiba <barryleiba@computer.org> 
> Sent: Monday, April 29, 2019 20:59
> To: Vigoureux, Martin (Nokia - FR/Paris-Saclay) <martin.vigoureux@nokia.com>
> Cc: The IESG <iesg@ietf.org>; anima-chairs@ietf.org; anima@ietf.org
> Subject: Re: Martin Vigoureux's Block on charter-ietf-anima-01-05: (with BLOCK and COMMENT)
> 
> > I am under the impression that there is a small ambiguity in the 
> > charter, which shouldn't be hard to resolve:
> >
> >    ANIMA work will rely on the framework described in
> >    draft-ietf-anima-reference-model. [...] The three areas of the framework are
> >    [...] and (3) Intent.
> >
> >    ANIMA will not work on Intent [...] without explicit rechartering.
> >
> > The first piece seems to allow for working on Intent while the second 
> > clearly not (within the current charter).
> 
> I tripped over that also when I first read it, but then understood:
> the WG will rely on the framework, which includes a set of things.
> Not all of those things will be worked on via this charter.  In particular, "intent" is one of the things that won't be.
> 
> As I read it, I think the charter is OK.  I suppose it could be clarified this way:
> 
> OLD
> ANIMA work will rely on the framework described in draft-ietf-anima-reference-model. Work not related to this framework is welcome for review, but WG adoption of such work requires explicit rechartering. The three areas of the framework are (1) the Autonomic Networking Infrastructure (ANI), (2) Autonomic Functions (AF) built from software modules called Autonomic Service Agents (ASA) and (3) Intent.
> 
> NEW
> ANIMA work will rely on the framework described in draft-ietf-anima-reference-model, though only parts of the framework are in scope for this charter, as detailed below.  Work not related to this framework is welcome for review, but WG adoption of such work requires explicit rechartering.
> The three areas of the framework are (1) the Autonomic Networking Infrastructure (ANI), (2) Autonomic Functions (AF) built from software modules called Autonomic Service Agents (ASA) and (3) Intent.
> 
> END
> 
> > I'm not sure to understand what the following means:
> >
> >    Acceptance of work items by the WG will be scheduled/throttled so that
> >    contributors can target them to enter WG last call after not more than a number
> >    of IETF meeting cycles agreed by the AD.
> 
> As I read it, it means that the working group won't take on so much work that the work they do take on doesn't get done.  Acceptance is based on negotiating a schedule (based on meeting cycles), and if the schedule isn't met, new work items can't be accepted.
> 
> Barry
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima