
From nobody Tue Mar  4 10:08:19 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 6CE551A01DD for <nmrg@ietfa.amsl.com>; Tue,  4 Mar 2014 10:08:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.547] 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 pxTJ9cGLkv5c for <nmrg@ietfa.amsl.com>; Tue,  4 Mar 2014 10:08:02 -0800 (PST)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) by ietfa.amsl.com (Postfix) with ESMTP id 03B641A0187 for <nmrg@irtf.org>; Tue,  4 Mar 2014 10:08:02 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 50067137B; Tue,  4 Mar 2014 19:07:58 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id p4Di5sGMe8hH; Tue,  4 Mar 2014 19:07:57 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by atlas3.jacobs-university.de (Postfix) with ESMTP; Tue,  4 Mar 2014 19:07:57 +0100 (CET)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7D6E420033; Tue,  4 Mar 2014 19:07:57 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 4T5KaMWHw0Zp; Tue,  4 Mar 2014 19:07:56 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 26BFD2002C; Tue,  4 Mar 2014 19:07:55 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 368C12B93615; Tue,  4 Mar 2014 19:07:54 +0100 (CET)
Date: Tue, 4 Mar 2014 19:07:54 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>
Message-ID: <20140304180754.GA28061@elstar.local>
Mail-Followup-To: Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>, nmrg@irtf.org
References: <8D63CBC0-7EC6-4304-8203-BEB53FD83033@inf.ufrgs.br>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8D63CBC0-7EC6-4304-8203-BEB53FD83033@inf.ufrgs.br>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/5rH8ddt6cVh8v-NffqQ7HSq5JN4
Cc: nmrg@irtf.org
Subject: Re: [nmrg] 33rd NMRG meeting - Call for Contributions
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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, 04 Mar 2014 18:08:09 -0000

On Tue, Jan 28, 2014 at 06:46:06PM -0200, Lisandro Zambenedetti Granville wrote:
> 
>                   CALL FOR CONTRIBUTIONS
>  
>       Autonomics for Network Management – Part II
>  
>   33rd Network Management Research Group (NMRG) meeting
>         IETF 89 - March 2-7, 2014 - London, England
> 

Hi,

I see that an NMRG meeting is scheduled for tomorrow (March 6th) but I
can't find an agenda - neither on the IETF agenda pages nor have I
seen one posted to the mailing list.

Does someone know what is expected to happen tomorrow during the
meeting?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Tue Mar  4 10:27:12 2014
Return-Path: <granville@inf.ufrgs.br>
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 D13841A028F for <nmrg@ietfa.amsl.com>; Tue,  4 Mar 2014 10:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=no
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 bm-ix0oEZCPr for <nmrg@ietfa.amsl.com>; Tue,  4 Mar 2014 10:27:08 -0800 (PST)
Received: from puma.inf.ufrgs.br (puma.inf.ufrgs.br [143.54.11.5]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2111A0002 for <nmrg@irtf.org>; Tue,  4 Mar 2014 10:27:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by puma.inf.ufrgs.br (Postfix) with ESMTP id 409F261CFE; Tue,  4 Mar 2014 15:27:18 -0300 (BRT)
Received: from [10.84.13.92] (unknown [85.255.235.241]) by puma.inf.ufrgs.br (Postfix) with ESMTP id D0B8261CCF; Tue,  4 Mar 2014 15:27:16 -0300 (BRT)
References: <8D63CBC0-7EC6-4304-8203-BEB53FD83033@inf.ufrgs.br> <20140304180754.GA28061@elstar.local>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20140304180754.GA28061@elstar.local>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <5836042B-82AA-4396-AD51-14405D550E5D@inf.ufrgs.br>
X-Mailer: iPhone Mail (11B651)
From: Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>
Date: Tue, 4 Mar 2014 18:26:56 +0000
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/UYGDjduk_UFXy2Xj2Y1IduCblE4
Cc: "nmrg@irtf.org" <nmrg@irtf.org>
Subject: Re: [nmrg] 33rd NMRG meeting - Call for Contributions
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, 04 Mar 2014 18:27:11 -0000

Hi Juergen

The NMRG meeting will be on Thursday. We are just waiting the confirmation o=
f a presentation title to advertise the program.=20

Best regards

Lisandro


Enviado via iPhone

> Em 04/03/2014, =C3=A0s 18:07, Juergen Schoenwaelder <j.schoenwaelder@jacob=
s-university.de> escreveu:
>=20
>> On Tue, Jan 28, 2014 at 06:46:06PM -0200, Lisandro Zambenedetti Granville=
 wrote:
>>=20
>>                  CALL FOR CONTRIBUTIONS
>>=20
>>      Autonomics for Network Management =E2=80=93 Part II
>>=20
>>  33rd Network Management Research Group (NMRG) meeting
>>        IETF 89 - March 2-7, 2014 - London, England
>=20
> Hi,
>=20
> I see that an NMRG meeting is scheduled for tomorrow (March 6th) but I
> can't find an agenda - neither on the IETF agenda pages nor have I
> seen one posted to the mailing list.
>=20
> Does someone know what is expected to happen tomorrow during the
> meeting?
>=20
> /js
>=20
> --=20
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Tue Mar  4 10:36:45 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 D70DE1A02C4 for <nmrg@ietfa.amsl.com>; Tue,  4 Mar 2014 10:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.547] 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 f-OafzeaEG25 for <nmrg@ietfa.amsl.com>; Tue,  4 Mar 2014 10:36:35 -0800 (PST)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3FF1A0262 for <nmrg@irtf.org>; Tue,  4 Mar 2014 10:36:35 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 91824139C; Tue,  4 Mar 2014 19:36:29 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id pA7x3dFztpwc; Tue,  4 Mar 2014 19:36:28 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by atlas3.jacobs-university.de (Postfix) with ESMTP; Tue,  4 Mar 2014 19:36:28 +0100 (CET)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 954412002F; Tue,  4 Mar 2014 19:36:28 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 5Pb01hoojhuy; Tue,  4 Mar 2014 19:36:27 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3CBFF2002C; Tue,  4 Mar 2014 19:36:26 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id C126F2B9383E; Tue,  4 Mar 2014 19:36:25 +0100 (CET)
Date: Tue, 4 Mar 2014 19:36:25 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>
Message-ID: <20140304183625.GA28225@elstar.local>
Mail-Followup-To: Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>, "nmrg@irtf.org" <nmrg@irtf.org>
References: <8D63CBC0-7EC6-4304-8203-BEB53FD83033@inf.ufrgs.br> <20140304180754.GA28061@elstar.local> <5836042B-82AA-4396-AD51-14405D550E5D@inf.ufrgs.br>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5836042B-82AA-4396-AD51-14405D550E5D@inf.ufrgs.br>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/uDYfCD94FUDzc887BIENfxuu4ew
Cc: "nmrg@irtf.org" <nmrg@irtf.org>
Subject: Re: [nmrg] 33rd NMRG meeting - Call for Contributions
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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, 04 Mar 2014 18:36:41 -0000

On Tue, Mar 04, 2014 at 06:26:56PM +0000, Lisandro Zambenedetti Granville wrote:
> Hi Juergen
> 
> The NMRG meeting will be on Thursday. We are just waiting the confirmation of a presentation title to advertise the program. 
> 

