Re: [nmrg] Proposed Description for UCAN BoF
"Michael Behringer (mbehring)" <mbehring@cisco.com> Fri, 16 May 2014 08:01 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 931661A00C9 for <nmrg@ietfa.amsl.com>; Fri, 16 May 2014 01:01:12 -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 GQU2yZHKcJbw for <nmrg@ietfa.amsl.com>; Fri, 16 May 2014 01:01:11 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 362721A0186 for <nmrg@irtf.org>; Fri, 16 May 2014 01:01:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2390; q=dns/txt; s=iport; t=1400227264; x=1401436864; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=VrtKd7r+Y35iW6j/F4zShKfsdV+L5RMQIULkqfIHvKA=; b=VTwjKMX2ny4Ln8DAw0FcZwwgCKKfvEUCnj7KyCh0pNYkzD8NTagEwPVu 2BteF32CJfXHlKyAC0A5OaVodbeh/Apt9f5JYGHb2MPMGbmlYLrLRMiyI tDCmMkmfHtLAwwEduSuGqnhPTb3cChAgjYdldbH+O9ArTpXrVval9K4MF 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AowGAEzFdVOtJA2K/2dsb2JhbABZgwZPWIJpp1QFBQGaHQEZeRZ0giUBAQEEIxFFDAQCAQgRBAEBAQICBh0DAgICHxEUAQgIAQEEDgUIiCUDEQ2sf54RDYYXF4EqhCuGZYFkFhsHBoJvNoEVBJdkgzGLcYVrgzdtgUM
X-IronPort-AV: E=Sophos;i="4.97,1065,1389744000"; d="scan'208";a="44382883"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-7.cisco.com with ESMTP; 16 May 2014 08:01:03 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s4G8137U001077 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 16 May 2014 08:01:03 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.213]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0123.003; Fri, 16 May 2014 03:01:03 -0500
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: Proposed Description for UCAN BoF
Thread-Index: Ac9wMTmclff2PD98TL+zuYSEfC0iCwAcnR8AAA4gFVA=
Date: Fri, 16 May 2014 08:01:02 +0000
Message-ID: <3AA7118E69D7CD4BA3ECD5716BAF28DF210A40D3@xmb-rcd-x14.cisco.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF210A0A1F@xmb-rcd-x14.cisco.com> <53751F4C.6050606@gmail.com>
In-Reply-To: <53751F4C.6050606@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.238.134]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/l8cRyQ_D2MtvSv7f93dEO_84UC4
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, 16 May 2014 08:01:12 -0000
Oh, gosh! Sorry about that, I just saw the empty "- description:" at the top, and didn't scroll down. Michael > -----Original Message----- > From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] > Sent: 15 May 2014 22:11 > To: Michael Behringer (mbehring) > Cc: nmrg@irtf.org > Subject: Re: Proposed Description for UCAN BoF > > 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 > >
- [nmrg] Proposed Description for UCAN BoF Michael Behringer (mbehring)
- Re: [nmrg] Proposed Description for UCAN BoF Brian E Carpenter
- Re: [nmrg] Proposed Description for UCAN BoF Michael Behringer (mbehring)
- Re: [nmrg] Proposed Description for UCAN BoF Benoit Claise