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

Sheng Jiang <jiangsheng@huawei.com> Fri, 27 June 2014 09:55 UTC

Return-Path: <jiangsheng@huawei.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 895F61B2F4F for <nmrg@ietfa.amsl.com>; Fri, 27 Jun 2014 02:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.252
X-Spam-Level:
X-Spam-Status: No, score=-3.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=unavailable
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 LzZgwjw7eWRv for <nmrg@ietfa.amsl.com>; Fri, 27 Jun 2014 02:55:31 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0FDC1B2CED for <nmrg@irtf.org>; Fri, 27 Jun 2014 02:55:30 -0700 (PDT)
Received: from 172.24.2.119 (EHLO nkgeml405-hub.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BXV63657; Fri, 27 Jun 2014 17:55:25 +0800 (CST)
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.249]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Fri, 27 Jun 2014 17:55:20 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, "anima@ietf.org" <anima@ietf.org>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: [Anima] Updating draft-irtf-nmrg-autonomic-network-definitions-00
Thread-Index: AQHPkeytPe7kAOvbJkO8AgJ/3sNQlJuEtauA
Date: Fri, 27 Jun 2014 09:55:20 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AEC157F@nkgeml512-mbx.china.huawei.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> <3AA7118E69D7CD4BA3ECD5716BAF28DF21BD33ED@xmb-rcd-x14.cisco.com> <5D36713D8A4E7348A7E10DF7437A4B923AEC1488@nkgeml512-mbx.china.huawei.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF21BD3776@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF21BD3776@xmb-rcd-x14.cisco.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/ihtHF4Vi2gjOGKrTiUb5mDySA9Q
Subject: Re: [nmrg] [Anima] 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 09:55:32 -0000

>> >> 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?
>>
>> That's a valid use case for autonomic function deployment. But, with these
>> two devices autonomic hot standby or backup each other, should the whole
>> network be called an autonomic network? If you think "network-wide" is a
>> too high threshold for autonomic network, we can work out some lower
>> description.
>
>Indeed, many people will probably imply that what we call an "autonomic
>network" is actually what we define as a "fully autonomic network".
>Maybe the better phrase would be "partially autonomic network".

This sounds better for me.

>But, no doubt we'll have more discussions around this at the IETF. I suggest to
>leave it for now, discuss at NMRG how people feel we should call it. OK?

That's ok, for sure. :)

Sheng

>Michael
>
>> Sheng
>> _______________________________________________
>> Anima mailing list
>> Anima@ietf.org
>> https://www.ietf.org/mailman/listinfo/anima