Sorry for confusing the date. But since we all have to manage our
personal agendas during IETF weeks well, it would be really nice to
have an agenda well ahead of the meeting.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Tue Mar  4 12:23:23 2014
Return-Path: <granville@inf.ufrgs.br>
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 2FE7D1A02EE for <nmrg@ietfa.amsl.com>; Tue,  4 Mar 2014 12:23:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=no
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 a5tDBLaW_ACo for <nmrg@ietfa.amsl.com>; Tue,  4 Mar 2014 12:23:16 -0800 (PST)
Received: from puma.inf.ufrgs.br (puma.inf.ufrgs.br [143.54.11.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3A51A02D2 for <nmrg@irtf.org>; Tue,  4 Mar 2014 12:23:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by puma.inf.ufrgs.br (Postfix) with ESMTP id 8C85161D3B for <nmrg@irtf.org>; Tue,  4 Mar 2014 17:23:19 -0300 (BRT)
Received: from dhcp-hotel-wifi-158-11.meeting.ietf.org (unknown [130.129.158.17]) by puma.inf.ufrgs.br (Postfix) with ESMTP id 2223261D33 for <nmrg@irtf.org>; Tue,  4 Mar 2014 17:23:16 -0300 (BRT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>
In-Reply-To: <20140304180754.GA28061@elstar.local>
Date: Tue, 4 Mar 2014 20:23:00 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <45207723-32AC-4CAC-A1D2-2857DD7ED204@inf.ufrgs.br>
References: <8D63CBC0-7EC6-4304-8203-BEB53FD83033@inf.ufrgs.br> <20140304180754.GA28061@elstar.local>
To: nmrg@irtf.org
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/H6_V_5bJXx5fORAMZXt1YYtOy7k
Subject: Re: [nmrg] 33rd NMRG meeting - Call for Contributions
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, 04 Mar 2014 20:23:17 -0000

Dear all

We=92ve just posted the program of the 33rd NMRG meeting in the IETF 89 =
material page. The 33rd NMRG meeting is organized as follows:

33rd Network Management Research Group (NMRG) meeting
IETF 89
March 6th 2014 - London, UK


13:00 - 15:00 : Thursday Afternoon Session I - Richmond/Chelsea/Tower
--------------------------------------------------

13:00 - 13:05 : Agenda Bashing

13:05 - 13:30 : Proactive self-healing mechanisms for IP networks - =
Laurent Ciavaglia

13:30 - 14:00 : Autonomic Network Definitions - Michael Behringer, Brian =
Carpenter, Sheng Jiang

14:00 - 14:30 : Gap Analysis for Autonomous Networking - Michael =
Behringer, Brian Carpenter, Sheng Jiang

14:30 - 15:00 : Discussion


We will probably count with a presentation of Dimitri Papadimitriou, to =
be confirmed.

Best regards,

Lisandro and Olivier

Em 04/03/2014, =E0(s) 18:07, Juergen Schoenwaelder =
<j.schoenwaelder@jacobs-university.de> escreveu:

> On Tue, Jan 28, 2014 at 06:46:06PM -0200, Lisandro Zambenedetti =
Granville wrote:
>>=20
>>                  CALL FOR CONTRIBUTIONS
>>=20
>>      Autonomics for Network Management =96 Part II
>>=20
>>  33rd Network Management Research Group (NMRG) meeting
>>        IETF 89 - March 2-7, 2014 - London, England
>>=20
>=20
> Hi,
>=20
> I see that an NMRG meeting is scheduled for tomorrow (March 6th) but I
> can't find an agenda - neither on the IETF agenda pages nor have I
> seen one posted to the mailing list.
>=20
> Does someone know what is expected to happen tomorrow during the
> meeting?
>=20
> /js
>=20
> --=20
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Thu Mar  6 07:55:57 2014
Return-Path: <jclarke@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 66BF01A00AE for <nmrg@ietfa.amsl.com>; Thu,  6 Mar 2014 07:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 23fO7Q76qB24 for <nmrg@ietfa.amsl.com>; Thu,  6 Mar 2014 07:55:52 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 96F581A013E for <nmrg@irtf.org>; Thu,  6 Mar 2014 07:55:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1171; q=dns/txt; s=iport; t=1394121349; x=1395330949; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=2meFDWCQNt21M3uV/P8UdUey3/BSDo7c+rg6RqMwHB0=; b=Rap4VtoL2dPhkY9j3Buem9/DaGBnwuoc0zoiKoUAGriorgwrymfdWqtS 0J8QNKf84f8yyarpJaJoW6JzPyvUJHlnhBOZ03DHA9f5/Y3ohwhZ2nxsT /zDzvyG+/+ii3s7HsayrET4ignee2n/aDZy3wNvMbvLs9gjqxPx4fWnYO w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAOmZGFOQ/khN/2dsb2JhbABagwbDSRZ0gmR9NAJZCAEBh3WfJ7AOF454hCIEiUyOcoZKi2GDSx4
X-IronPort-AV: E=Sophos;i="4.97,601,1389744000";  d="scan'208";a="7461991"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-1.cisco.com with ESMTP; 06 Mar 2014 15:55:48 +0000
Received: from [10.82.247.40] (rtp-vpn2-1829.cisco.com [10.82.247.40]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s26Ftk20022891 for <nmrg@irtf.org>; Thu, 6 Mar 2014 15:55:47 GMT
Message-ID: <53189A82.80404@cisco.com>
Date: Thu, 06 Mar 2014 10:55:46 -0500
From: Joe Marcus Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: nmrg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/sRl076KwPwyH4KX_A2nz71FClgY
Subject: [nmrg] Comments on 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: Thu, 06 Mar 2014 15:55:54 -0000

After listening to the talks today, I have an overall comment related to 
network traceability in an autonomic environment.  I was very intrigued 
by Laurent's talk as I have been doing work in this area using Cisco 
embedded automation.  I strongly feel that we should be doing more 
autonomic cross-device analysis of problem conditions to do smart 
rerouting in the case of instability.  For example, in addition to local 
factors like temperature and load, we could look at path or hop 
stability in terms of dropped packets along a flow, jitter, latency, 
etc. and determine a new optimum/stable path.

Additionally, with respect to the troubleshooting section in 
draft-jiang-nmrg-an-gap-analysis-00, I think there is something that can 
be done autonomically relating to hardware failure.  Given Laurent's 
ideas again, a device that can detect imminent failure (e.g., SMART-like 
operations on harddrives), and make proactive changes to the network to 
reroute around an impending hardware failure until humans can get 
involved.  This can prevent extended outages.  Perhaps this is something 
that could supplement this section of text.

Joe


From nobody Fri Mar  7 02:02:16 2014
Return-Path: <brian.e.carpenter@gmail.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 917A71A02B3 for <nmrg@ietfa.amsl.com>; Fri,  7 Mar 2014 02:02:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 0YrWm5noQRb4 for <nmrg@ietfa.amsl.com>; Fri,  7 Mar 2014 02:02:13 -0800 (PST)
Received: from mail-bk0-x22c.google.com (mail-bk0-x22c.google.com [IPv6:2a00:1450:4008:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id A65E81A0164 for <nmrg@irtf.org>; Fri,  7 Mar 2014 02:02:12 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id mz13so870283bkb.3 for <nmrg@irtf.org>; Fri, 07 Mar 2014 02:02:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rukhEctuf0kYkidEy964DH/IRfDWA0Tql9DPxr1LmpA=; b=FwlOj4SuPyRQZHA+jn/DNQzOaTg33QvV6r2cWBGE0bbD2e8CUJFUsvRGoncxhhmSwo KeMnNDSuudfXNtg8PColOQEN5Zl9YYAqIX7r9s36gTb+qDYtc0HAha6j5GWdMmwlU/PL PGZlJI4mqRXpUDaakan0bum0yu0xvIJULqbClbV6YW7x7xJKEu4a/PYE0trKSbutuFXT JqfKJ1FwbGWWOD0rMNqutNOs7tHYmSsBPbY4UE2NMulhrd4BLB2btiCxXH1ODSgei4r0 D3SPKV/H89yGnH/rRUIaJ8q+dUD0odF20w3X3JAUOxDj98azfZC7lwcfhFVaU4OZ4tGe dO7A==
X-Received: by 10.204.94.199 with SMTP id a7mr1780939bkn.25.1394186527917; Fri, 07 Mar 2014 02:02:07 -0800 (PST)
Received: from [31.133.165.224] (dhcp-a5e0.meeting.ietf.org. [31.133.165.224]) by mx.google.com with ESMTPSA id f11sm1689544bkj.6.2014.03.07.02.02.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Mar 2014 02:02:07 -0800 (PST)
Message-ID: <53199927.1090707@gmail.com>
Date: Fri, 07 Mar 2014 23:02:15 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joe Marcus Clarke <jclarke@cisco.com>
References: <53189A82.80404@cisco.com>
In-Reply-To: <53189A82.80404@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/MLpLRSK33bkMdmElizKn3gViOio
Cc: nmrg@irtf.org
Subject: Re: [nmrg] Comments on 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: Fri, 07 Mar 2014 10:02:14 -0000

Hi Joe,

On 07/03/2014 04:55, Joe Marcus Clarke wrote:
> After listening to the talks today, I have an overall comment related to
> network traceability in an autonomic environment.  I was very intrigued
> by Laurent's talk as I have been doing work in this area using Cisco
> embedded automation.  I strongly feel that we should be doing more
> autonomic cross-device analysis of problem conditions to do smart
> rerouting in the case of instability.  

Yes; and not just instability. Other conditions like impending overload
could trigger action. (Always with appropriate damping to prevent
oscillation, of course.)

> For example, in addition to local
> factors like temperature and load, we could look at path or hop
> stability in terms of dropped packets along a flow, jitter, latency,
> etc. and determine a new optimum/stable path.
> 
> Additionally, with respect to the troubleshooting section in
> draft-jiang-nmrg-an-gap-analysis-00, I think there is something that can
> be done autonomically relating to hardware failure.  Given Laurent's
> ideas again, a device that can detect imminent failure (e.g., SMART-like
> operations on harddrives), and make proactive changes to the network to
> reroute around an impending hardware failure until humans can get
> involved.  This can prevent extended outages.  Perhaps this is something
> that could supplement this section of text.

Thanks, yes. This is a case where more than one device may be involved
(which is why we're arguing that an east-west negotiation between devices
is needed).

     Brian


From nobody Fri Mar  7 15:47:31 2014
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 1C8131A020D for <nmrg@ietfa.amsl.com>; Fri,  7 Mar 2014 15:47:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 y7A4nFwdbVgD for <nmrg@ietfa.amsl.com>; Fri,  7 Mar 2014 15:47:28 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA291A01C0 for <nmrg@irtf.org>; Fri,  7 Mar 2014 15:47:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3354; q=dns/txt; s=iport; t=1394236044; x=1395445644; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=l2Lx6iOG+JSivEKWDQo4jRizz5d5ondoSrn3G8q+XEU=; b=W6MtM2OrrPzYBxbauavwNQjZE98MFuzSAzA7G7xxOfZ+HFpFu30rQFu1 Vcq1Wxn1XXh1WuHYoZ95M9pyVJ5yQVzMcC6IXHnLYJsdnxUeOa071Imv6 td0qpnD3aj13FILtEr7VD6lWFaShblm9CDzSrarxPhp/KT+qBczZsPySq Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFABRZGlOtJV2c/2dsb2JhbABagwaBEsEvgRQWdIInAQQ6UQEqFEImAQQbE4den1ewQBeOKoNcgRQEqm6DLYIr
X-IronPort-AV: E=Sophos;i="4.97,610,1389744000"; d="scan'208";a="25831904"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-5.cisco.com with ESMTP; 07 Mar 2014 23:47:23 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s27NlN42020698 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <nmrg@irtf.org>; Fri, 7 Mar 2014 23:47:23 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.171]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0123.003; Fri, 7 Mar 2014 17:47:23 -0600
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: Autonomic Use Cases
Thread-Index: Ac86X5T6lfxN1wJKTHant9hA7a0vlg==
Date: Fri, 7 Mar 2014 23:47:22 +0000
Message-ID: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.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.131]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/JZekH9XNE2fsMX7jaYK3Fyj_OKY
Subject: [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: Fri, 07 Mar 2014 23:47:30 -0000

NMRG,=20

During the meeting we mentioned the need to document use cases. This sectio=
n in the definitions draft is so far empty. Since we should have that secti=
on BEFORE working out the use cases, I drafted something up here.=20

I also realised that while we haven't really written down in the draft that=
 the key point of this work really is to work out common infrastructure req=
uirements. So I'm also suggesting an additional short section in the Design=
 Goals section:=20

      <section title=3D"Common Autonomic Networking Infrastructure">
	<t><xref target=3D"I-D.irtf-nmrg-an-gap-analysis"/> points out that there =
are already a number of fully or partially autonomic functions available to=
day. However, they are largely independent, and each has its own methods an=
d protocols to communicate, discover, define and distribute policy, etc. </=
t>
	<t>The goal of the work on autonomic networking in the IETF is therefore n=
ot just to create autonomic functions, but to define a common infrastructur=
e that autonomic functions can use. This autonomic networking infrastructur=
e may contain common control and management functions such as messaging, se=
rvice discovery, negotiation, intent distribution, etc. A common approach t=
o define and manage intent is also required. </t>
	<t>Refer to the reference model below: All the components around the "auto=
nomic service agents" should be common components, such that the autonomic =
service agents do not have to replicate common tasks individually. </t>
      </section>

Comments? Does this capture the idea well?=20

And then, the use case section could look like this:=20

      <section title=3D"Guidelines for Case Studies">
	<t>Case studies and problem statements are mandatory to understand common =
requirements for autonomic functions. This section explains how case studie=
s should be outlined and what they should describe:
        <list style=3D"symbols">
	  <t>Title</t>
	  <t>Problem Statement: An explanation which problem is being addressed, w=
ith information about existing solutions and their shortcomings.</t>
	  <t>Intended user / administrator experience: The goal of autonomic netwo=
rking is to simplify network administration and usage. Use cases should poi=
nt out how their experience differs from current solutions. If a use case d=
epends on configuration, it may include configuration samples, although obv=
iously the goal is to reduce or eliminate configuration. </t>
	  <t>Intent: Strictly speaking intent is part of the administrator experie=
nce, but should probably explained explicitly with a high-level view on how=
 the autonomic function could be defined in intent (if required). </t>
	  <t>Local knowledge: What the function needs to know about the capabiliti=
es of the node itself, and which local resources need to be accessed.</t>
	  <t>Communication requirements: The requirements for message exchange, di=
scovery, negotiation, etc with other autonomic nodes. </t>
        </list>
	</t>
	<t>Use cases are not required to outline a solution in detail, nor to spec=
ify precise protocol or intent details. They are used at this point to dete=
rmine a consolidated approach to developping an autonomic networking infras=
tructure. </t>
      </section>

Comments?=20
Michael


From nobody Sat Mar  8 06:03:47 2014
Return-Path: <dimitri.papadimitriou@alcatel-lucent.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 5F6201A0159 for <nmrg@ietfa.amsl.com>; Sat,  8 Mar 2014 06:03:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-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 fGIkOE31hZPK for <nmrg@ietfa.amsl.com>; Sat,  8 Mar 2014 06:03:44 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 605701A00FC for <nmrg@irtf.org>; Sat,  8 Mar 2014 06:03:43 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s28E3buR027067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 8 Mar 2014 08:03:38 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s28E3ZWD027808 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 8 Mar 2014 15:03:35 +0100
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.10]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Sat, 8 Mar 2014 15:03:35 +0100
From: "Papadimitriou, Dimitri (Dimitri)" <dimitri.papadimitriou@alcatel-lucent.com>
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: Autonomic Use Cases
Thread-Index: Ac86X5T6lfxN1wJKTHant9hA7a0vlgAXSsnA
Date: Sat, 8 Mar 2014 14:03:34 +0000
Message-ID: <84675BAA8C49154AB81E2587BE8BDF8308B4AC52@FR711WXCHMBA07.zeu.alcatel-lucent.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/DMnDi4VHCh7E9abEUou9k0-CnQk
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: Sat, 08 Mar 2014 14:03:46 -0000

Hi Michael,

I certainly share this goal.=20

Reading throughout the intro, OSPF currently provides adaptive routing (wit=
hin the setting for which they have been configured, information exchanged =
with other OSPF routers, etc.), a main goal that requires also further word=
ing is the augmentation of their capability by means of predictive (and not=
 only reactive) re-parametrization that couldn't be diagnosed by OSPF alone=
, information element not exchanged by the OSPF protocol itself, and proced=
ures not currently part of its algorithmic. This example can be generalized=
 to other protocols and processes but bare with me, the ultimate goal of au=
tonomics is indeed to provide network-wide (so-called) intelligence to node=
s while minimizing functional and informational dependence on centralized m=
anagement or control systems.=20

Hence, the focus of this design goal should be on autonomic (distributed) c=
ontrol plane elements.

Thanks,
-dimitri.

> -----Original Message-----
> From: nmrg [mailto:nmrg-bounces@irtf.org] On Behalf Of Michael Behringer
> (mbehring)
> Sent: Saturday, March 08, 2014 00:47
> To: nmrg@irtf.org
> Subject: [nmrg] Autonomic Use Cases
>=20
> NMRG,
>=20
> During the meeting we mentioned the need to document use cases. This
> section in the definitions draft is so far empty. Since we should have
> that section BEFORE working out the use cases, I drafted something up
> here.
>=20
> I also realised that while we haven't really written down in the draft
> that the key point of this work really is to work out common
> infrastructure requirements. So I'm also suggesting an additional short
> section in the Design Goals section:
>=20
>       <section title=3D"Common Autonomic Networking Infrastructure">
> 	<t><xref target=3D"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 networkin=
g
> infrastructure may contain common control and management functions such a=
s
> messaging, service discovery, negotiation, intent distribution, etc. A
> common approach to define and manage intent is also required. </t>
> 	<t>Refer to the reference model below: All the components around the
> "autonomic service agents" should be common components, such that the
> autonomic service agents do not have to replicate common tasks
> individually. </t>
>       </section>
>=20
> Comments? Does this capture the idea well?
>=20
> And then, the use case section could look like this:
>=20
>       <section title=3D"Guidelines for Case Studies">
> 	<t>Case studies and problem statements are mandatory to understand
> common requirements for autonomic functions. This section explains how
> case studies should be outlined and what they should describe:
>         <list style=3D"symbols">
> 	  <t>Title</t>
> 	  <t>Problem Statement: An explanation which problem is being
> addressed, with information about existing solutions and their
> shortcomings.</t>
> 	  <t>Intended user / administrator experience: The goal of autonomic
> networking is to simplify network administration and usage. Use cases
> should point out how their experience differs from current solutions. If =
a
> use case depends on configuration, it may include configuration samples,
> although obviously the goal is to reduce or eliminate configuration. </t>
> 	  <t>Intent: Strictly speaking intent is part of the administrator
> experience, but should probably explained explicitly with a high-level
> view on how the autonomic function could be defined in intent (if
> required). </t>
> 	  <t>Local knowledge: What the function needs to know about the
> capabilities of the node itself, and which local resources need to be
> accessed.</t>
> 	  <t>Communication requirements: The requirements for message
> exchange, discovery, negotiation, etc with other autonomic nodes. </t>
>         </list>
> 	</t>
> 	<t>Use cases are not required to outline a solution in detail, nor
> to specify precise protocol or intent details. They are used at this poin=
t
> to determine a consolidated approach to developping an autonomic
> networking infrastructure. </t>
>       </section>
>=20
> Comments?
> Michael
>=20
> _______________________________________________
> nmrg mailing list
> nmrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nmrg


From nobody Sat Mar  8 13:26:15 2014
Return-Path: <jclarke@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 CDD161A02DB for <nmrg@ietfa.amsl.com>; Sat,  8 Mar 2014 13:26:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 z4sRvQ7V3EUA for <nmrg@ietfa.amsl.com>; Sat,  8 Mar 2014 13:26:10 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6FFEB1A02F2 for <nmrg@irtf.org>; Sat,  8 Mar 2014 13:26:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4057; q=dns/txt; s=iport; t=1394313966; x=1395523566; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=fW8FXBCbwnzQ9ejoDA2jZR/YactrpheIoNMAPpyqkVI=; b=Ykhz+ipj9ynJt1FIyVwJRTOIf3KYYzTcCDYEko2dt/m5NsicYLpi4dPc XUJ3X9Ggquuj4cIPVHdBIS685+GOWh85VXrBmXtJ529KEBzCktkN/SwKy V8A/T567ToBu0YCXPmjq4m+AYiYCYHpKWWRQRsJgOdfJvGorm03OC2fe1 Y=;
X-IronPort-AV: E=Sophos;i="4.97,615,1389744000";  d="scan'208";a="7188042"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 08 Mar 2014 21:26:05 +0000
Received: from [10.117.46.171] (rtp-jclarke-89110.cisco.com [10.117.46.171]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s28LQ4CU001774; Sat, 8 Mar 2014 21:26:04 GMT
Message-ID: <531B8AEC.9050501@cisco.com>
Date: Sat, 08 Mar 2014 16:26:04 -0500
From: Joe Marcus Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, "nmrg@irtf.org" <nmrg@irtf.org>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@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/RGol2a93AekaiPa1iKjoakd9K64
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: Sat, 08 Mar 2014 21:26:13 -0000

On 3/7/14, 6:47 PM, Michael Behringer (mbehring) wrote:
> NMRG,
>
> During the meeting we mentioned the need to document use cases. This section in the definitions draft is so far empty. Since we should have that section BEFORE working out the use cases, I drafted something up here.
>
> I also realised that while we haven't really written down in the draft that the key point of this work really is to work out common infrastructure requirements. So I'm also suggesting an additional short section in the Design Goals section:
>
>        <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?

> 	<t>Refer to the reference model below: All the components around the "autonomic service agents" should be common components, such that the autonomic service agents do not have to replicate common tasks individually. </t>
>        </section>
>
> Comments? Does this capture the idea well?

I think so.  I like the idea of moving beyond atomic autonomic functions 
into more of an autonomic system.  One key aspect of this system is 
self-monitoring and diagnostics (think regulation).  The idea of probes, 
sentinels, etc. play into this, and I think it should be called out in 
the list.

>
> And then, the use case section could look like this:
>
>        <section title="Guidelines for Case Studies">
> 	<t>Case studies and problem statements are mandatory to understand common requirements for autonomic functions. This section explains how case studies should be outlined and what they should describe:
>          <list style="symbols">
> 	  <t>Title</t>
> 	  <t>Problem Statement: An explanation which problem is being addressed, with information about existing solutions and their shortcomings.</t>

Nit: OF which problem is being...

> 	  <t>Intended user / administrator experience: The goal of autonomic networking is to simplify network administration and usage. Use cases should point out how their experience differs from current solutions. If a use case depends on configuration, it may include configuration samples, although obviously the goal is to reduce or eliminate configuration. </t>
> 	  <t>Intent: Strictly speaking intent is part of the administrator experience, but should probably explained explicitly with a high-level view on how the autonomic function could be defined in intent (if required). </t>

Nit: probably BE explained...

> 	  <t>Local knowledge: What the function needs to know about the capabilities of the node itself, and which local resources need to be accessed.</t>
> 	  <t>Communication requirements: The requirements for message exchange, discovery, negotiation, etc with other autonomic nodes. </t>
>          </list>
> 	</t>
> 	<t>Use cases are not required to outline a solution in detail, nor to specify precise protocol or intent details. They are used at this point to determine a consolidated approach to developping an autonomic networking infrastructure. </t>

Nit: DEVELOPING (typo)

>        </section>
>
> Comments?

I think this is a good set of high-level guidelines.  Is there a need 
for remote knowledge as well?  That is, what if a node needs to know 
topology to make the right choice?

Joe


From nobody Mon Mar 10 08:16:23 2014
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 AE53B1A0496 for <nmrg@ietfa.amsl.com>; Mon, 10 Mar 2014 08:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level: 
X-Spam-Status: No, score=-15.048 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.547, 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 1hI2wj9V40cf for <nmrg@ietfa.amsl.com>; Mon, 10 Mar 2014 08:16:08 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8CB1A0233 for <nmrg@irtf.org>; Mon, 10 Mar 2014 08:16:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1854; q=dns/txt; s=iport; t=1394464563; x=1395674163; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=4qdv7rU64r8sy3NMf1kTCbFvAh/lez7MJ6YEuNbGtSU=; b=dB4lKH3jABEJcRdfk/WDjLW85oGYpKQ+bMmSLg8vP9Wppq7JXOYXeApt 65pFd344OiMZEJx8Jw3jFMxMMgzjX8x8HVdxIwZaiWZui02ctMUclkLWx u77tLS3opVfXdt5Oocdoe7ufbyu4R1SQpziS5okFZ+IcBptbhwNc1QsFR A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAPDWHVOtJXG8/2dsb2JhbABagwY7V8E8gRsWdIIlAQEBBAEBATc0FwQCAQgRBAEBCxQJBycLFAkIAgQBEgiHcQ3PRBMEjF+BSzgGgx6BFASqcoMtgis
X-IronPort-AV: E=Sophos;i="4.97,624,1389744000"; d="scan'208";a="309048637"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 10 Mar 2014 15:15:59 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s2AFFxET011757 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <nmrg@irtf.org>; Mon, 10 Mar 2014 15:15:59 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.171]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Mon, 10 Mar 2014 10:15:58 -0500
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: [nmrg] Comments on autonomic use cases
Thread-Index: AQHPOVSVhQgY0FPTw0WzVDfxysZ0XJraG7Ag
Date: Mon, 10 Mar 2014 15:15:58 +0000
Message-ID: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9B08BB@xmb-rcd-x14.cisco.com>
References: <53189A82.80404@cisco.com>
In-Reply-To: <53189A82.80404@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.148.163.59]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/EMBqN18wzGQITnb3TVQiqPDWmyk
Subject: Re: [nmrg] Comments on 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: Mon, 10 Mar 2014 15:16:18 -0000

Joe,=20

I like your ideas. Why don't you write them up, either as a standalone use =
case, or with Laurent? It would be interesting to see a concrete example of=
 such an autonomic behaviour, and deduce which type of interactions would b=
e required.=20

Michael

> -----Original Message-----
> From: nmrg [mailto:nmrg-bounces@irtf.org] On Behalf Of Joe Clarke
> (jclarke)
> Sent: 06 March 2014 16:56
> To: nmrg@irtf.org
> Subject: [nmrg] Comments on autonomic use cases
>=20
> After listening to the talks today, I have an overall comment related to
> network traceability in an autonomic environment.  I was very intrigued b=
y
> Laurent's talk as I have been doing work in this area using Cisco embedde=
d
> automation.  I strongly feel that we should be doing more autonomic cross=
-
> device analysis of problem conditions to do smart rerouting in the case o=
f
> instability.  For example, in addition to local factors like temperature =
and
> load, we could look at path or hop stability in terms of dropped packets
> along a flow, jitter, latency, etc. and determine a new optimum/stable pa=
th.
>=20
> Additionally, with respect to the troubleshooting section in draft-jiang-
> nmrg-an-gap-analysis-00, I think there is something that can be done
> autonomically relating to hardware failure.  Given Laurent's ideas again,=
 a
> device that can detect imminent failure (e.g., SMART-like operations on
> harddrives), and make proactive changes to the network to reroute around
> an impending hardware failure until humans can get involved.  This can
> prevent extended outages.  Perhaps this is something that could
> supplement this section of text.
>=20
> Joe
>=20
> _______________________________________________
> nmrg mailing list
> nmrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nmrg


From nobody Mon Mar 10 08:17:09 2014
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 0272B1A0496 for <nmrg@ietfa.amsl.com>; Mon, 10 Mar 2014 08:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level: 
X-Spam-Status: No, score=-15.048 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.547, 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 gRPhYG3rSpXI for <nmrg@ietfa.amsl.com>; Mon, 10 Mar 2014 08:17:00 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id AE1E61A0492 for <nmrg@irtf.org>; Mon, 10 Mar 2014 08:17:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5353; q=dns/txt; s=iport; t=1394464615; x=1395674215; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=RerCByhJNCu5SFAtYoRPuDB9JYDPJ4y0nlnd+0Rpbn0=; b=JX6+m7b5nmmv/KNyrtPZ22TZAuQI4+06iYlD1KMJRYHM1qlsv1019Oe5 Br9O7kQXXzhGSg1W+LNaAA7YClEE7diBmk6xeWoq4OkqEyply7duLcLvO oNx56pxQj8XqXDdTKwmQWYzoG6kWywTNKhuKqdijE8Ia/TAbTVrQRaf4R I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAPDWHVOtJV2c/2dsb2JhbABagwaBEsE8gRsWdIIlAQEBAwE6RAcEAgEIEQQBAQEKFBAyHQgBAQQBEggTh1YIz1EXjio4BoMegRQEqnKDLYIr
X-IronPort-AV: E=Sophos;i="4.97,624,1389744000"; d="scan'208";a="309238751"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP; 10 Mar 2014 15:16:55 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2AFGt4E002835 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <nmrg@irtf.org>; Mon, 10 Mar 2014 15:16:55 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.171]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Mon, 10 Mar 2014 10:16:54 -0500
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: [nmrg] Autonomic Use Cases
Thread-Index: Ac86X5T6lfxN1wJKTHant9hA7a0vlgA57goAAEMkh2A=
Date: Mon, 10 Mar 2014 15:16:53 +0000
Message-ID: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9B0939@xmb-rcd-x14.cisco.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.com> <531B8AEC.9050501@cisco.com>
In-Reply-To: <531B8AEC.9050501@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.148.163.59]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/Hl1lS55roBr3w-chP30uMIX0w2I
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: Mon, 10 Mar 2014 15:17:06 -0000

> -----Original Message-----
> From: Joe Clarke (jclarke)
> Sent: 08 March 2014 22:26
> To: Michael Behringer (mbehring); nmrg@irtf.org
> Subject: Re: [nmrg] Autonomic Use Cases
>=20
> On 3/7/14, 6:47 PM, Michael Behringer (mbehring) wrote:
> > NMRG,
> >
> > During the meeting we mentioned the need to document use cases. This
> section in the definitions draft is so far empty. Since we should have th=
at
> section BEFORE working out the use cases, I drafted something up here.
> >
> > I also realised that while we haven't really written down in the draft =
that
> the key point of this work really is to work out common infrastructure
> requirements. So I'm also suggesting an additional short section in the
> Design Goals section:
> >
> >        <section title=3D"Common Autonomic Networking Infrastructure">
> > 	<t><xref target=3D"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>
>=20
> Is this IETF or IRTF?  I know the goal is to eventually move into the IET=
F, but
> what do you intend here?

The way I see it, we kick this work off in the IRTF, but will soon move to =
the IETF for standardisation of approaches. Personally I think we don't nee=
d to be overly precise here, especially since IMO this section is going to =
drop off the final doc if and when it becomes an RFC.=20
=20
> > 	<t>Refer to the reference model below: All the components around
> the "autonomic service agents" should be common components, such that
> the autonomic service agents do not have to replicate common tasks
> individually. </t>
> >        </section>
> >
> > Comments? Does this capture the idea well?
>=20
> I think so.  I like the idea of moving beyond atomic autonomic functions =
into
> more of an autonomic system.  One key aspect of this system is self-
> monitoring and diagnostics (think regulation).  The idea of probes,
> sentinels, etc. play into this, and I think it should be called out in th=
e list.

Good point, added "self-monitoring and diagnostics" to the list. Thanks!
=20
> >
> > And then, the use case section could look like this:
> >
> >        <section title=3D"Guidelines for Case Studies">
> > 	<t>Case studies and problem statements are mandatory to
> understand common requirements for autonomic functions. This section
> explains how case studies should be outlined and what they should
> describe:
> >          <list style=3D"symbols">
> > 	  <t>Title</t>
> > 	  <t>Problem Statement: An explanation which problem is being
> > addressed, with information about existing solutions and their
> > shortcomings.</t>
>=20
> Nit: OF which problem is being...

Fixed. Thank you! :-)=20
=20
> > 	  <t>Intended user / administrator experience: The goal of
> autonomic networking is to simplify network administration and usage. Use
> cases should point out how their experience differs from current solution=
s.
> If a use case depends on configuration, it may include configuration
> samples, although obviously the goal is to reduce or eliminate
> configuration. </t>
> > 	  <t>Intent: Strictly speaking intent is part of the administrator
> > experience, but should probably explained explicitly with a high-level
> > view on how the autonomic function could be defined in intent (if
> > required). </t>
>=20
> Nit: probably BE explained...

