Re: [nmrg] Updating draft-irtf-nmrg-autonomic-network-definitions-00

"Michael Behringer (mbehring)" <mbehring@cisco.com> Fri, 27 June 2014 07:00 UTC

Return-Path: <mbehring@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 361161B3165 for <nmrg@ietfa.amsl.com>; Fri, 27 Jun 2014 00:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 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.651, 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 m6Iqlbwi3Va9 for <nmrg@ietfa.amsl.com>; Fri, 27 Jun 2014 00:00:26 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7049C1B2AE7 for <nmrg@irtf.org>; Fri, 27 Jun 2014 00:00:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3556; q=dns/txt; s=iport; t=1403852426; x=1405062026; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=V3IQoLT1LcxVGR6u7oHP4EnLhpEXLZUswsRAAgatbvg=; b=VFZEsV1guvp6NOGesksn7KCq7GlBrKZQD4r6xNVaQ5oVhwVSKKDE572B iARjdp9wkb01Bdufbs+jsDX+gqff0Av2/YN5C9vcwAZWMvFAUKSmZDKDP HIETlCrkVnCyofe9gq+tR2aDoXnYo4JwkU2Wve94WvIUBHP15/SfB6KQO 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuMFAEAWrVOtJV2b/2dsb2JhbABbgw2BLIJup0QBAQEBAQEFAW2YfQEZcRZ1hAMBAQEEIxFRBAIBCBEEAQEDAgYdAwICAjAUAQgIAQEEARIIiDqlWJ04F4ErhDmIRCc4BoJxNoEWBa5Og0KBbkI
X-IronPort-AV: E=Sophos;i="5.01,558,1400025600"; d="scan'208";a="336015545"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-2.cisco.com with ESMTP; 27 Jun 2014 07:00:25 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s5R70Pau005064 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 27 Jun 2014 07:00:25 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.51]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Fri, 27 Jun 2014 02:00:18 -0500
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "anima@ietf.org" <anima@ietf.org>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: Updating draft-irtf-nmrg-autonomic-network-definitions-00
Thread-Index: Ac+Ps8dVKhhDDzh8R4WTmNCrIuSMYgAmu8DAADYwkFAAHyjQkAAMNiqA
Date: Fri, 27 Jun 2014 07:00:17 +0000
Message-ID: <3AA7118E69D7CD4BA3ECD5716BAF28DF21BD33ED@xmb-rcd-x14.cisco.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF21BCA03D@xmb-rcd-x14.cisco.com> <5D36713D8A4E7348A7E10DF7437A4B923AEBC73A@nkgeml512-mbx.china.huawei.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF21BD222A@xmb-rcd-x14.cisco.com> <5D36713D8A4E7348A7E10DF7437A4B923AEC11E3@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AEC11E3@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.238.133]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/qI1muCuIDK9RDwuiQdPw7sNWZvQ
Subject: Re: [nmrg] Updating draft-irtf-nmrg-autonomic-network-definitions-00
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: Fri, 27 Jun 2014 07:00:28 -0000

Sheng, 

> -----Original Message-----
> From: Sheng Jiang [mailto:jiangsheng@huawei.com]
> Sent: 27 June 2014 03:33
> To: Michael Behringer (mbehring); anima@ietf.org; nmrg@irtf.org
> Subject: RE: Updating draft-irtf-nmrg-autonomic-network-definitions-00
> 
> >> One comments: the current definition of autonomic network looks
> vague.
> >> May I propose to modify it: a network which employs autonomic
> >> functions network-wide.
> >
> >Thanks for the suggestion Sheng. Well, I think the definition is
> >recursive, and actually DOES reflect what you're suggesting, because it
> says:
> >
> >      <t>Autonomic Network: A network containing autonomic nodes.</t>
> >and
> >      <t>Autonomic Node: A node which employs autonomic functions. It
> >may
> >      operate on any layer of the networking stack. Examples are routers,
> >      switches, personal computers, call managers, etc.</t>
> >
> >The only thing that's not covered is the "network wide". But that's
> >also not necessarily true, because an autonomic function could well
> >span only a few devices.
> 
> Hi, Michael,
> 
> The point is how much scale of autonomic function can be called an
> autonomic network. Say, if there is a network with hundreds devices, two of
> these devices has been deployed some autonomic functions. Can the
> network be claimed as an autonomic network? "Network wide" does not
> mean every devices. It means a large portion of the network have
> autonomic functions.

The fundamental question is whether we want to include autonomic functions that for example just involve two devices. And I would strongly suggest YES, for example I can see improvements on VRRP in the future as an autonomic function (you could already claim some limited autonomy, in fact). We want to cover that, right? 

Michael

> >We could change the Autonomic Function definition to (last sentence
> added):
> >
> >      <t>Autonomic Function: A function which requires no
> >configuration, and
> >      can derive all required information either through
> >self-knowledge, discovery
> >      or through intent. Typically an autonomic function spans several
> >nodes.</t>
> >
> >What do you think? I'm a bit in between "yes, this is more precise",
> >and "this doesn't add much value and complicates things". Slight
> >tendency to agree to add it.
> 
> This is helpful. But it does not address my concern regarding to the
> autonomic network definition.
> 
> Regards,
> 
> Sheng
> 
> >Thoughts?
> >
> >Michael
> >
> >
> >>
> >> Best regards,
> >>
> >> Sheng