[Anima] What is intent ?

Toerless Eckert <tte@cs.fau.de> Tue, 25 July 2017 20:35 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 8637C1317C1 for <anima@ietfa.amsl.com>; Tue, 25 Jul 2017 13:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id zMllurJf-icA for <anima@ietfa.amsl.com>; Tue, 25 Jul 2017 13:34:59 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE103131461 for <anima@ietf.org>; Tue, 25 Jul 2017 13:34:58 -0700 (PDT)
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 3C91758C4D8; Tue, 25 Jul 2017 22:34:55 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 25FD4B0C6BF; Tue, 25 Jul 2017 22:34:55 +0200 (CEST)
Date: Tue, 25 Jul 2017 22:34:55 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: anima@ietf.org, nmrg@ietf.org
Message-ID: <20170725203454.GA7884@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/4gx3vT7DKHgZiG_GfDzqAfwgdhA>
Subject: [Anima] What is intent ?
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 25 Jul 2017 20:35:00 -0000

I have an autonomic network, and i want for another customer another
L3VPN service instance in it.  How would i tell the network that i want
this ? Via intent or via something else ?

If it is something else, what is it ? I do not see any other information flow from
operator to network beside intent in RFC7575 or draft-ietf-anima-reference-model. 
Maybe i am missing something.

If it is intent, how would it look like ? Could it simply be a definition
of an L3VPN service instance in the model defined in rfc8049 ? If not, why not ?

IMHO: Intent in ANIMA includes service definitions such as what rfc8049 is,
except that we would reserve the right to eliminate all parameters of rfc8049
for which we figure out autonomic ways to determine them. Which alas seems to
be quite difficult for most parameters. 

Other folks in the IETF clearly think that a service definition is NOT intent,
but intent can only be some yet unclear high level policy. If thats the
prevailing opinion/wisdom in the IETF, then IMHO we need to be more explicit about the
fact that Intent is not the only input into the network but that there is
also other input. Such as services. And anything else that people do not want to
call Intent.

Lets assume service and other necessary data operator->network should not
be called intent. But lets say the superset of intent + services + everything
else is called eg: "information". I think that draft-du-anima-an-intent
would equally apply to all information we would want to distribute into
an autonomic network.