Fixed, thank you! :-)=20

> > 	  <t>Local knowledge: What the function needs to know about the
> capabilities of the node itself, and which local resources need to be
> accessed.</t>
> > 	  <t>Communication requirements: The requirements for message
> exchange, discovery, negotiation, etc with other autonomic nodes. </t>
> >          </list>
> > 	</t>
> > 	<t>Use cases are not required to outline a solution in detail, nor to
> > specify precise protocol or intent details. They are used at this
> > point to determine a consolidated approach to developping an autonomic
> > networking infrastructure. </t>
>=20
> Nit: DEVELOPING (typo)

Fixed as well, thanks for the review!
=20
> >        </section>
> >
> > Comments?
>=20
> I think this is a good set of high-level guidelines.  Is there a need for=
 remote
> knowledge as well?  That is, what if a node needs to know topology to mak=
e
> the right choice?

Yes there is. The academic research in autonomic networking defines a "know=
ledge plane" for this purpose. You're right, that needs to be represented h=
ere somehow. I would contend that knowledge is both "inside" and "remote". =
It is however a fairly abstract concept, we'll need to nail this down with =
some good use cases.=20

Michael

> Joe


From nobody Mon Mar 10 23:15:53 2014
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 082CE1A063E for <nmrg@ietfa.amsl.com>; Mon, 10 Mar 2014 23:15:51 -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 RQOrpkXshgCZ for <nmrg@ietfa.amsl.com>; Mon, 10 Mar 2014 23:15:47 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD651A0641 for <nmrg@irtf.org>; Mon, 10 Mar 2014 23:15:46 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml210-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BSK96626; Tue, 11 Mar 2014 14:09:13 +0800 (CST)
Received: from SZXEML453-HUB.china.huawei.com (10.82.67.196) by szxeml210-edg.china.huawei.com (172.24.2.183) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 11 Mar 2014 14:08:58 +0800
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by SZXEML453-HUB.china.huawei.com (10.82.67.196) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 11 Mar 2014 14:08:59 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Tue, 11 Mar 2014 14:08:54 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Papadimitriou, Dimitri (Dimitri)" <dimitri.papadimitriou@alcatel-lucent.com>, "Michael Behringer (mbehring)" <mbehring@cisco.com>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: Autonomic Use Cases
Thread-Index: Ac86X5T6lfxN1wJKTHant9hA7a0vlgAXSsnAAIy0PcA=
Date: Tue, 11 Mar 2014 06:08:52 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE25FC2@nkgeml512-mbx.china.huawei.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.com> <84675BAA8C49154AB81E2587BE8BDF8308B4AC52@FR711WXCHMBA07.zeu.alcatel-lucent.com>
In-Reply-To: <84675BAA8C49154AB81E2587BE8BDF8308B4AC52@FR711WXCHMBA07.zeu.alcatel-lucent.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/AnUG7T5404q7MioZ02DDZA_gbiA
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 06:15:51 -0000

