Re: [Anima] Pete Resnick's No Objection on charter-ietf-anima-00-17: (with COMMENT)

Benoit Claise <bclaise@cisco.com> Sun, 02 November 2014 16:57 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7141A8979; Sun, 2 Nov 2014 08:57:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.194
X-Spam-Level:
X-Spam-Status: No, score=-13.194 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, 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 hQxLl5taxwd3; Sun, 2 Nov 2014 08:57:35 -0800 (PST)
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 7B0791A894A; Sun, 2 Nov 2014 08:57:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5743; q=dns/txt; s=iport; t=1414947454; x=1416157054; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=YPBdx8XM6JfyffGBwFyPIWWKTLOpWbL0WatUB0Ei5Nw=; b=TUHtQPUYg+bAbTGalPMCiyxcZA7KsLYnZxgnK5DVOs4X5IuX1BAuITND VPjIPEJx3NpHGNtYJsTSq88RQjBOG35FUbthh/rG7enLhM7e1fSlcB4QU SooO07/G2ycR/xyd2Faa+SAcIKi4MEerc2ZFkN/bDXd/ywgaq07Y4IM/u M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArQEAPBhVlStJssW/2dsb2JhbABZAxaDTFiIYcQ2h00CgSgBAQEBAX2EAwEBBHkQCw4KCSUPAkYGDQEHAQEFiDgNyQYBAQEBAQEBAQEBAQEBAQEBAQEBAQEXkD8BAT8QBxGEOgWWaYcYh3WOW4N5PC8BgQ6BPAEBAQ
X-IronPort-AV: E=Sophos;i="5.07,295,1413244800"; d="scan'208,217";a="233611958"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 02 Nov 2014 16:57:32 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id sA2GvWZC014025; Sun, 2 Nov 2014 16:57:32 GMT
Message-ID: <5456627C.30000@cisco.com>
Date: Sun, 02 Nov 2014 17:57:32 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <20141030144919.7222.58863.idtracker@ietfa.amsl.com> <54537DDF.4090103@cisco.com> <5453B5EF.2040107@qti.qualcomm.com>
In-Reply-To: <5453B5EF.2040107@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary="------------080506070703010604080909"
Archived-At: http://mailarchive.ietf.org/arch/msg/anima/kfhOsb74bI4kToFHSahtpuf5MjQ
Cc: The IESG <iesg@ietf.org>, anima@ietf.org
Subject: Re: [Anima] Pete Resnick's No Objection on charter-ietf-anima-00-17: (with COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Nov 2014 16:57:36 -0000

Hi Pete,

Done in the version 20, https://datatracker.ietf.org/doc/charter-ietf-anima/

Thanks an regards, Benoit
> On 10/31/14 5:17 AM, Benoit Claise wrote:
>> Pete,
>>> 9th paragraph:
>>>
>>>     Definition of a discovery functionality for autonomic functions
>>>
>>> I don't understand what that means. By "functionality" do you mean
>>> protocol?
>>>
>>> Brian's response: "Definition of a discovery protocol for autonomic
>>> nodes."
>> After some more investigation, this was discussed in 
>> http://www.ietf.org/mail-archive/web/anima/current/msg00454.html,
>>
>>     1) the choice of the term "functionality" instead of "protocol"
>>     was used on purpose as to avoid choosing _a priori_ the
>>     (de)composition in protocol(s). i.e. one _a posteriori_ /
>>     informed decision will be how to "group" the different
>>     functionality in one or more protocols (or extension of existing
>>     ones).
>>
>> I thought that Laurent had a valid argument.
>
> Then let's take a shot at rewriting it so that it's clear what the 
> intention is:
>
>    The goal of this working group shall be to develop one or more
>    protocol specifications (or extensions to existing protocols) to
>    address the following problem areas. These were selected to according
>    to the analyzed technical gaps in draft-irtf-nmrg-an-gap-analysis:
>
>    o Discovery for autonomic nodes
>
>    o Negotiation for autonomic nodes
>       Starting point: draft-jiang-config-negotiation-protocol
>
>    o Bootstrapping a trust infrastructure
>       Starting point: draft-pritikin-bootstrapping-keyinfrastructures
>
>    o Separated Autonomic Control Plane
>       Starting point: draft-behringer-autonomic-control-plane
>
> pr
> -- 
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478