Re: [nmrg] Comments on autonomic use cases

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 07 March 2014 10:02 UTC

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