PkhlbmNlLCB0aGUgZm9jdXMgb2YgdGhpcyBkZXNpZ24gZ29hbCBzaG91bGQgYmUgb24gYXV0b25v
bWljIChkaXN0cmlidXRlZCkNCj5jb250cm9sIHBsYW5lIGVsZW1lbnRzLg0KDQpJIGZ1bGx5IGFn
cmVlIG9uIHRoaXMgb2JzZXJ2YXRpb24uIEhvd2V2ZXIsIHRvIGNsYXJpZnksIHRoaXMgYXV0b25v
bWljIGNvbnRyb2wgcGxhbmUgd2UgYXJlIHRhbGsgYWJvdXQgaXMgZGlmZmVyZW50IGZyb20gdGhl
IGN1cnJlbnQgY29udHJvbCBwbGFuIHRoYXQgbWFpbmx5IGZvY3VzIG9uLCBidXQgb25seSBvbiBy
b3V0aW5nIGFuZCByZWFjaGFiaWxpdHkuIFRoZSBuZXcgYXV0b25vbWljIGNvbnRyb2wgcGxhbiBp
cyBtYWlubHkgdGFyZ2V0aW5nIHRvIG1pbmltaXplIHRoZSBjdXJyZW50IG1hbmFnZW1lbnQgcGxh
bi4gSXQgc2hvdWxkIGJlIGFibGUgdG8gYXV0b25vbWljYWxseSBkZWNpZGUgdGhlIG1vc3QgKGlm
IG5vdCBhbGwpIG9mIG1hbmFnZW1lbnQgb2JqZWN0cyB0aGF0IGN1cnJlbnRseSBuZWVkcyBodW1h
biBpbnRlbGxpZ2VuY2UuDQoNClRoYW5rcywNCg0KU2hlbmcNCg0KPlRoYW5rcywNCj4tZGltaXRy
aS4NCj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiBGcm9tOiBubXJnIFttYWls
dG86bm1yZy1ib3VuY2VzQGlydGYub3JnXSBPbiBCZWhhbGYgT2YgTWljaGFlbA0KPkJlaHJpbmdl
cg0KPj4gKG1iZWhyaW5nKQ0KPj4gU2VudDogU2F0dXJkYXksIE1hcmNoIDA4LCAyMDE0IDAwOjQ3
DQo+PiBUbzogbm1yZ0BpcnRmLm9yZw0KPj4gU3ViamVjdDogW25tcmddIEF1dG9ub21pYyBVc2Ug
Q2FzZXMNCj4+DQo+PiBOTVJHLA0KPj4NCj4+IER1cmluZyB0aGUgbWVldGluZyB3ZSBtZW50aW9u
ZWQgdGhlIG5lZWQgdG8gZG9jdW1lbnQgdXNlIGNhc2VzLiBUaGlzDQo+PiBzZWN0aW9uIGluIHRo
ZSBkZWZpbml0aW9ucyBkcmFmdCBpcyBzbyBmYXIgZW1wdHkuIFNpbmNlIHdlIHNob3VsZCBoYXZl
DQo+PiB0aGF0IHNlY3Rpb24gQkVGT1JFIHdvcmtpbmcgb3V0IHRoZSB1c2UgY2FzZXMsIEkgZHJh
ZnRlZCBzb21ldGhpbmcgdXANCj4+IGhlcmUuDQo+Pg0KPj4gSSBhbHNvIHJlYWxpc2VkIHRoYXQg
d2hpbGUgd2UgaGF2ZW4ndCByZWFsbHkgd3JpdHRlbiBkb3duIGluIHRoZSBkcmFmdA0KPj4gdGhh
dCB0aGUga2V5IHBvaW50IG9mIHRoaXMgd29yayByZWFsbHkgaXMgdG8gd29yayBvdXQgY29tbW9u
DQo+PiBpbmZyYXN0cnVjdHVyZSByZXF1aXJlbWVudHMuIFNvIEknbSBhbHNvIHN1Z2dlc3Rpbmcg
YW4gYWRkaXRpb25hbCBzaG9ydA0KPj4gc2VjdGlvbiBpbiB0aGUgRGVzaWduIEdvYWxzIHNlY3Rp
b246DQo+Pg0KPj4gICAgICAgPHNlY3Rpb24gdGl0bGU9IkNvbW1vbiBBdXRvbm9taWMgTmV0d29y
a2luZyBJbmZyYXN0cnVjdHVyZSI+DQo+PiAJPHQ+PHhyZWYgdGFyZ2V0PSJJLUQuaXJ0Zi1ubXJn
LWFuLWdhcC1hbmFseXNpcyIvPiBwb2ludHMgb3V0IHRoYXQNCj4+IHRoZXJlIGFyZSBhbHJlYWR5
IGEgbnVtYmVyIG9mIGZ1bGx5IG9yIHBhcnRpYWxseSBhdXRvbm9taWMgZnVuY3Rpb25zDQo+PiBh
dmFpbGFibGUgdG9kYXkuIEhvd2V2ZXIsIHRoZXkgYXJlIGxhcmdlbHkgaW5kZXBlbmRlbnQsIGFu
ZCBlYWNoIGhhcyBpdHMNCj4+IG93biBtZXRob2RzIGFuZCBwcm90b2NvbHMgdG8gY29tbXVuaWNh
dGUsIGRpc2NvdmVyLCBkZWZpbmUgYW5kIGRpc3RyaWJ1dGUNCj4+IHBvbGljeSwgZXRjLiA8L3Q+
DQo+PiAJPHQ+VGhlIGdvYWwgb2YgdGhlIHdvcmsgb24gYXV0b25vbWljIG5ldHdvcmtpbmcgaW4g
dGhlIElFVEYgaXMNCj4+IHRoZXJlZm9yZSBub3QganVzdCB0byBjcmVhdGUgYXV0b25vbWljIGZ1
bmN0aW9ucywgYnV0IHRvIGRlZmluZSBhIGNvbW1vbg0KPj4gaW5mcmFzdHJ1Y3R1cmUgdGhhdCBh
dXRvbm9taWMgZnVuY3Rpb25zIGNhbiB1c2UuIFRoaXMgYXV0b25vbWljIG5ldHdvcmtpbmcNCj4+
IGluZnJhc3RydWN0dXJlIG1heSBjb250YWluIGNvbW1vbiBjb250cm9sIGFuZCBtYW5hZ2VtZW50
IGZ1bmN0aW9ucw0KPnN1Y2ggYXMNCj4+IG1lc3NhZ2luZywgc2VydmljZSBkaXNjb3ZlcnksIG5l
Z290aWF0aW9uLCBpbnRlbnQgZGlzdHJpYnV0aW9uLCBldGMuIEENCj4+IGNvbW1vbiBhcHByb2Fj
aCB0byBkZWZpbmUgYW5kIG1hbmFnZSBpbnRlbnQgaXMgYWxzbyByZXF1aXJlZC4gPC90Pg0KPj4g
CTx0PlJlZmVyIHRvIHRoZSByZWZlcmVuY2UgbW9kZWwgYmVsb3c6IEFsbCB0aGUgY29tcG9uZW50
cyBhcm91bmQgdGhlDQo+PiAiYXV0b25vbWljIHNlcnZpY2UgYWdlbnRzIiBzaG91bGQgYmUgY29t
bW9uIGNvbXBvbmVudHMsIHN1Y2ggdGhhdCB0aGUNCj4+IGF1dG9ub21pYyBzZXJ2aWNlIGFnZW50
cyBkbyBub3QgaGF2ZSB0byByZXBsaWNhdGUgY29tbW9uIHRhc2tzDQo+PiBpbmRpdmlkdWFsbHku
IDwvdD4NCj4+ICAgICAgIDwvc2VjdGlvbj4NCj4+DQo+PiBDb21tZW50cz8gRG9lcyB0aGlzIGNh
cHR1cmUgdGhlIGlkZWEgd2VsbD8NCj4+DQo+PiBBbmQgdGhlbiwgdGhlIHVzZSBjYXNlIHNlY3Rp
b24gY291bGQgbG9vayBsaWtlIHRoaXM6DQo+Pg0KPj4gICAgICAgPHNlY3Rpb24gdGl0bGU9Ikd1
aWRlbGluZXMgZm9yIENhc2UgU3R1ZGllcyI+DQo+PiAJPHQ+Q2FzZSBzdHVkaWVzIGFuZCBwcm9i
bGVtIHN0YXRlbWVudHMgYXJlIG1hbmRhdG9yeSB0byB1bmRlcnN0YW5kDQo+PiBjb21tb24gcmVx
dWlyZW1lbnRzIGZvciBhdXRvbm9taWMgZnVuY3Rpb25zLiBUaGlzIHNlY3Rpb24gZXhwbGFpbnMg
aG93DQo+PiBjYXNlIHN0dWRpZXMgc2hvdWxkIGJlIG91dGxpbmVkIGFuZCB3aGF0IHRoZXkgc2hv
dWxkIGRlc2NyaWJlOg0KPj4gICAgICAgICA8bGlzdCBzdHlsZT0ic3ltYm9scyI+DQo+PiAJICA8
dD5UaXRsZTwvdD4NCj4+IAkgIDx0PlByb2JsZW0gU3RhdGVtZW50OiBBbiBleHBsYW5hdGlvbiB3
aGljaCBwcm9ibGVtIGlzIGJlaW5nDQo+PiBhZGRyZXNzZWQsIHdpdGggaW5mb3JtYXRpb24gYWJv
dXQgZXhpc3Rpbmcgc29sdXRpb25zIGFuZCB0aGVpcg0KPj4gc2hvcnRjb21pbmdzLjwvdD4NCj4+
IAkgIDx0PkludGVuZGVkIHVzZXIgLyBhZG1pbmlzdHJhdG9yIGV4cGVyaWVuY2U6IFRoZSBnb2Fs
IG9mIGF1dG9ub21pYw0KPj4gbmV0d29ya2luZyBpcyB0byBzaW1wbGlmeSBuZXR3b3JrIGFkbWlu
aXN0cmF0aW9uIGFuZCB1c2FnZS4gVXNlIGNhc2VzDQo+PiBzaG91bGQgcG9pbnQgb3V0IGhvdyB0
aGVpciBleHBlcmllbmNlIGRpZmZlcnMgZnJvbSBjdXJyZW50IHNvbHV0aW9ucy4gSWYgYQ0KPj4g
dXNlIGNhc2UgZGVwZW5kcyBvbiBjb25maWd1cmF0aW9uLCBpdCBtYXkgaW5jbHVkZSBjb25maWd1
cmF0aW9uIHNhbXBsZXMsDQo+PiBhbHRob3VnaCBvYnZpb3VzbHkgdGhlIGdvYWwgaXMgdG8gcmVk
dWNlIG9yIGVsaW1pbmF0ZSBjb25maWd1cmF0aW9uLiA8L3Q+DQo+PiAJICA8dD5JbnRlbnQ6IFN0
cmljdGx5IHNwZWFraW5nIGludGVudCBpcyBwYXJ0IG9mIHRoZSBhZG1pbmlzdHJhdG9yDQo+PiBl
eHBlcmllbmNlLCBidXQgc2hvdWxkIHByb2JhYmx5IGV4cGxhaW5lZCBleHBsaWNpdGx5IHdpdGgg
YSBoaWdoLWxldmVsDQo+PiB2aWV3IG9uIGhvdyB0aGUgYXV0b25vbWljIGZ1bmN0aW9uIGNvdWxk
IGJlIGRlZmluZWQgaW4gaW50ZW50IChpZg0KPj4gcmVxdWlyZWQpLiA8L3Q+DQo+PiAJICA8dD5M
b2NhbCBrbm93bGVkZ2U6IFdoYXQgdGhlIGZ1bmN0aW9uIG5lZWRzIHRvIGtub3cgYWJvdXQgdGhl
DQo+PiBjYXBhYmlsaXRpZXMgb2YgdGhlIG5vZGUgaXRzZWxmLCBhbmQgd2hpY2ggbG9jYWwgcmVz
b3VyY2VzIG5lZWQgdG8gYmUNCj4+IGFjY2Vzc2VkLjwvdD4NCj4+IAkgIDx0PkNvbW11bmljYXRp
b24gcmVxdWlyZW1lbnRzOiBUaGUgcmVxdWlyZW1lbnRzIGZvciBtZXNzYWdlDQo+PiBleGNoYW5n
ZSwgZGlzY292ZXJ5LCBuZWdvdGlhdGlvbiwgZXRjIHdpdGggb3RoZXIgYXV0b25vbWljIG5vZGVz
LiA8L3Q+DQo+PiAgICAgICAgIDwvbGlzdD4NCj4+IAk8L3Q+DQo+PiAJPHQ+VXNlIGNhc2VzIGFy
ZSBub3QgcmVxdWlyZWQgdG8gb3V0bGluZSBhIHNvbHV0aW9uIGluIGRldGFpbCwgbm9yDQo+PiB0
byBzcGVjaWZ5IHByZWNpc2UgcHJvdG9jb2wgb3IgaW50ZW50IGRldGFpbHMuIFRoZXkgYXJlIHVz
ZWQgYXQgdGhpcyBwb2ludA0KPj4gdG8gZGV0ZXJtaW5lIGEgY29uc29saWRhdGVkIGFwcHJvYWNo
IHRvIGRldmVsb3BwaW5nIGFuIGF1dG9ub21pYw0KPj4gbmV0d29ya2luZyBpbmZyYXN0cnVjdHVy
ZS4gPC90Pg0KPj4gICAgICAgPC9zZWN0aW9uPg0KPj4NCj4+IENvbW1lbnRzPw0KPj4gTWljaGFl
bA0KPj4NCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+PiBubXJnIG1haWxpbmcgbGlzdA0KPj4gbm1yZ0BpcnRmLm9yZw0KPj4gaHR0cHM6Ly93d3cu
aXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ubXJnDQo+DQo+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj5ubXJnIG1haWxpbmcgbGlzdA0KPm5tcmdAaXJ0
Zi5vcmcNCj5odHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL25tcmcNCg==


