Re: [Anima] Call for Volunteer - ANIMA signaling design team

[Brian E Carpenter <[e-mail]>]

Laurent,

Can you be specific about what is unclear? Can you reduce it to individual issues, which we can track at
http://trac.tools.ietf.org/wg/anima/trac/wiki/Open%20Issues even before the team has officially started?

Also - how things fit together is the topic of https://tools.ietf.org/html/draft-behringer-anima-reference-model-01 so maybe
that is where we should add explanations.

(To be vey specific about my thoughts, the only way to tell whether the proposed signaling protocol is adequate is to do what is
described in the design team charter: confront it with some of the use cases, as described in the two initial goals.)

Regards
   Brian

On 01/05/2015 02:49, Laurent Ciavaglia wrote:
> Dear Sheng, all,
> 
> I would like to volunteer for the ANIMA signaling design team.
> However, the mission statement (as described below) is not fully clear to me, thus I would suggest we (ANIMA WG) spend some
> cycles to clarify the mission, the objectives and relationship with other components / work items of ANIMA.
> 
> Thanks, best regards, Laurent.
> 
> 
> On 27/04/2015 12:02, Sheng Jiang wrote:
>> Hi, all,
>>
>> We are calling for volunteers to form a design time for ANIMA signaling design team. The chairs has assigned two editors
>> (Brian Carpenter and Bing Liu), we are expecting up to 4 main contributors. The charter, initial goal and target date for the
>> signaling design team is introduced below. It also available in the design team wiki page.
>>
>> http://trac.tools.ietf.org/wg/anima/trac/wiki/Signaling
>>
>> Because of the intended design team work, we expect that the design team members would need to spend at least half a day per
>> week on this project for maybe 4..6 month, but it should become less afterwards. We would like to limit the design team to one
>> year (or shorter if the goals are reached faster of course).
>>
>> As WG chairs we will participate and help of course in the design team primarily for logistics. In principle, the design team
>> discussions should be open for all ANIMA participators. People who is interested, but do not have enough time to commit, could
>> also be able to participate and make contributions or comments.
>>
>> This call is last for one week. It ends May 3rd, Sunday. Please reply before it if you are interested in the commitment.
>>
>> Charter for the signaling design team
>>
>> The Anima WG charter states a requirement for discovery and negotiation mechanisms to enable closed-loop interaction between
>> autonomic nodes. It also states the goal of developing one or more protocol specifications (or extensions to existing
>> protocols) to achieve these goals. There is an existing draft requirements analysis, whose main points include
>>
>>     - support for any type of network objective parameter;
>>     - discovery must support any topology and bootstrap scenario;
>>     - synchronize parameters with other nodes individually or by flooding;
>>     - negotiate parameters with other nodes;
>>     - always secure.
>>
>> A simple TLV format is proposed for the protocol design. Binary or name-based discovery are proposed as alternative discovery
>> approaches.
>>
>> The purpose of the design team is to analyze these issues and recommend a combined approach to the working group, preferably
>> in the form of one draft or a small set of coordinated drafts. The proposed approach should be suitable for use by the
>> Autonomic Control Plane, and for other use cases including those listed in the Anima WG charter.
>>
>> In preparing the recommendation, the design team will verify and update the existing requirements and understand the relevant
>> use cases. However, documenting and solving use cases is out of scope for the design team. The design team is encouraged to
>> develop protocol walkthroughs and an abstract API as aids to understanding. The design team is not itself expected to produce
>> code, but ease of implementation is an important consideration.
>>
>> The draft(s) should be delivered by the July 2015 IETF (2015-07-06 cutoff date).
>>
>> Initial Goals
>>
>>     - Validate and update the existing list of requirements (​
>> http://tools.ietf.org/html/draft-carpenter-anima-gdn-protocol#section-2) against bootstrap and ACP drafts (and optionally
>> against other use case validation drafts). Target date: end May.
>>     - Recommend how the other milestone components of ANIMA (bootstrap, ACP, validation drafts) should use the signaling
>> protocol(s). As a side-effect, critique the proposal on the table (​
>> https://tools.ietf.org/html/draft-carpenter-anima-gdn-protocol#section-3).
>>
>> Target date: mid June.
>>
>> Best regards,
>>
>> Toerless + Sheng
>> _______________________________________________
>> Anima mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/anima
> 
> 
> 
> _______________________________________________
> Anima mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/anima
>