Re: [nmrg] Comments on autonomic use cases
"Michael Behringer (mbehring)" <mbehring@cisco.com> Mon, 10 March 2014 15:16 UTC
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, 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. 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
- [nmrg] Comments on autonomic use cases Joe Marcus Clarke
- Re: [nmrg] Comments on autonomic use cases Brian E Carpenter
- Re: [nmrg] Comments on autonomic use cases Michael Behringer (mbehring)
- Re: [nmrg] Comments on autonomic use cases Joe Marcus Clarke