From nobody Mon Mar 10 23:24:32 2014
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 E1D381A0641 for <nmrg@ietfa.amsl.com>; Mon, 10 Mar 2014 23:24:29 -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 U0JIHwXpqiwn for <nmrg@ietfa.amsl.com>; Mon, 10 Mar 2014 23:24:27 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by ietfa.amsl.com (Postfix) with ESMTP id EC4F91A063E for <nmrg@irtf.org>; Mon, 10 Mar 2014 23:24:26 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml207-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQW94998; Tue, 11 Mar 2014 14:24:14 +0800 (CST)
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml207-edg.china.huawei.com (172.24.2.56) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 11 Mar 2014 14:23:55 +0800
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by szxeml411-hub.china.huawei.com (10.82.67.138) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 11 Mar 2014 14:23:57 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Tue, 11 Mar 2014 14:23:54 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: Autonomic Use Cases
Thread-Index: Ac86X5T6lfxN1wJKTHant9hA7a0vlgCkc5KQ
Date: Tue, 11 Mar 2014 06:23:53 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE25FD7@nkgeml512-mbx.china.huawei.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@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/aWCk7ZO5iGgbGiwdqAe7VU8qRus
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 06:24:30 -0000

SGksIE1pY2hhZWwsDQoNCllvdXIgdGV4dCBmb3IgIkRlc2lnbiBHb2FsIiBhbmQgIkd1aWRlbGlu
ZXMgZm9yIENhc2UgU3R1ZGllcyIgbG9va3MgZ29vZC4NCg0KT25lIG1vcmUgdGhpbmcgSSB3b3Vs
ZCBsaWtlIHRvIGFkZDogdGhlIHVzZSBjYXNlcyBjb3VsZCBiZSB3cml0dGVuIHVwIHdpdGggdGhl
IGFzc3VtcHRpb24gdGhhdCB0aGUgY29tbW9uIGluZnJhc3RydWN0dXJlIHN1cHBvcnQgKGZvciBl
eGFtcGxlLCB0aGUgbmVnb3RpYXRpb24gYWJpbGl0eSBhbW9uZyBkZXZpY2VzKSB3YXMgYWxyZWFk
eSBpbiB0aGUgcGxhY2UuIFRoZSB1c2UgY2FzZXMgKGRvY3VtZW50cykgY291bGQgZm9jdXMgb24g
dGhlIHNjZW5hcmlvcywgcmVxdWlyZW1lbnRzIGFuZCBhdXRvbm9taWMgZnVuY3Rpb25zLg0KDQpS
ZWdhcmRzLA0KDQpTaGVuZw0KDQo+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBu
bXJnIFttYWlsdG86bm1yZy1ib3VuY2VzQGlydGYub3JnXSBPbiBCZWhhbGYgT2YgTWljaGFlbCBC
ZWhyaW5nZXINCj4obWJlaHJpbmcpDQo+U2VudDogU2F0dXJkYXksIE1hcmNoIDA4LCAyMDE0IDc6
NDcgQU0NCj5Ubzogbm1yZ0BpcnRmLm9yZw0KPlN1YmplY3Q6IFtubXJnXSBBdXRvbm9taWMgVXNl
IENhc2VzDQo+DQo+Tk1SRywNCj4NCj5EdXJpbmcgdGhlIG1lZXRpbmcgd2UgbWVudGlvbmVkIHRo
ZSBuZWVkIHRvIGRvY3VtZW50IHVzZSBjYXNlcy4gVGhpcw0KPnNlY3Rpb24gaW4gdGhlIGRlZmlu
aXRpb25zIGRyYWZ0IGlzIHNvIGZhciBlbXB0eS4gU2luY2Ugd2Ugc2hvdWxkIGhhdmUgdGhhdA0K
PnNlY3Rpb24gQkVGT1JFIHdvcmtpbmcgb3V0IHRoZSB1c2UgY2FzZXMsIEkgZHJhZnRlZCBzb21l
dGhpbmcgdXAgaGVyZS4NCj4NCj5JIGFsc28gcmVhbGlzZWQgdGhhdCB3aGlsZSB3ZSBoYXZlbid0
IHJlYWxseSB3cml0dGVuIGRvd24gaW4gdGhlIGRyYWZ0IHRoYXQgdGhlDQo+a2V5IHBvaW50IG9m
IHRoaXMgd29yayByZWFsbHkgaXMgdG8gd29yayBvdXQgY29tbW9uIGluZnJhc3RydWN0dXJlDQo+
cmVxdWlyZW1lbnRzLiBTbyBJJ20gYWxzbyBzdWdnZXN0aW5nIGFuIGFkZGl0aW9uYWwgc2hvcnQg
c2VjdGlvbiBpbiB0aGUgRGVzaWduDQo+R29hbHMgc2VjdGlvbjoNCj4NCj4gICAgICA8c2VjdGlv
biB0aXRsZT0iQ29tbW9uIEF1dG9ub21pYyBOZXR3b3JraW5nIEluZnJhc3RydWN0dXJlIj4NCj4J
PHQ+PHhyZWYgdGFyZ2V0PSJJLUQuaXJ0Zi1ubXJnLWFuLWdhcC1hbmFseXNpcyIvPiBwb2ludHMg
b3V0IHRoYXQgdGhlcmUNCj5hcmUgYWxyZWFkeSBhIG51bWJlciBvZiBmdWxseSBvciBwYXJ0aWFs
bHkgYXV0b25vbWljIGZ1bmN0aW9ucyBhdmFpbGFibGUgdG9kYXkuDQo+SG93ZXZlciwgdGhleSBh
cmUgbGFyZ2VseSBpbmRlcGVuZGVudCwgYW5kIGVhY2ggaGFzIGl0cyBvd24gbWV0aG9kcyBhbmQN
Cj5wcm90b2NvbHMgdG8gY29tbXVuaWNhdGUsIGRpc2NvdmVyLCBkZWZpbmUgYW5kIGRpc3RyaWJ1
dGUgcG9saWN5LCBldGMuIDwvdD4NCj4JPHQ+VGhlIGdvYWwgb2YgdGhlIHdvcmsgb24gYXV0b25v
bWljIG5ldHdvcmtpbmcgaW4gdGhlIElFVEYgaXMNCj50aGVyZWZvcmUgbm90IGp1c3QgdG8gY3Jl
YXRlIGF1dG9ub21pYyBmdW5jdGlvbnMsIGJ1dCB0byBkZWZpbmUgYSBjb21tb24NCj5pbmZyYXN0
cnVjdHVyZSB0aGF0IGF1dG9ub21pYyBmdW5jdGlvbnMgY2FuIHVzZS4gVGhpcyBhdXRvbm9taWMg
bmV0d29ya2luZw0KPmluZnJhc3RydWN0dXJlIG1heSBjb250YWluIGNvbW1vbiBjb250cm9sIGFu
ZCBtYW5hZ2VtZW50IGZ1bmN0aW9ucyBzdWNoDQo+YXMgbWVzc2FnaW5nLCBzZXJ2aWNlIGRpc2Nv
dmVyeSwgbmVnb3RpYXRpb24sIGludGVudCBkaXN0cmlidXRpb24sIGV0Yy4gQQ0KPmNvbW1vbiBh
cHByb2FjaCB0byBkZWZpbmUgYW5kIG1hbmFnZSBpbnRlbnQgaXMgYWxzbyByZXF1aXJlZC4gPC90
Pg0KPgk8dD5SZWZlciB0byB0aGUgcmVmZXJlbmNlIG1vZGVsIGJlbG93OiBBbGwgdGhlIGNvbXBv
bmVudHMgYXJvdW5kIHRoZQ0KPiJhdXRvbm9taWMgc2VydmljZSBhZ2VudHMiIHNob3VsZCBiZSBj
b21tb24gY29tcG9uZW50cywgc3VjaCB0aGF0IHRoZQ0KPmF1dG9ub21pYyBzZXJ2aWNlIGFnZW50
cyBkbyBub3QgaGF2ZSB0byByZXBsaWNhdGUgY29tbW9uIHRhc2tzIGluZGl2aWR1YWxseS4NCj48
L3Q+DQo+ICAgICAgPC9zZWN0aW9uPg0KPg0KPkNvbW1lbnRzPyBEb2VzIHRoaXMgY2FwdHVyZSB0
aGUgaWRlYSB3ZWxsPw0KPg0KPkFuZCB0aGVuLCB0aGUgdXNlIGNhc2Ugc2VjdGlvbiBjb3VsZCBs
b29rIGxpa2UgdGhpczoNCj4NCj4gICAgICA8c2VjdGlvbiB0aXRsZT0iR3VpZGVsaW5lcyBmb3Ig
Q2FzZSBTdHVkaWVzIj4NCj4JPHQ+Q2FzZSBzdHVkaWVzIGFuZCBwcm9ibGVtIHN0YXRlbWVudHMg
YXJlIG1hbmRhdG9yeSB0byB1bmRlcnN0YW5kDQo+Y29tbW9uIHJlcXVpcmVtZW50cyBmb3IgYXV0
b25vbWljIGZ1bmN0aW9ucy4gVGhpcyBzZWN0aW9uIGV4cGxhaW5zIGhvdw0KPmNhc2Ugc3R1ZGll
cyBzaG91bGQgYmUgb3V0bGluZWQgYW5kIHdoYXQgdGhleSBzaG91bGQgZGVzY3JpYmU6DQo+ICAg
ICAgICA8bGlzdCBzdHlsZT0ic3ltYm9scyI+DQo+CSAgPHQ+VGl0bGU8L3Q+DQo+CSAgPHQ+UHJv
YmxlbSBTdGF0ZW1lbnQ6IEFuIGV4cGxhbmF0aW9uIHdoaWNoIHByb2JsZW0gaXMgYmVpbmcNCj5h
ZGRyZXNzZWQsIHdpdGggaW5mb3JtYXRpb24gYWJvdXQgZXhpc3Rpbmcgc29sdXRpb25zIGFuZCB0
aGVpcg0KPnNob3J0Y29taW5ncy48L3Q+DQo+CSAgPHQ+SW50ZW5kZWQgdXNlciAvIGFkbWluaXN0
cmF0b3IgZXhwZXJpZW5jZTogVGhlIGdvYWwgb2YgYXV0b25vbWljDQo+bmV0d29ya2luZyBpcyB0
byBzaW1wbGlmeSBuZXR3b3JrIGFkbWluaXN0cmF0aW9uIGFuZCB1c2FnZS4gVXNlIGNhc2VzIHNo
b3VsZA0KPnBvaW50IG91dCBob3cgdGhlaXIgZXhwZXJpZW5jZSBkaWZmZXJzIGZyb20gY3VycmVu
dCBzb2x1dGlvbnMuIElmIGEgdXNlIGNhc2UNCj5kZXBlbmRzIG9uIGNvbmZpZ3VyYXRpb24sIGl0
IG1heSBpbmNsdWRlIGNvbmZpZ3VyYXRpb24gc2FtcGxlcywgYWx0aG91Z2gNCj5vYnZpb3VzbHkg
dGhlIGdvYWwgaXMgdG8gcmVkdWNlIG9yIGVsaW1pbmF0ZSBjb25maWd1cmF0aW9uLiA8L3Q+DQo+
CSAgPHQ+SW50ZW50OiBTdHJpY3RseSBzcGVha2luZyBpbnRlbnQgaXMgcGFydCBvZiB0aGUgYWRt
aW5pc3RyYXRvcg0KPmV4cGVyaWVuY2UsIGJ1dCBzaG91bGQgcHJvYmFibHkgZXhwbGFpbmVkIGV4
cGxpY2l0bHkgd2l0aCBhIGhpZ2gtbGV2ZWwgdmlldyBvbg0KPmhvdyB0aGUgYXV0b25vbWljIGZ1
bmN0aW9uIGNvdWxkIGJlIGRlZmluZWQgaW4gaW50ZW50IChpZiByZXF1aXJlZCkuIDwvdD4NCj4J
ICA8dD5Mb2NhbCBrbm93bGVkZ2U6IFdoYXQgdGhlIGZ1bmN0aW9uIG5lZWRzIHRvIGtub3cgYWJv
dXQgdGhlDQo+Y2FwYWJpbGl0aWVzIG9mIHRoZSBub2RlIGl0c2VsZiwgYW5kIHdoaWNoIGxvY2Fs
IHJlc291cmNlcyBuZWVkIHRvIGJlDQo+YWNjZXNzZWQuPC90Pg0KPgkgIDx0PkNvbW11bmljYXRp
b24gcmVxdWlyZW1lbnRzOiBUaGUgcmVxdWlyZW1lbnRzIGZvciBtZXNzYWdlDQo+ZXhjaGFuZ2Us
IGRpc2NvdmVyeSwgbmVnb3RpYXRpb24sIGV0YyB3aXRoIG90aGVyIGF1dG9ub21pYyBub2Rlcy4g
PC90Pg0KPiAgICAgICAgPC9saXN0Pg0KPgk8L3Q+DQo+CTx0PlVzZSBjYXNlcyBhcmUgbm90IHJl
cXVpcmVkIHRvIG91dGxpbmUgYSBzb2x1dGlvbiBpbiBkZXRhaWwsIG5vciB0bw0KPnNwZWNpZnkg
cHJlY2lzZSBwcm90b2NvbCBvciBpbnRlbnQgZGV0YWlscy4gVGhleSBhcmUgdXNlZCBhdCB0aGlz
IHBvaW50IHRvDQo+ZGV0ZXJtaW5lIGEgY29uc29saWRhdGVkIGFwcHJvYWNoIHRvIGRldmVsb3Bw
aW5nIGFuIGF1dG9ub21pYyBuZXR3b3JraW5nDQo+aW5mcmFzdHJ1Y3R1cmUuIDwvdD4NCj4gICAg
ICA8L3NlY3Rpb24+DQo+DQo+Q29tbWVudHM/DQo+TWljaGFlbA0KPg0KPl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+bm1yZyBtYWlsaW5nIGxpc3QNCj5u
bXJnQGlydGYub3JnDQo+aHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ubXJn
DQo=


