[Roll] * one correction * Fwd: Formation of a Routing Protocol Design Team for ROLL

Begin forwarded message:

> From: JP Vasseur <jvasseur@cisco.com>
> Date: April 1, 2009 9:57:34 AM CEDT
> To: ROLL WG <roll@ietf.org>
> Subject: [Roll] Formation of a Routing Protocol Design Team for ROLL
>
> Dear WG,
>
> We have formed a new Design Team in the ROLL Working Group. Please  
> find below the charter and team members.
>
> Since some of you may not be familiar with the concept of a Design  
> Team, I would like to remind a few points:
>
> * The work produced by a Design Team has no special status in the WG  
> and is subject to WG consensus as any other individual submission
> * We ask the Design Team to request for input from the WG and to  
> provide regular updates on the progress: please send input requests  
> to the mailing list, post regular updates of the document to get a  
> chance to everybody to comment, ...
> * All: please provide input to the Design Team and copy the mailing  
> list.
>
> Design Team Members
> ###################
> 	Tim Winter (Editor)
> 	Pascal Thubert
> 	Stephen Dawson
> 	Kris Pister
> 	Thomas Clausen
> 	Jonathan Hui

	   Anders Brandt

>
> (Thanks to the DT members)
>
> Charter
> ######
>
> The charter is fairly simple: produce an IPv6 routing solution for  
> LLN (one of our new WG item) in light of the four application- 
> specific routing requirements documents:
> 	* draft-ietf-roll-urban-routing-reqs
> 	* draft-ietf-roll-industrial-routing-reqs
> 	* draft-ietf-roll-home-routing-reqs
> 	* draft-ietf-roll-building-routing-reqs
>
> The routing solution may either be based on an extension of an  
> existing routing protocol or a new protocol. In the former case, the  
> design team is expected to interact with the WG that is responsible  
> for the development of the protocol.
>
> Please make sure to be aligned with the ROLL terminology document  
> and provide input to their authors should new terms be introduced.
>
> According to our charter, it is asked to pay a particular attention  
> to the security and manageability aspects of the routing solution.
>
> The Design Team is not tasked to produce a MIB for the routing  
> solution.
>
> Milestones
> #########
>
> May 1: produce a first draft of the routing solution document
> IETF-75 meeting: produce a more complete version of the document by  
> the cut-off submission date for the IETF-75 meeting.
>
> The Design Team will be dissolved once the WG will have adopted a  
> routing solution document as a WG document (should it be the one  
> proposed by the WG or not).
>
> It is strongly encouraged to produce new version as the document  
> progress (each time a substantial change is made to the document).
>
> Thanks.
>
> JP.
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll