IETF Logo Mail Archive

Re: [nmrg] Proposed Description for UCAN BoF

Benoit Claise <bclaise@cisco.com> Fri, 06 June 2014 10:36 UTC

Return-Path: <bclaise@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 5DCC81A0456 for <nmrg@ietfa.amsl.com>; Fri, 6 Jun 2014 03:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level:
X-Spam-Status: No, score=-10.152 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.651, 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 z9NKYzK4FvoJ for <nmrg@ietfa.amsl.com>; Fri, 6 Jun 2014 03:36:05 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A70631A044B for <nmrg@irtf.org>; Fri, 6 Jun 2014 03:36:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1597; q=dns/txt; s=iport; t=1402050958; x=1403260558; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=lQNJwKMFHgtwnkSo7zCbqsay357+ECsDlmx1N6vrsuI=; b=l8cxZ8Z8yxYJmcxZWzg+BaE35GdWlNzvHBSV5++RWWA8v5aqFuEtsXqB M2tmxL8iT7G15LWaF/PMkA2SgwqyXQQ3XR6wYIOVMk612bEi7+xCydJBl bUIuGduG3suNPUHCpo1mzUDAnq8IG6v3ItdRUVokCYjF2pRQ/gjM1KKyI c=;
X-IronPort-AV: E=Sophos;i="4.98,988,1392163200"; d="scan'208";a="75822827"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 06 Jun 2014 10:35:56 +0000
Received: from [10.60.67.91] (ams-bclaise-89110.cisco.com [10.60.67.91]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s56AZuxv000788; Fri, 6 Jun 2014 10:35:56 GMT
Message-ID: <5391998C.7010606@cisco.com>
Date: Fri, 06 Jun 2014 12:35:56 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Michael Behringer (mbehring)" <mbehring@cisco.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF210A0A1F@xmb-rcd-x14.cisco.com> <53751F4C.6050606@gmail.com>
In-Reply-To: <53751F4C.6050606@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/du6Dxp6cejlzbK8yZSWaRk39DoU
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: Fri, 06 Jun 2014 10:36:06 -0000

On 15/05/2014 22:10, Brian E Carpenter wrote:
> 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.
If you guys think so, update the BoF description.

Regards, B.
>
> 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
>>
> _______________________________________________
> nmrg mailing list
> nmrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nmrg
>

v2.23.0 | Report a Bug | By Email