From nobody Tue Mar 11 00:04:03 2014
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

Pj4gICAgICAgIDxzZWN0aW9uIHRpdGxlPSJDb21tb24gQXV0b25vbWljIE5ldHdvcmtpbmcgSW5m
cmFzdHJ1Y3R1cmUiPg0KPj4gCTx0Pjx4cmVmIHRhcmdldD0iSS1ELmlydGYtbm1yZy1hbi1nYXAt
YW5hbHlzaXMiLz4gcG9pbnRzIG91dCB0aGF0IHRoZXJlDQo+YXJlIGFscmVhZHkgYSBudW1iZXIg
b2YgZnVsbHkgb3IgcGFydGlhbGx5IGF1dG9ub21pYyBmdW5jdGlvbnMgYXZhaWxhYmxlIHRvZGF5
Lg0KPkhvd2V2ZXIsIHRoZXkgYXJlIGxhcmdlbHkgaW5kZXBlbmRlbnQsIGFuZCBlYWNoIGhhcyBp
dHMgb3duIG1ldGhvZHMgYW5kDQo+cHJvdG9jb2xzIHRvIGNvbW11bmljYXRlLCBkaXNjb3Zlciwg
ZGVmaW5lIGFuZCBkaXN0cmlidXRlIHBvbGljeSwgZXRjLiA8L3Q+DQo+PiAJPHQ+VGhlIGdvYWwg
b2YgdGhlIHdvcmsgb24gYXV0b25vbWljIG5ldHdvcmtpbmcgaW4gdGhlIElFVEYgaXMNCj50aGVy
ZWZvcmUgbm90IGp1c3QgdG8gY3JlYXRlIGF1dG9ub21pYyBmdW5jdGlvbnMsIGJ1dCB0byBkZWZp
bmUgYSBjb21tb24NCj5pbmZyYXN0cnVjdHVyZSB0aGF0IGF1dG9ub21pYyBmdW5jdGlvbnMgY2Fu
IHVzZS4gVGhpcyBhdXRvbm9taWMgbmV0d29ya2luZw0KPmluZnJhc3RydWN0dXJlIG1heSBjb250
YWluIGNvbW1vbiBjb250cm9sIGFuZCBtYW5hZ2VtZW50IGZ1bmN0aW9ucyBzdWNoDQo+YXMgbWVz
c2FnaW5nLCBzZXJ2aWNlIGRpc2NvdmVyeSwgbmVnb3RpYXRpb24sIGludGVudCBkaXN0cmlidXRp
b24sIGV0Yy4gQQ0KPmNvbW1vbiBhcHByb2FjaCB0byBkZWZpbmUgYW5kIG1hbmFnZSBpbnRlbnQg
aXMgYWxzbyByZXF1aXJlZC4gPC90Pg0KPg0KPklzIHRoaXMgSUVURiBvciBJUlRGPyAgSSBrbm93
IHRoZSBnb2FsIGlzIHRvIGV2ZW50dWFsbHkgbW92ZSBpbnRvIHRoZQ0KPklFVEYsIGJ1dCB3aGF0
IGRvIHlvdSBpbnRlbmQgaGVyZT8NCg0KVGhlIGF1dG9ub21pYyBuZXR3b3JrIHdvcmsgaW4gSVJU
RiBhbmQgSUVURiBhcmUgcmVsZXZhbnQgdG8gZWFjaCBvdGhlci4gVGhlIGlkZWFsIGlzIHdlIGhh
dmUgaGlnaC1sZXZlbCBkZWZpbml0aW9ucywgZGVzaWduIGdvYWxzLCByZXF1aXJlbWVudHMgYW5k
IGdhcCBhbmFseXNpcyBpbiBJUlRGLiBGb3IgYW55IGNvbmNyZXRlIHByb3RvY29sIHdvcmssIHRo
YXQgc3VwcG9ydHMgY29tbW9uIGF1dG9ub21pYyBuZXR3b3JrIGluZnJhc3RydWN0dXJlLCBzdWNo
IGFzIG5lZ290aWF0aW9uIHByb3RvY29sLCBzaG91bGQgYmUgaG9sZCBpbiBJRVRGLg0KDQpJZGVh
bGx5LCB3ZSB3b3VsZCBoYXZlIHNldmVyYWwgYXV0b25vbWljIG5ldHdvcmsgdXNlIGNhc2VzIHRo
YXQgYXJlIGJhc2VkIG9uIHRoZSBzYW1lIGNvbW1vbiBjb250cm9sIGFuZCBtYW5hZ2VtZW50IGZ1
bmN0aW9ucy4gVGhlbiB3ZSBjYW4gd29yayBvbiB0aGVzZSBjb21tb24gY29udHJvbCBhbmQgbWFu
YWdlbWVudCBmdW5jdGlvbnMgaW4gSUVURiwgd2hpbGUgZWFjaCBvZiB1c2UgY2FzZXMgbWF5IGhh
dmUgaXRzIG93biBpbnN0YW5jZSBvbiB0b3Agb2YgdGhlIGNvbW1vbiBpbmZyYXN0cnVjdHVyZS4N
Cg0KQmVzdCByZWdhcmRzLA0KDQpTaGVuZw0K


From nobody Wed Mar 12 01:42:20 2014
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 74E451A0926 for <nmrg@ietfa.amsl.com>; Wed, 12 Mar 2014 01:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level: 
X-Spam-Status: No, score=-15.048 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.547, 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 jSavtgNptB8u for <nmrg@ietfa.amsl.com>; Wed, 12 Mar 2014 01:42:11 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id A5A051A0922 for <nmrg@irtf.org>; Wed, 12 Mar 2014 01:42:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7164; q=dns/txt; s=iport; t=1394613726; x=1395823326; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=LB+d/QEs/Xncd1jgyg1u1o+VU/1jc4MekW8ri9iscwE=; b=JfFvjGlxw3AZL5AtSGYYqrMLQx+6qXM2ppPjA05/vBar9l/tVZCaTlW3 GvAdPFEj7EblvuwvI98ZU9NJCOF7yvTQzGANQjkWpa1uuyixX8PVR5FES +yNDDwqgF5dTWQ0/UdKrg3H1xYlKRYHASV2dfUZVLDOqcnekQbCmuKZrH g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFAL4cIFOtJV2c/2dsb2JhbABagwY7V4MGtxuHMBmBABZ0giUBAQEDAQEBASAROhcEAgEIEQQBAQMCBh0DAgICJQsUAQgIAQEEARIIE4dWCA2wZ6BsEwSBKYs3gUsWIgaCaTWBFASqcoMtgis
X-IronPort-AV: E=Sophos;i="4.97,636,1389744000"; d="scan'208";a="309739073"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 12 Mar 2014 08:42:05 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2C8g4v8012698 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 12 Mar 2014 08:42:05 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.171]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Wed, 12 Mar 2014 03:42:04 -0500
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "Papadimitriou, Dimitri (Dimitri)" <dimitri.papadimitriou@alcatel-lucent.com>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: Autonomic Use Cases
Thread-Index: Ac86X5T6lfxN1wJKTHant9hA7a0vlgAXSsnAAIy0PcAAEIjEYA==
Date: Wed, 12 Mar 2014 08:42:03 +0000
Message-ID: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9B54FC@xmb-rcd-x14.cisco.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9AEDD9@xmb-rcd-x14.cisco.com> <84675BAA8C49154AB81E2587BE8BDF8308B4AC52@FR711WXCHMBA07.zeu.alcatel-lucent.com> <5D36713D8A4E7348A7E10DF7437A4B923AE25FC2@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE25FC2@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.147.144.92]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/4a6TZyHNHkBWa0pb6sr9DFg7R_o
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: Wed, 12 Mar 2014 08:42:16 -0000

