Re: [Anima] Intent "beginning to end"

John Strassner <strazpdj@gmail.com> Fri, 22 April 2016 01:25 UTC

Return-Path: <strazpdj@gmail.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 E922812EC0B for <anima@ietfa.amsl.com>; Thu, 21 Apr 2016 18:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 TUsqx6U-XvS5 for <anima@ietfa.amsl.com>; Thu, 21 Apr 2016 18:25:36 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 2524812EC18 for <anima@ietf.org>; Thu, 21 Apr 2016 18:25:35 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id c126so70886368lfb.2 for <anima@ietf.org>; Thu, 21 Apr 2016 18:25:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=KnlVsfJh2hRUYUdn8U+J61R+D6iggAp4ncr6ral8snA=; b=XWgIdm03Ib3+xDfIr6s4aaTc4Ne7oAQfto+2clWGbheMqyCjMpAHUkpnywnmyyyIpy NhCgVLl8bO9Gd2jzqoMKrpSl9U9oPBTcK2Sd9SG3YpiuKxXoMx3M/J5RHZiTCCKMAjUn VWxGgQHQGoEQkQWcQ8OYM9QJX3tHikwN8IdlVAj28GNww1+34zfhFZ5qH6XyU/Sf7nmD Tpr+x+qrNbtSz8mtAJXykpuYnbvwvBPLA9LbtPncBq7vhUZ5ivo6ehVWi5OtW124FIkK n2dlCvYnJAuTFPhLmLcdjYVLvR29NDmSp0gbxK1O8jIV0TpDdD6ZdDrxq+yj+BG4mhfP 1/Mw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=KnlVsfJh2hRUYUdn8U+J61R+D6iggAp4ncr6ral8snA=; b=VYMJNmVus5raG9vr3xnosFslmjPcwtMtBPO96d2xNZOqEpi1ZymWaEUZ6STukB8nyB 0dVIJJkFC2xyyWP5vMhpz5XKxPjTtDz5/nRQifoA7JAeEkBo7wf14nlbHoNK/T/k4oth +nEn5uKbt/F+DGBpdjMVuW1JdjtnzhkRa6Agm0KUWdeCS4/+4Rps1ZBe3cmcM3L2xshf p+MUo/q7NRDOUG1Ww1ufh2E01cxjmwnjwuCQ8nFLULiPQdG4FyLItP8O36/xmBU08IDw mzjM8E4ep1TjX2egqekDz0gCS+qXlB7m/CPzgbYqzdrUMaeB2/u76rUKvqviSmsp07S1 dDKQ==
X-Gm-Message-State: AOPr4FUxkvZie0YY//ONg2M91TgDUNTANP1QK80Pa67bkt56JXZRi6pXxNeZtpemZpcGPWZbw2WLg5nr/r6BjA==
MIME-Version: 1.0
X-Received: by 10.25.216.106 with SMTP id p103mr946883lfg.16.1461288333376; Thu, 21 Apr 2016 18:25:33 -0700 (PDT)
Received: by 10.25.21.105 with HTTP; Thu, 21 Apr 2016 18:25:33 -0700 (PDT)
In-Reply-To: <57197A8D.1000306@gmail.com>
References: <qmlk2x0r390tnev5gbvwictx.1461284618276@email.android.com> <57197A8D.1000306@gmail.com>
Date: Thu, 21 Apr 2016 18:25:33 -0700
Message-ID: <CAJwYUrEod6-QtXg=s54skzo=hapZQyFofyjQQbjZruVkjku2KQ@mail.gmail.com>
From: John Strassner <strazpdj@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, John Strassner <strazpdj@gmail.com>
Content-Type: multipart/alternative; boundary="001a1140d0ca0684cd053108b4ad"
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima/an2098aj_S85rMAxQpWMGgS-rZs>
Cc: "jmh.direct" <jmh.direct@joelhalpern.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "Michael Behringer (mbehring)" <mbehring@cisco.com>, Anima WG <anima@ietf.org>
Subject: Re: [Anima] Intent "beginning to end"
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, 22 Apr 2016 01:25:38 -0000

> Intent (H): what humans generate, that must be sanity checked,
> reconciled, and compiled into
> Intent (A): a consistent form of Intent that can be interpreted
> by an algorithm in any autonomic node.

When I read draft draft-du-anima-an-intent-03, I got the impression
that both Intent (H) and Intent (A) were worked on in the policy
system. Even if this is not the case, clearly nodes that are not
fully autonomic will not be interested in adding additional
resources to understand and act on intent.

My problem is that I do not believe that we can define a mechanism
to specify Intent (A) in a vendor-independent, interoperable manner.
Hence, I see no reason why **every** mode MUST be able to ingest
and act on intent.

regards,
John

On Thu, Apr 21, 2016 at 6:12 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 22/04/2016 12:23, jmh.direct wrote:
> > From what I have seen, at the business level the needed information is
> spread across multiple sources.  So if, as diagrammed, Intent starts at the
> human, then something needs to compile it together.
>
> Certainly. So in fact we are talking about two different things.
>
> Intent (H): what humans generate, that must be sanity checked, reconciled,
> and compiled into
> Intent (A): a consistent form of Intent that can be interpreted by an
> algorithm in any autonomic node.
>
> I believe that Anima should focus on Intent (A).
>
>    Brian
>
> > Yours,Joel
> >
> >
> > Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone--------
> Original message --------From: Brian E Carpenter <
> brian.e.carpenter@gmail.com> Date: 4/21/2016  5:02 PM  (GMT-05:00) To:
> John Strassner <strazpdj@gmail.com>, "Joel M. Halpern" <
> jmh@joelhalpern.com> Cc: Anima WG <anima@ietf.org>, "Michael Behringer
> (mbehring)" <mbehring@cisco.com> Subject: Re: [Anima] Intent "beginning
> to end"
> > On 22/04/2016 08:46, John Strassner wrote:
> > ...
> >>     3) I believe that interpreting/compiling intent will be HARD, and
> >>         that understanding intent will be MUCH HARDER. Why does
> >>         every autonomic node need to do that?
> >
> > Surely that depends on the detailed design of Intent syntax and
> semantics,
> > by which I mean the Intent that is distributed to all autonomic nodes
> > and hence to all ASAs. Given that we know it needs to be interpreted by
> > individual ASAs, shouldn't we design it to be readily interpreted?
> > (If there is some more abstract format of Intent that is *not*
> distributed
> > everywhere, that's fine, but it's not our concern for designing Anima.
> > We have to worry about the concrete Intent that's sent to all AN nodes.)
> >
> > An ASA that manages resource X, which involves negotiation with other
> > ASAs also managing resource X, and setting configuration for itself and
> > perhaps for subsidiary non-autonomic devices using resource X, will need
> > to interpret statements about settings the affect resource X, as well as
> > statements about generic settings. So they need to be readily
> interpretable.
> >
> >     Brian
> >
>
>


-- 
regards,
John