[nmrg] Fwd: UCAN BoF approved
Benoit Claise <bclaise@cisco.com> Thu, 12 June 2014 09:08 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 F0DCD1B279F for <nmrg@ietfa.amsl.com>; Thu, 12 Jun 2014 02:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level:
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 yugqbBuWUuBe for <nmrg@ietfa.amsl.com>; Thu, 12 Jun 2014 02:08:46 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F2151B279B for <nmrg@irtf.org>; Thu, 12 Jun 2014 02:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6279; q=dns/txt; s=iport; t=1402564126; x=1403773726; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=ekWWpGtlVE9ImKoeNQYLj7IcFFeA+6wNrIbE1MZeZl4=; b=HinGcpgVEAUJbUxxPfQGOL5thzrGN0f/oBnWrrOTnFhQYjD7e0QG4PAF eF2dfLDzujt2ZLYKfZ0Qr3dOuN5hDDDsz6awikInRdfEC9zhbdXJHwTeO dPiI54A6K0CFL+Au5EaL7L3dEdTu0zbaXazCLAraq9sqnlaSa1HA3YA4T k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmsFANJsmVOtJssW/2dsb2JhbABag1+qJQEBAQEBAQUBmR4BgSB1hAMBAQEEbgYEDQQcAwECChYPCQMCAQIBOwIIBg0GAgEBFgGIJw3RSReFXIgdEQE/GAaEOwSaMoFDhTeMWIM+O4E5
X-IronPort-AV: E=Sophos; i="5.01,463,1400025600"; d="scan'208,217"; a="83540889"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 12 Jun 2014 09:08:44 +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 s5C98h7I003126 for <nmrg@irtf.org>; Thu, 12 Jun 2014 09:08:43 GMT
Message-ID: <53996E1B.7030100@cisco.com>
Date: Thu, 12 Jun 2014 11:08:43 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "nmrg@irtf.org" <nmrg@irtf.org>
References: <53996DD0.8080604@cisco.com>
In-Reply-To: <53996DD0.8080604@cisco.com>
X-Forwarded-Message-Id: <53996DD0.8080604@cisco.com>
Content-Type: multipart/alternative; boundary="------------040007030402020404080407"
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/rbl5iENVTdjQwE-lCVLFG-3O3F4
Subject: [nmrg] Fwd: UCAN BoF approved
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, 12 Jun 2014 09:08:48 -0000
Dear all, Forwarded here, as - I don't like cross-posting - It relates to NMRG Let's have the discussion on the ANIMA mailing list. Regards, Benoit -------- Original Message -------- Subject: UCAN BoF approved Date: Thu, 12 Jun 2014 11:07:28 +0200 From: Benoit Claise <bclaise@cisco.com> To: anima@ietf.org Dear all, As the responsible AD, let me share the news: The IESG/IAB approved the UCAN BoF yesterday. Some concerns were discussed, which would need to addressed on this list, during the BoF preparation, or during the BoF: - What is the commonality between all the use cases? - How would the IETF attract people to work on this topic? For example, the operators. - Not sure there are universal solutions to the problem space, so it is not clear that we should work on the general rather than specific solutions - "100 people in the room is too optimistic", 30 is more realistic. I reduced it to 50 in the WIKI ACTION: this email should be forwarded to the homenet WG to attract more people IMO, a successful UCAN BoF would be: - You explain (draft-irtf-nmrg-autonomic-network-definitions <http://tools.ietf.org/html/draft-irtf-nmrg-autonomic-network-definitions>, draft-irtf-nmrg-an-gap-analysis <http://tools.ietf.org/html/draft-irtf-nmrg-an-gap-analysis>) and you set up the stage on what AN is and what AN is not. The second part is equally important, when I see your BoF description "The fundamental goal of Autonomic Networking (AN) is self-management, including self-configuration, self-optimization, self-healing and self-protection. " - You provide the criteria for which use cases are in scope. - You review the different use cases, and try to classify them. - You try to deduce commonality/requirements between use cases or you decide on which specific pain points you want to work on. - You provide examples of protocol work you envision *This Bof is accepted, however this is a conditional acceptance*: BoF accepted at the condition that the proponents put some serious energy to finish the 2 NMRG drafts. Regards, Benoit
- [nmrg] Fwd: UCAN BoF approved Benoit Claise