VGhlIGF1dG9ub21pYyBjb250cm9sIHBsYW5lIGlzIGEgZ2VuZXJpYyBjb21tdW5pY2F0aW9ucyBj
aGFubmVsIGJldHdlZW4gYXV0b25vbWljIGRldmljZXMuIEl0IGNvbnRhaW5zIHByb3RvY29scyBu
ZWVkZWQgZm9yIGF1dG9ub21pYyBwdXJwb3Nlcywgc3VjaCBhcyBhIG1lc3NhZ2UgYnVzLCBkaXNj
b3ZlcnkgZnVuY3Rpb25zLCBldGMuIA0KDQpNaWNoYWVsDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogU2hlbmcgSmlhbmcgW21haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5j
b21dDQo+IFNlbnQ6IDExIE1hcmNoIDIwMTQgMDc6MDkNCj4gVG86IFBhcGFkaW1pdHJpb3UsIERp
bWl0cmkgKERpbWl0cmkpOyBNaWNoYWVsIEJlaHJpbmdlciAobWJlaHJpbmcpOw0KPiBubXJnQGly
dGYub3JnDQo+IFN1YmplY3Q6IFJFOiBBdXRvbm9taWMgVXNlIENhc2VzDQo+IA0KPiA+SGVuY2Us
IHRoZSBmb2N1cyBvZiB0aGlzIGRlc2lnbiBnb2FsIHNob3VsZCBiZSBvbiBhdXRvbm9taWMNCj4g
PihkaXN0cmlidXRlZCkgY29udHJvbCBwbGFuZSBlbGVtZW50cy4NCj4gDQo+IEkgZnVsbHkgYWdy
ZWUgb24gdGhpcyBvYnNlcnZhdGlvbi4gSG93ZXZlciwgdG8gY2xhcmlmeSwgdGhpcyBhdXRvbm9t
aWMgY29udHJvbA0KPiBwbGFuZSB3ZSBhcmUgdGFsayBhYm91dCBpcyBkaWZmZXJlbnQgZnJvbSB0
aGUgY3VycmVudCBjb250cm9sIHBsYW4gdGhhdA0KPiBtYWlubHkgZm9jdXMgb24sIGJ1dCBvbmx5
IG9uIHJvdXRpbmcgYW5kIHJlYWNoYWJpbGl0eS4gVGhlIG5ldyBhdXRvbm9taWMNCj4gY29udHJv
bCBwbGFuIGlzIG1haW5seSB0YXJnZXRpbmcgdG8gbWluaW1pemUgdGhlIGN1cnJlbnQgbWFuYWdl
bWVudCBwbGFuLg0KPiBJdCBzaG91bGQgYmUgYWJsZSB0byBhdXRvbm9taWNhbGx5IGRlY2lkZSB0
aGUgbW9zdCAoaWYgbm90IGFsbCkgb2YNCj4gbWFuYWdlbWVudCBvYmplY3RzIHRoYXQgY3VycmVu
dGx5IG5lZWRzIGh1bWFuIGludGVsbGlnZW5jZS4NCj4gDQo+IFRoYW5rcywNCj4gDQo+IFNoZW5n
DQo+IA0KPiA+VGhhbmtzLA0KPiA+LWRpbWl0cmkuDQo+ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogbm1yZyBbbWFpbHRvOm5tcmctYm91bmNlc0BpcnRmLm9y
Z10gT24gQmVoYWxmIE9mIE1pY2hhZWwNCj4gPkJlaHJpbmdlcg0KPiA+PiAobWJlaHJpbmcpDQo+
ID4+IFNlbnQ6IFNhdHVyZGF5LCBNYXJjaCAwOCwgMjAxNCAwMDo0Nw0KPiA+PiBUbzogbm1yZ0Bp
cnRmLm9yZw0KPiA+PiBTdWJqZWN0OiBbbm1yZ10gQXV0b25vbWljIFVzZSBDYXNlcw0KPiA+Pg0K
PiA+PiBOTVJHLA0KPiA+Pg0KPiA+PiBEdXJpbmcgdGhlIG1lZXRpbmcgd2UgbWVudGlvbmVkIHRo
ZSBuZWVkIHRvIGRvY3VtZW50IHVzZSBjYXNlcy4gVGhpcw0KPiA+PiBzZWN0aW9uIGluIHRoZSBk
ZWZpbml0aW9ucyBkcmFmdCBpcyBzbyBmYXIgZW1wdHkuIFNpbmNlIHdlIHNob3VsZA0KPiA+PiBo
YXZlIHRoYXQgc2VjdGlvbiBCRUZPUkUgd29ya2luZyBvdXQgdGhlIHVzZSBjYXNlcywgSSBkcmFm
dGVkDQo+ID4+IHNvbWV0aGluZyB1cCBoZXJlLg0KPiA+Pg0KPiA+PiBJIGFsc28gcmVhbGlzZWQg
dGhhdCB3aGlsZSB3ZSBoYXZlbid0IHJlYWxseSB3cml0dGVuIGRvd24gaW4gdGhlDQo+ID4+IGRy
YWZ0IHRoYXQgdGhlIGtleSBwb2ludCBvZiB0aGlzIHdvcmsgcmVhbGx5IGlzIHRvIHdvcmsgb3V0
IGNvbW1vbg0KPiA+PiBpbmZyYXN0cnVjdHVyZSByZXF1aXJlbWVudHMuIFNvIEknbSBhbHNvIHN1
Z2dlc3RpbmcgYW4gYWRkaXRpb25hbA0KPiA+PiBzaG9ydCBzZWN0aW9uIGluIHRoZSBEZXNpZ24g
R29hbHMgc2VjdGlvbjoNCj4gPj4NCj4gPj4gICAgICAgPHNlY3Rpb24gdGl0bGU9IkNvbW1vbiBB
dXRvbm9taWMgTmV0d29ya2luZyBJbmZyYXN0cnVjdHVyZSI+DQo+ID4+IAk8dD48eHJlZiB0YXJn
ZXQ9IkktRC5pcnRmLW5tcmctYW4tZ2FwLWFuYWx5c2lzIi8+IHBvaW50cyBvdXQgdGhhdA0KPiA+
PiB0aGVyZSBhcmUgYWxyZWFkeSBhIG51bWJlciBvZiBmdWxseSBvciBwYXJ0aWFsbHkgYXV0b25v
bWljIGZ1bmN0aW9ucw0KPiA+PiBhdmFpbGFibGUgdG9kYXkuIEhvd2V2ZXIsIHRoZXkgYXJlIGxh
cmdlbHkgaW5kZXBlbmRlbnQsIGFuZCBlYWNoIGhhcw0KPiA+PiBpdHMgb3duIG1ldGhvZHMgYW5k
IHByb3RvY29scyB0byBjb21tdW5pY2F0ZSwgZGlzY292ZXIsIGRlZmluZSBhbmQNCj4gPj4gZGlz
dHJpYnV0ZSBwb2xpY3ksIGV0Yy4gPC90Pg0KPiA+PiAJPHQ+VGhlIGdvYWwgb2YgdGhlIHdvcmsg
b24gYXV0b25vbWljIG5ldHdvcmtpbmcgaW4gdGhlIElFVEYgaXMNCj4gPj4gdGhlcmVmb3JlIG5v
dCBqdXN0IHRvIGNyZWF0ZSBhdXRvbm9taWMgZnVuY3Rpb25zLCBidXQgdG8gZGVmaW5lIGENCj4g
Pj4gY29tbW9uIGluZnJhc3RydWN0dXJlIHRoYXQgYXV0b25vbWljIGZ1bmN0aW9ucyBjYW4gdXNl
LiBUaGlzDQo+ID4+IGF1dG9ub21pYyBuZXR3b3JraW5nIGluZnJhc3RydWN0dXJlIG1heSBjb250
YWluIGNvbW1vbiBjb250cm9sIGFuZA0KPiA+PiBtYW5hZ2VtZW50IGZ1bmN0aW9ucw0KPiA+c3Vj
aCBhcw0KPiA+PiBtZXNzYWdpbmcsIHNlcnZpY2UgZGlzY292ZXJ5LCBuZWdvdGlhdGlvbiwgaW50
ZW50IGRpc3RyaWJ1dGlvbiwgZXRjLg0KPiA+PiBBIGNvbW1vbiBhcHByb2FjaCB0byBkZWZpbmUg
YW5kIG1hbmFnZSBpbnRlbnQgaXMgYWxzbyByZXF1aXJlZC4gPC90Pg0KPiA+PiAJPHQ+UmVmZXIg
dG8gdGhlIHJlZmVyZW5jZSBtb2RlbCBiZWxvdzogQWxsIHRoZSBjb21wb25lbnRzIGFyb3VuZA0K
PiB0aGUNCj4gPj4gImF1dG9ub21pYyBzZXJ2aWNlIGFnZW50cyIgc2hvdWxkIGJlIGNvbW1vbiBj
b21wb25lbnRzLCBzdWNoIHRoYXQNCj4gdGhlDQo+ID4+IGF1dG9ub21pYyBzZXJ2aWNlIGFnZW50
cyBkbyBub3QgaGF2ZSB0byByZXBsaWNhdGUgY29tbW9uIHRhc2tzDQo+ID4+IGluZGl2aWR1YWxs
eS4gPC90Pg0KPiA+PiAgICAgICA8L3NlY3Rpb24+DQo+ID4+DQo+ID4+IENvbW1lbnRzPyBEb2Vz
IHRoaXMgY2FwdHVyZSB0aGUgaWRlYSB3ZWxsPw0KPiA+Pg0KPiA+PiBBbmQgdGhlbiwgdGhlIHVz
ZSBjYXNlIHNlY3Rpb24gY291bGQgbG9vayBsaWtlIHRoaXM6DQo+ID4+DQo+ID4+ICAgICAgIDxz
ZWN0aW9uIHRpdGxlPSJHdWlkZWxpbmVzIGZvciBDYXNlIFN0dWRpZXMiPg0KPiA+PiAJPHQ+Q2Fz
ZSBzdHVkaWVzIGFuZCBwcm9ibGVtIHN0YXRlbWVudHMgYXJlIG1hbmRhdG9yeSB0bw0KPiB1bmRl
cnN0YW5kDQo+ID4+IGNvbW1vbiByZXF1aXJlbWVudHMgZm9yIGF1dG9ub21pYyBmdW5jdGlvbnMu
IFRoaXMgc2VjdGlvbiBleHBsYWlucw0KPiA+PiBob3cgY2FzZSBzdHVkaWVzIHNob3VsZCBiZSBv
dXRsaW5lZCBhbmQgd2hhdCB0aGV5IHNob3VsZCBkZXNjcmliZToNCj4gPj4gICAgICAgICA8bGlz
dCBzdHlsZT0ic3ltYm9scyI+DQo+ID4+IAkgIDx0PlRpdGxlPC90Pg0KPiA+PiAJICA8dD5Qcm9i
bGVtIFN0YXRlbWVudDogQW4gZXhwbGFuYXRpb24gd2hpY2ggcHJvYmxlbSBpcyBiZWluZw0KPiA+
PiBhZGRyZXNzZWQsIHdpdGggaW5mb3JtYXRpb24gYWJvdXQgZXhpc3Rpbmcgc29sdXRpb25zIGFu
ZCB0aGVpcg0KPiA+PiBzaG9ydGNvbWluZ3MuPC90Pg0KPiA+PiAJICA8dD5JbnRlbmRlZCB1c2Vy
IC8gYWRtaW5pc3RyYXRvciBleHBlcmllbmNlOiBUaGUgZ29hbCBvZg0KPiBhdXRvbm9taWMNCj4g
Pj4gbmV0d29ya2luZyBpcyB0byBzaW1wbGlmeSBuZXR3b3JrIGFkbWluaXN0cmF0aW9uIGFuZCB1
c2FnZS4gVXNlIGNhc2VzDQo+ID4+IHNob3VsZCBwb2ludCBvdXQgaG93IHRoZWlyIGV4cGVyaWVu
Y2UgZGlmZmVycyBmcm9tIGN1cnJlbnQgc29sdXRpb25zLg0KPiA+PiBJZiBhIHVzZSBjYXNlIGRl
cGVuZHMgb24gY29uZmlndXJhdGlvbiwgaXQgbWF5IGluY2x1ZGUgY29uZmlndXJhdGlvbg0KPiA+
PiBzYW1wbGVzLCBhbHRob3VnaCBvYnZpb3VzbHkgdGhlIGdvYWwgaXMgdG8gcmVkdWNlIG9yIGVs
aW1pbmF0ZQ0KPiBjb25maWd1cmF0aW9uLiA8L3Q+DQo+ID4+IAkgIDx0PkludGVudDogU3RyaWN0
bHkgc3BlYWtpbmcgaW50ZW50IGlzIHBhcnQgb2YgdGhlIGFkbWluaXN0cmF0b3INCj4gPj4gZXhw
ZXJpZW5jZSwgYnV0IHNob3VsZCBwcm9iYWJseSBleHBsYWluZWQgZXhwbGljaXRseSB3aXRoIGEN
Cj4gPj4gaGlnaC1sZXZlbCB2aWV3IG9uIGhvdyB0aGUgYXV0b25vbWljIGZ1bmN0aW9uIGNvdWxk
IGJlIGRlZmluZWQgaW4NCj4gPj4gaW50ZW50IChpZiByZXF1aXJlZCkuIDwvdD4NCj4gPj4gCSAg
PHQ+TG9jYWwga25vd2xlZGdlOiBXaGF0IHRoZSBmdW5jdGlvbiBuZWVkcyB0byBrbm93IGFib3V0
IHRoZQ0KPiA+PiBjYXBhYmlsaXRpZXMgb2YgdGhlIG5vZGUgaXRzZWxmLCBhbmQgd2hpY2ggbG9j
YWwgcmVzb3VyY2VzIG5lZWQgdG8gYmUNCj4gPj4gYWNjZXNzZWQuPC90Pg0KPiA+PiAJICA8dD5D
b21tdW5pY2F0aW9uIHJlcXVpcmVtZW50czogVGhlIHJlcXVpcmVtZW50cyBmb3IgbWVzc2FnZQ0K
PiA+PiBleGNoYW5nZSwgZGlzY292ZXJ5LCBuZWdvdGlhdGlvbiwgZXRjIHdpdGggb3RoZXIgYXV0
b25vbWljIG5vZGVzLiA8L3Q+DQo+ID4+ICAgICAgICAgPC9saXN0Pg0KPiA+PiAJPC90Pg0KPiA+
PiAJPHQ+VXNlIGNhc2VzIGFyZSBub3QgcmVxdWlyZWQgdG8gb3V0bGluZSBhIHNvbHV0aW9uIGlu
IGRldGFpbCwgbm9yDQo+ID4+IHRvIHNwZWNpZnkgcHJlY2lzZSBwcm90b2NvbCBvciBpbnRlbnQg
ZGV0YWlscy4gVGhleSBhcmUgdXNlZCBhdCB0aGlzDQo+ID4+IHBvaW50IHRvIGRldGVybWluZSBh
IGNvbnNvbGlkYXRlZCBhcHByb2FjaCB0byBkZXZlbG9wcGluZyBhbg0KPiA+PiBhdXRvbm9taWMg
bmV0d29ya2luZyBpbmZyYXN0cnVjdHVyZS4gPC90Pg0KPiA+PiAgICAgICA8L3NlY3Rpb24+DQo+
ID4+DQo+ID4+IENvbW1lbnRzPw0KPiA+PiBNaWNoYWVsDQo+ID4+DQo+ID4+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+IG5tcmcgbWFpbGluZyBs
aXN0DQo+ID4+IG5tcmdAaXJ0Zi5vcmcNCj4gPj4gaHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9ubXJnDQo+ID4NCj4gPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQo+ID5ubXJnIG1haWxpbmcgbGlzdA0KPiA+bm1yZ0BpcnRmLm9yZw0K
PiA+aHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ubXJnDQo=


