IETF Logo Mail Archive

Re: [nmrg] Proposed Description for UCAN BoF

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 15 May 2014 20:11 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 519561A02C6 for <nmrg@ietfa.amsl.com>; Thu, 15 May 2014 13:11:04 -0700 (PDT)
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 bbHqZlCuLCmd for <nmrg@ietfa.amsl.com>; Thu, 15 May 2014 13:11:02 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 837161A02F3 for <nmrg@irtf.org>; Thu, 15 May 2014 13:10:52 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id lj1so1501166pab.22 for <nmrg@irtf.org>; Thu, 15 May 2014 13:10:45 -0700 (PDT)
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=AlZUgnqwGehe2Ub9Fqr/NlLPySDINEuyy8CUt7vW18Q=; b=k+Rnz2ixX8btzawyIhx2vmZDAJ8I9HPke6FU4+8s6VXXmZ/dwp9x7fLQRcVoYo2uEo zYdz9r2NnBe4zMo8Anrxc9HW0dHe+pY382j4RmkdcNx5ASLLB5E/Lon3rrdbax1uh4yF W5IZRAPhl0oD0h3I3SaLcQUZG1Nrr/ilKFW4SpOfeiy3pxT1hKf1y8cd9SWRKCjSdfWx ZqZ1IdP4quyyyhNI51Pv7u/ljczy096Dmla3bEvQIpJk4JRm9MIOdrdHMSERzy3MPVZX /yMW4knS6ONOmmhLyfXqRJF6kZ/q1XLiZB+6e8t3ryYgrK73O65Vp/8VHp4E4RaWrP7M xqPg==
X-Received: by 10.68.192.193 with SMTP id hi1mr15301435pbc.108.1400184645433; Thu, 15 May 2014 13:10:45 -0700 (PDT)
Received: from [192.168.178.20] (101.200.69.111.dynamic.snap.net.nz. [111.69.200.101]) by mx.google.com with ESMTPSA id kj1sm10599959pbd.20.2014.05.15.13.10.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 15 May 2014 13:10:44 -0700 (PDT)
Message-ID: <53751F4C.6050606@gmail.com>
Date: Fri, 16 May 2014 08:10:52 +1200
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: "Michael Behringer (mbehring)" <mbehring@cisco.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF210A0A1F@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF210A0A1F@xmb-rcd-x14.cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/1nvjeiCqaB2ff1oKZ-K6sH86MMg
Cc: "nmrg@irtf.org" <nmrg@irtf.org>
Subject: Re: [nmrg] Proposed Description for UCAN BoF
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, 15 May 2014 20:11:04 -0000

Michael,

Don't you see the description at
http://trac.tools.ietf.org/bof/trac/wiki/WikiStart#UCANproposal ?
Browser refresh needed?

However, your text would be a useful addition I think.

Regards
   Brian

On 15/05/2014 23:52, Michael Behringer (mbehring) wrote:
> On the wiki (http://trac.tools.ietf.org/bof/trac/wiki/WikiStart#TimeframeIETF90Toronto) we don't have a description yet for the BoF we applied for. Let me propose here what I have in mind, for discussion: 
> 
> --
> Autonomic Networking focuses on self-management of network elements. An autonomic function works in a distributed way across various network elements, allowing however central guidance and reporting. Autonomic functions already exist today, for example IGP routing protocols such as OSPF. However, all such functions have their own discovery, messaging and security mechanisms. 
> 	
> This BoF collects and analyses use cases for Autonomic Networking.  The goal is to find commonalities between various use cases, to be able to determine generic requirements for Autonomic Networking functions and to conclude whether there is scope for a common, generic Autonomic Networking Infrastructure for all autonomic functions. 
> --
> 
> What do others want to get out of this BoF? Please provide input! 
> 
> Michael
>

v2.23.0 | Report a Bug | By Email