Re: [nmrg] Comments on autonomic use cases

Joe Marcus Clarke <jclarke@cisco.com> Fri, 14 March 2014 05:12 UTC

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