[Anima] Anima/Laurent: re. figuring out intent

Toerless Eckert <tte@cs.fau.de> Fri, 18 November 2016 02:21 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 D8C6312979D for <anima@ietfa.amsl.com>; Thu, 17 Nov 2016 18:21:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.696
X-Spam-Level:
X-Spam-Status: No, score=-5.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497] 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 VEvEhp2ZhCn1 for <anima@ietfa.amsl.com>; Thu, 17 Nov 2016 18:21:36 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BA9F128E18 for <anima@ietf.org>; Thu, 17 Nov 2016 18:21:36 -0800 (PST)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 73E5358C4B0; Fri, 18 Nov 2016 03:21:34 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 56B6BB0AE82; Fri, 18 Nov 2016 03:21:34 +0100 (CET)
Date: Fri, 18 Nov 2016 03:21:34 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Laurent Ciavaglia <Laurent.Ciavaglia@alcatel-lucent.com>
Message-ID: <20161118022132.GA3400@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/VWg077c2FMN8ipFgghSqlMZHTTs>
Cc: anima@ietf.org
Subject: [Anima] Anima/Laurent: re. figuring out intent
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 18 Nov 2016 02:21:38 -0000

Laurent: wrt to your comment on the mike in Seoul:

Thanks for crushing my hopes to find a way through the jungle ;-)
Kidding. Very good comment, very much appreciated.

So, if a full, even high level, direction for intent is further out because,
would it then make sense to think of shorter term incremental definitions,
hopefully in a way that they could be reuseable building blocks for intent
later.

For example: A lot of network service provisioning today is done just with group-template
based per-device configuration. Shouldn't we look at how we could improve and/or
standardize this approach with anima. The semantic would be blocks of
device configuration surrounded by a meta layer to define groupings eg:
by device/vendor type/roles etc.. 

Maybe this is not the right incremental step. But my main question is:
what incremental steps, if any do make most sense to you and others looking
into intent.

Cheers
    Toerless