Re: [Anima] Intent per ASA or per AF?
Laurent Ciavaglia <Laurent.Ciavaglia@nokia-bell-labs.com> Fri, 18 November 2016 02:04 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 043F512985B for <anima@ietfa.amsl.com>; Thu, 17 Nov 2016 18:04:42 -0800 (PST)
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 ThyGg8HcGiXb for <anima@ietfa.amsl.com>; Thu, 17 Nov 2016 18:04:39 -0800 (PST)
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 2C7E512979D for <anima@ietf.org>; Thu, 17 Nov 2016 18:04:37 -0800 (PST)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id 9BD08DFC0C790; Fri, 18 Nov 2016 02:04:34 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id uAI24YeK017153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 18 Nov 2016 02:04:35 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id uAI24YrV006612 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Nov 2016 03:04:34 +0100
Received: from [135.224.207.20] (135.239.27.38) by FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 18 Nov 2016 03:04:33 +0100
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, "anima@ietf.org" <anima@ietf.org>
References: <7f30b33118334c09a54acb9293b2c265@XCH-RCD-006.cisco.com>
From: Laurent Ciavaglia <Laurent.Ciavaglia@nokia-bell-labs.com>
Organization: Nokia Bell Labs
Message-ID: <ee95389f-d74d-a5f1-6292-ba875613e6a2@nokia-bell-labs.com>
Date: Fri, 18 Nov 2016 03:04:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7f30b33118334c09a54acb9293b2c265@XCH-RCD-006.cisco.com>
Content-Type: multipart/alternative; boundary="------------377EF7A34481CE41A9E810DB"
X-Originating-IP: [135.239.27.38]
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/V67NXVyPlimS-KiCkHFhbRO2EvM>
Subject: Re: [Anima] Intent per ASA or per AF?
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:04:42 -0000
Michael, Definitely not designed per ASA. As mentioned at the mic, in draft-peloso (https://datatracker.ietf.org/doc/draft-peloso-anima-autonomic-function), we've proposed format for "intent" at the AF level. Please note, that once "resolved" the AF intent will exist (be translated) in the instances of the AF (the ASAs) as AF instance descriptor. This is ASA-level/specific information. Best regards, Laurent. On 18/11/2016 02:53, Michael Behringer (mbehring) wrote: > One question that just came up: Should Intent be designed per ASA or per AF? > > My suggestion previously was to segment Intent into sections per Autonomic Functions. > > Example: Intent for the bootstrap function could be: > - allow bootstrapping new devices only during maintenance window > > For such Intent, action could be taken on the registrar (one ASA of the AF), or on the proxy (another ASA of the same AF). > > It seems to me an author of an AF might like all ASAs of his AF to know about the Intent, because the proxy may also take actions. > > Michael > > _______________________________________________ > Anima mailing list > Anima@ietf.org > https://www.ietf.org/mailman/listinfo/anima > -- Laurent Ciavaglia Nokia, Bell Labs +33 160 402 636 route de Villejust - Nozay, France linkedin.com/in/laurent.ciavaglia
- [Anima] Intent per ASA or per AF? Michael Behringer (mbehring)
- Re: [Anima] Intent per ASA or per AF? Laurent Ciavaglia
- Re: [Anima] Intent per ASA or per AF? Brian E Carpenter
- Re: [Anima] Intent per ASA or per AF? Michael Behringer (mbehring)
- Re: [Anima] Intent per ASA or per AF? ludwig
- Re: [Anima] Intent per ASA or per AF? Michael Richardson
- Re: [Anima] Intent per ASA or per AF? Michael Behringer (mbehring)
- Re: [Anima] Intent per ASA or per AF? Brian E Carpenter
- Re: [Anima] Intent per ASA or per AF? Michael Behringer (mbehring)