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

Sheng Jiang <jiangsheng@huawei.com> Fri, 27 June 2014 07:42 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 9DAA61B3173 for <nmrg@ietfa.amsl.com>; Fri, 27 Jun 2014 00:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.242
X-Spam-Level:
X-Spam-Status: No, score=-3.242 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, T_FSL_HELO_BARE_IP_2=0.01] 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 evFC6qu22vox for <nmrg@ietfa.amsl.com>; Fri, 27 Jun 2014 00:42:35 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4E471B3129 for <nmrg@irtf.org>; Fri, 27 Jun 2014 00:42:33 -0700 (PDT)
Received: from 172.24.2.119 (EHLO 172.24.1.48) ([172.24.2.119]) by szxrg03-dlp.huawei.com (MOS 4.4.3-GA FastPath queued) with ESMTP id AQW45101; Fri, 27 Jun 2014 15:40:26 +0800 (CST)
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.249]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Fri, 27 Jun 2014 15:38:59 +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: Updating draft-irtf-nmrg-autonomic-network-definitions-00
Thread-Index: Ac+Ps8dVKhhDDzh8R4WTmNCrIuSMYgAmu8DAADYwkFAAHyjQkAAMNiqAAAEyf8A=
Date: Fri, 27 Jun 2014 07:38:58 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AEC1488@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>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF21BD33ED@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
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020208.53AD1FEB.008B,ss=1,re=0.000,fgs=0, ip=169.254.7.249, so=2013-05-26 15:14:31, dmn=2011-05-27 18:58:46
X-Mirapoint-Loop-Id: f638cdad9f32c514b8f697783744f699
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/ggq8sUE3GV9Gdr_ebyXZADi74ZY
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:42:36 -0000

>> >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?

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.

Sheng