From nobody Thu Mar 13 22:12:21 2014
Return-Path: <jclarke@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 B90A51A0030 for <nmrg@ietfa.amsl.com>; Thu, 13 Mar 2014 22:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 3UIc7lO1PAYd for <nmrg@ietfa.amsl.com>; Thu, 13 Mar 2014 22:12:14 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id A05D61A0045 for <nmrg@irtf.org>; Thu, 13 Mar 2014 22:12:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1998; q=dns/txt; s=iport; t=1394773926; x=1395983526; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=vRymLdYisG9JxCo/IAxTzUj9SR0KTH1BIRXM8Vqrhfo=; b=R0CWrLYjbIiWdqBMYsBYJCbSAf45GFEArcVv4DAOdpWgw26Ehm14UYBI LickG+GJ8ZnWJe1RlPtY1Ly5EfTasb4Rfx0m+VskZrMg9lcoF8PitwW56 9e4HqTW+CuKCHAhDcocx0aSoQAYR8s3YaIb5+3CoVEX1QWGqvKWzaUFyX s=;
X-IronPort-AV: E=Sophos;i="4.97,652,1389744000"; d="scan'208";a="27420876"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP; 14 Mar 2014 05:12:06 +0000
Received: from [10.150.72.65] (dhcp-10-150-72-65.cisco.com [10.150.72.65]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s2E5C5JB012906; Fri, 14 Mar 2014 05:12:05 GMT
Message-ID: <53228FA5.1020501@cisco.com>
Date: Fri, 14 Mar 2014 01:12:05 -0400
From: Joe Marcus Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>, "nmrg@irtf.org" <nmrg@irtf.org>
References: <53189A82.80404@cisco.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9B08BB@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF1D9B08BB@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/tYfse3clmgG_CPOu_Rmg_JL10tg
Subject: Re: [nmrg] Comments on 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: Fri, 14 Mar 2014 05:12:19 -0000

On 3/10/14, 11:15 AM, Michael Behringer (mbehring) wrote:
> Joe,
>
> I like your ideas. Why don't you write them up, either as a standalone use case, or with Laurent? It would be interesting to see a concrete example of such an autonomic behaviour, and deduce which type of interactions would be required.

Happy to.  Laurent is away, but when he returns, I'll see what we wants 
to do.

Joe

>
> Michael
>
>> -----Original Message-----
>> From: nmrg [mailto:nmrg-bounces@irtf.org] On Behalf Of Joe Clarke
>> (jclarke)
>> Sent: 06 March 2014 16:56
>> To: nmrg@irtf.org
>> Subject: [nmrg] Comments on autonomic use cases
>>
>> After listening to the talks today, I have an overall comment related to
>> network traceability in an autonomic environment.  I was very intrigued by
>> Laurent's talk as I have been doing work in this area using Cisco embedded
>> automation.  I strongly feel that we should be doing more autonomic cross-
>> device analysis of problem conditions to do smart rerouting in the case of
>> instability.  For example, in addition to local factors like temperature and
>> load, we could look at path or hop stability in terms of dropped packets
>> along a flow, jitter, latency, etc. and determine a new optimum/stable path.
>>
>> Additionally, with respect to the troubleshooting section in draft-jiang-
>> nmrg-an-gap-analysis-00, I think there is something that can be done
>> autonomically relating to hardware failure.  Given Laurent's ideas again, a
>> device that can detect imminent failure (e.g., SMART-like operations on
>> harddrives), and make proactive changes to the network to reroute around
>> an impending hardware failure until humans can get involved.  This can
>> prevent extended outages.  Perhaps this is something that could
>> supplement this section of text.
>>
>> Joe
>>
>> _______________________________________________
>> nmrg mailing list
>> nmrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/nmrg


From nobody Fri Mar 14 23:39:15 2014
Return-Path: <phanvc@gmail.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 7C91A1A0035 for <nmrg@ietfa.amsl.com>; Fri, 14 Mar 2014 23:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 V_i2bkxl6abn for <nmrg@ietfa.amsl.com>; Fri, 14 Mar 2014 23:39:08 -0700 (PDT)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 609561A002A for <nmrg@irtf.org>; Fri, 14 Mar 2014 23:39:08 -0700 (PDT)
Received: by mail-yh0-f43.google.com with SMTP id b6so3511141yha.16 for <nmrg@irtf.org>; Fri, 14 Mar 2014 23:39:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=GackySr3gL30HZWxIS+67IQrqBHuyRYeva4CiB5JHQk=; b=sKyA5SiIJuhQ04QGrrttFIlOsOnSQOjnYW7VngfIBqmoNK3bBbsUDQ21znt4rXKMd7 eRpmCqbDdjheX6cWiUxiD/6dKbCvSVFQpYPEmwMWxbrZJZ8WKvfgyb3XAofI8IsjYQmC 3EIAl8+/HWVjZEx8LlZynqDhmE01O3X9giIQNCRcGTQxguY7Z3f/eGdQLoqrdXwgQmlq rU5eQtoWC4jDWzBINuWOiAjSu+rVuHPQ4HA7/A57Dw7OS+j3u0B3qUeUiIlEdVsl6olD aq/aZ7gUTEBrErzNYzEyCOyufCzz9IrEqrGcD6dBfptQGPAMFvrSGuLsWZVS2HcE92RN L2/Q==
MIME-Version: 1.0
X-Received: by 10.236.100.235 with SMTP id z71mr17157135yhf.43.1394865539992;  Fri, 14 Mar 2014 23:38:59 -0700 (PDT)
Sender: phanvc@gmail.com
Received: by 10.170.139.8 with HTTP; Fri, 14 Mar 2014 23:38:59 -0700 (PDT)
Date: Sat, 15 Mar 2014 13:38:59 +0700
X-Google-Sender-Auth: R_iksOHM60MRDFbR8RwyKNPr5Wk
Message-ID: <CAADY+-sQJK9GP4OiugCWgF0zGSw-Jb0zBej2kfK01s5aknfiuQ@mail.gmail.com>
From: Phan Cong Vinh <pcvinh@ntt.edu.vn>
To: nmrg@irtf.org
Content-Type: multipart/alternative; boundary=20cf301b65fb054fc204f49f716b
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/bu3-NbnSw3ma8g6max6nBPUKbEc
Subject: [nmrg] [ICTCC 2014] CFP: The International Conference on NaTure of Computation and Communication
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: Sat, 15 Mar 2014 06:39:11 -0000

--20cf301b65fb054fc204f49f716b
Content-Type: text/plain; charset=UTF-8

 The International Conference on NaTure of Computation and Communication

(ICTCC)

Location: Ho Chi Minh City, Vietnam
Time: 24-25 November 2014
Website: http://ictcc.org/2014

----

The ICTCC 2014 jointly organized by EAI and Nguyen Tat Thanh University
(NTTU) is a place for highly original ideas about how the nature is going
to shape computing systems of the future. Hence, it focuses on rigorous
approaches and cutting-edge solutions, which encompass three classes of
major methods:

    Those that take inspiration from nature for the development of novel
problem solving techniques;
    Those that are based on the use of computers or networks to synthesize
natural phenomena; and
    Those that employ natural materials (e.g., molecules,) to compute or
communicate.

Its purpose is to make a formal basis more accessible to researchers,
scientists, professionals and students as well as developers and
practitioners in ICT by providing them with state-of-the-art research
results, applications, opportunities and future trends.

We hope that the conference will receive many papers and the participation
of a large number of students, researchers, and professionals from all over
the world.

Original papers are solicited for the ICTCC 2014. In particular,
theoretical contributions should be formally stated and justified, and
practical applications should be based on their firm formal basis.
Suggested topics include, but are not limited to, the following:
SCOPE OF TOPICS:

    Autonomic computing/communicating
    Amorphous computing
    Biologically-inspired computing/communicating
    Cellular automata
    Cellular computing
    Collective intelligence in computing/communicating
    Collision-based computing
    Computation/communication based on chaos and dynamical systems
    Context-aware computing/communicating
    DNA computing
    Evolutionary computing
    Hypercomputation
    Massive parallel computing
    Membrane computing
    Molecular computing
    Neural computing
    Optical computing
    Physarum computing
    Quantum computing
    Relativistic computing
    Spatial computing
    Swam intelligence in computing/communicating
    Wetware computing

HIGHLIGHTS

    The event is endorsed by the European Alliance for Innovation, a
leading community-based organization devoted to the advancement of
innovation in the field of ICT

    All accepted papers will be published by Springer and made available
through SpringerLink Digital Library, one of the world's largest scientific
libraries

    Proceedings will be submitted for indexing by Google Scholar, ISI, EI
Compendex, Scopus and many more

IMPORTANT DATES

    Workshop proposals due: 01 April 2014

    Tutorial/Industry track proposal deadline: 06 June 2014

    Demo/Poster proposal deadline: 06 June 2014

    Submission deadline: 31 July 2014

    Notification of acceptance: 31 August 2014

    Camera-ready deadline: 01 October 2014

PUBLICATION

Official conference proceedings of ICTCC 2014 will appear in the Lecture
Notes of ICST (LNICST) series jointly published by ICST and Springer and
indexed in DBLP, Google Scholar, ISI Proceedings, EI, CrossRef and
Zentralblatt Math.

All papers, but particularly those nominated for the Best Paper
competition, will be automatically considered for publication in an
expanded form in the special issues of Springer Mobile Networks and
Applications (MONET) journal (SCIE-indexed) and EAI endorsed Transactions
on Context-Aware Systems and Applications

--20cf301b65fb054fc204f49f716b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">=C2=A0<font face=3D"verdana, sans-serif">=
<span style=3D"color:rgb(0,0,0)">The International Conference on NaTure of =
Computation and Communication</span><br></font></div><pre style=3D"color:rg=
b(0,0,0)"><font face=3D"verdana, sans-serif">(ICTCC)

Location: Ho Chi Minh City, Vietnam
Time: 24-25 November 2014
Website: <a href=3D"http://ictcc.org/2014">http://ictcc.org/2014</a>

----

The ICTCC 2014 jointly organized by EAI and Nguyen Tat Thanh University
(NTTU) is a place for highly original ideas about how the nature is going
to shape computing systems of the future. Hence, it focuses on rigorous
approaches and cutting-edge solutions, which encompass three classes of
major methods:

    Those that take inspiration from nature for the development of novel
problem solving techniques;
    Those that are based on the use of computers or networks to synthesize
natural phenomena; and
    Those that employ natural materials (e.g., molecules,) to compute or
communicate.

Its purpose is to make a formal basis more accessible to researchers,
scientists, professionals and students as well as developers and
practitioners in ICT by providing them with state-of-the-art research
results, applications, opportunities and future trends.

We hope that the conference will receive many papers and the participation
of a large number of students, researchers, and professionals from all over
the world.

Original papers are solicited for the ICTCC 2014. In particular,
theoretical contributions should be formally stated and justified, and
practical applications should be based on their firm formal basis.
Suggested topics include, but are not limited to, the following:
SCOPE OF TOPICS:

    Autonomic computing/communicating
    Amorphous computing
    Biologically-inspired computing/communicating
    Cellular automata
    Cellular computing
    Collective intelligence in computing/communicating
    Collision-based computing
    Computation/communication based on chaos and dynamical systems
    Context-aware computing/communicating
    DNA computing
    Evolutionary computing
    Hypercomputation
    Massive parallel computing
    Membrane computing
    Molecular computing
    Neural computing
    Optical computing
    Physarum computing
    Quantum computing
    Relativistic computing
    Spatial computing
    Swam intelligence in computing/communicating
    Wetware computing

HIGHLIGHTS

    The event is endorsed by the European Alliance for Innovation, a
leading community-based organization devoted to the advancement of
innovation in the field of ICT

    All accepted papers will be published by Springer and made available
through SpringerLink Digital Library, one of the world&#39;s largest scient=
ific
libraries

    Proceedings will be submitted for indexing by Google Scholar, ISI, EI
Compendex, Scopus and many more

IMPORTANT DATES

    Workshop proposals due: 01 April 2014

    Tutorial/Industry track proposal deadline: 06 June 2014

    Demo/Poster proposal deadline: 06 June 2014

    Submission deadline: 31 July 2014

    Notification of acceptance: 31 August 2014

    Camera-ready deadline: 01 October 2014

PUBLICATION

Official conference proceedings of ICTCC 2014 will appear in the Lecture
Notes of ICST (LNICST) series jointly published by ICST and Springer and
indexed in DBLP, Google Scholar, ISI Proceedings, EI, CrossRef and
Zentralblatt Math.

All papers, but particularly those nominated for the Best Paper
competition, will be automatically considered for publication in an
expanded form in the special issues of Springer Mobile Networks and
Applications (MONET) journal (SCIE-indexed) and EAI endorsed Transactions
on Context-Aware Systems and Applications</font></pre><pre style=3D"color:r=
gb(0,0,0)"><br></pre>
</div>

--20cf301b65fb054fc204f49f716b--

