Re: [nmrg] draft-irtf-nmrg-autonomic-network-definitions-01 feedback
Benoit Claise <bclaise@cisco.com> Tue, 22 July 2014 00:53 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: nmrg@ietfa.amsl.com
Delivered-To: nmrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39B411A01F3 for <nmrg@ietfa.amsl.com>; Mon, 21 Jul 2014 17:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 cXAG2AgXVXG2 for <nmrg@ietfa.amsl.com>; Mon, 21 Jul 2014 17:53:09 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EE521A0114 for <nmrg@irtf.org>; Mon, 21 Jul 2014 17:53:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2803; q=dns/txt; s=iport; t=1405990388; x=1407199988; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=lixobYzRlRA1oZouwv14NGhUdh9HoLhM0zW09AEOgoA=; b=krzysYtbFeYQYYwG1ly9UTAp7WO8hX6v8zlXWOVpr+FE6IrSctI5meId EMRMiBD07TNo0EQmii3/tbLcHgf/kvOkVLEf3nNsOj/r9cwssiYdEtccf eBVSw9OCDwKtVJJ/c768X8u2E0TBJgcydsOEmhUaB3al71vc6UfrW+G3f s=;
X-IronPort-AV: E=Sophos;i="5.01,706,1400025600"; d="scan'208";a="62851515"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-7.cisco.com with ESMTP; 22 Jul 2014 00:53:07 +0000
Received: from [10.82.219.128] (rtp-vpn3-892.cisco.com [10.82.219.128]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s6M0quam024082; Tue, 22 Jul 2014 00:52:57 GMT
Message-ID: <53CDB5E5.5020204@cisco.com>
Date: Mon, 21 Jul 2014 20:52:53 -0400
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <53CD5D41.6050302@cisco.com> <53CD8E33.7070808@gmail.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF21BEE9C7@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF21BEE9C7@xmb-rcd-x14.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/L4qiuMhXYVnpkLVxAtHRogX_s4M
Cc: "nmrg@irtf.org" <nmrg@irtf.org>
Subject: Re: [nmrg] draft-irtf-nmrg-autonomic-network-definitions-01 feedback
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Management Research Group discussion list <nmrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmrg>, <mailto:nmrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/nmrg/>
List-Post: <mailto:nmrg@irtf.org>
List-Help: <mailto:nmrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmrg>, <mailto:nmrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2014 00:53:10 -0000
Hi Michael, > Let me expand a bit about intent versus configuration. > > For now, I stick to what is written in the document: > > 1. Intent does NOT contain configuration. (note: "contain") Ok. > 2. An autonomic function does not REQUIRE configuration. This does not mean that there couldn't be a function that runs in a default mode using only intent, but could be locally also use some configuration. > > So, to me, intent and configuration will co-exist, but configuration is not part of the autonomic part (which is why I think the doc is actually correct). > > There is a need for conflict resolution. And this works something like this: > > prio 0: default behaviour (without intent) > prio 1: intent > prio 2: other (netconf, SNMP, i2rs, CLI, ...) > > In other words, a more specific guidance takes priority over a less specific one. Following this, an intent guidance will be overruled by CLI. (how the various options in my "prio 2" are sorted is outside scope for this discussion, and I guess someone has worked this out already?) > > For you Benoit, this leads to two questions: > 1. does the above explanation make sense, Ok > or am I missing your point? > 2. if it does, should this explanation in some form go into the definitions draft? No clear view on that one. > > Regarding: > -- > 3.7 Modularity > Section 3 intro says: > > This section explains the high level goals of Autonomic Networking, > independent of any specific solutions. > > Is this an Autonomic Networking design goal to be modular? Not really > I see this more like a good deployment practice, i.e. if you think about an autonomic protocol, please think of deployment, i.e. modularity > -- > > I wonder whether we should just delete that section? You are right, this is not specific to AN. Happy to delete. Regards, Benoit > > The other comments are clear, and I'll take care of them. > > Michael > > >> -----Original Message----- >> From: nmrg [mailto:nmrg-bounces@irtf.org] On Behalf Of Brian E Carpenter >> Sent: 21 July 2014 18:04 >> To: Benoit Claise (bclaise) >> Cc: nmrg@irtf.org >> Subject: Re: [nmrg] draft-irtf-nmrg-autonomic-network-definitions-01 >> feedback >> >> Thanks Benoit. Michael has the editing pen so I will only comment on one >> point right now: >> >>> I guess you want to rephrase that the intent is a general policy above >>> configuration or information for a specific node, >> I think it can also be for a specific role, where a bunch of nodes can all fill >> that role (e.g. an intent that applies to all CE routers, or all AFTRs,...). >> >> Regards >> Brian >> >> _______________________________________________ >> nmrg mailing list >> nmrg@irtf.org >> https://www.irtf.org/mailman/listinfo/nmrg > . >
- [nmrg] draft-irtf-nmrg-autonomic-network-definiti… Benoit Claise
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Brian E Carpenter
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Michael Behringer (mbehring)
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Laurent Ciavaglia
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Arran Cudbard-Bell
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Benoit Claise
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Laurent Ciavaglia
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Brian E Carpenter
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Olivier Festor
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Sheng Jiang
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Michael Behringer (mbehring)
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Alexander Clemm (alex)
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Brian E Carpenter
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Alexander Clemm (alex)
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Brian E Carpenter
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Benoit Claise
- Re: [nmrg] draft-irtf-nmrg-autonomic-network-defi… Michael Behringer (mbehring)