Re: [nmrg] Autonomic Use Cases

Sheng Jiang <jiangsheng@huawei.com> Tue, 11 March 2014 07:04 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 0CE811A0696 for <nmrg@ietfa.amsl.com>; Tue, 11 Mar 2014 00:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level:
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] 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 rt4SZeoigWk6 for <nmrg@ietfa.amsl.com>; Tue, 11 Mar 2014 00:03:56 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by ietfa.amsl.com (Postfix) with ESMTP id 9FBEE1A03C8 for <nmrg@irtf.org>; Tue, 11 Mar 2014 00:03:55 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQX00932; Tue, 11 Mar 2014 14:57:22 +0800 (CST)
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml208-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 11 Mar 2014 14:57:20 +0800
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by szxeml405-hub.china.huawei.com (10.82.67.60) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 11 Mar 2014 14:57:21 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Tue, 11 Mar 2014 14:57:19 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Joe Marcus Clarke <jclarke@cisco.com>, "Michael Behringer (mbehring)" <mbehring@cisco.com>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: [nmrg] Autonomic Use Cases
Thread-Index: Ac86X5T6lfxN1wJKTHant9hA7a0vlgAcl9sAAIi429A=
Date: Tue, 11 Mar 2014 06:57:18 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE26012@nkgeml512-mbx.china.huawei.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.com> <531B8AEC.9050501@cisco.com>
In-Reply-To: <531B8AEC.9050501@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/e2BKuhM7Gl-c0WkydfWvQQYohpg
Subject: Re: [nmrg] Autonomic Use Cases
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, 11 Mar 2014 07:04:01 -0000

>>        <section title="Common Autonomic Networking Infrastructure">
>> 	<t><xref target="I-D.irtf-nmrg-an-gap-analysis"/> points out that there
>are already a number of fully or partially autonomic functions available today.
>However, they are largely independent, and each has its own methods and
>protocols to communicate, discover, define and distribute policy, etc. </t>
>> 	<t>The goal of the work on autonomic networking in the IETF is
>therefore not just to create autonomic functions, but to define a common
>infrastructure that autonomic functions can use. This autonomic networking
>infrastructure may contain common control and management functions such
>as messaging, service discovery, negotiation, intent distribution, etc. A
>common approach to define and manage intent is also required. </t>
>
>Is this IETF or IRTF?  I know the goal is to eventually move into the
>IETF, but what do you intend here?

The autonomic network work in IRTF and IETF are relevant to each other. The ideal is we have high-level definitions, design goals, requirements and gap analysis in IRTF. For any concrete protocol work, that supports common autonomic network infrastructure, such as negotiation protocol, should be hold in IETF.

Ideally, we would have several autonomic network use cases that are based on the same common control and management functions. Then we can work on these common control and management functions in IETF, while each of use cases may have its own instance on top of the common infrastructure.

Best regards,

Sheng