Re: [Anima] Fwd: New Version Notification for draft-du-anima-an-intent-04.txt

Laurent Ciavaglia <Laurent.Ciavaglia@nokia-bell-labs.com> Mon, 11 July 2016 12:37 UTC

Return-Path: <laurent.ciavaglia@nokia-bell-labs.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 06C4712D7B3 for <anima@ietfa.amsl.com>; Mon, 11 Jul 2016 05:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 9tOiu0rf1HJH for <anima@ietfa.amsl.com>; Mon, 11 Jul 2016 05:37:42 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A1A512D759 for <anima@ietf.org>; Mon, 11 Jul 2016 05:37:42 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 06CA3B4EF6E9E; Mon, 11 Jul 2016 12:37:38 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u6BCbdwR011078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 11 Jul 2016 12:37:40 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u6BCbdnb032643 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 11 Jul 2016 14:37:39 +0200
Received: from [172.27.205.129] (135.239.27.40) by FR711WXCHHUB02.zeu.alcatel-lucent.com (135.239.2.112) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 11 Jul 2016 14:37:38 +0200
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Michael Behringer (mbehring)" <mbehring@cisco.com>, anima <anima@ietf.org>
References: <20160708153949.32209.45567.idtracker@ietfa.amsl.com> <f71bea03-d9a0-8178-cd3f-91671a66551c@nokia-bell-labs.com> <1fe314ad-d22f-1291-7e85-4e51ccd328a2@gmail.com> <c5cb4a64cc924448a215c263888888e2@XCH-RCD-006.cisco.com> <54f47cc8-bd8b-3783-274a-86e98d9e49ea@gmail.com>
From: Laurent Ciavaglia <Laurent.Ciavaglia@nokia-bell-labs.com>
Organization: Nokia Bell Labs
Message-ID: <4ce143d1-d623-702e-5926-1fbc174020ad@nokia-bell-labs.com>
Date: Mon, 11 Jul 2016 14:37:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <54f47cc8-bd8b-3783-274a-86e98d9e49ea@gmail.com>
Content-Type: multipart/alternative; boundary="------------4216BF61F0C0796AF02F90C3"
X-Originating-IP: [135.239.27.40]
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/CMWJ67G0O5TFH1n8KQt7MM4SK1M>
Subject: Re: [Anima] Fwd: New Version Notification for draft-du-anima-an-intent-04.txt
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: Mon, 11 Jul 2016 12:37:44 -0000

Hello,

> Yes. There's been an assumption, I think, that one "autonomic function" == one ASA.
> We need to be clear if that is an axiom, and we need to think about how ASAs are
> named, and if those names need to be registered somehow.

Mmmh... where does this assumption come from...?
I think we've been quite clear the general case is one AF == multiple 
ASAs. An AF instantiated by (only) one ASA is a sub-case. Cf. figure 1 
of the Reference model draft.

Why would ASAs need a name? That ASA need an ID is ok, but machines 
don't care about having stuff referenced with names... and I don't think 
human operators will have to deal with ASAs (one of the goals of 
ANetworking), or at least not often enough to justify the use of a 
naming scheme.
AFs could have names (and would actually need more than just name, e.g. 
version number, description of what it does, requires, etc.).

Or am I completely overlooking something?

Best regards, Laurent.