Subject: [Capwap] RE: Call For CAPWAP Objectives Draft Editor and Requirements Inpu t

From: "Wijnen, Bert (Bert)" <[email-masked]>
Date: Mon, 27 Sep 2004 13:38:34 +0200

CAPWAP WG participants,

   I like this initiative of the WG chairs to get this work going.
   But let me clarify:

   The WG charter does NOT yet include this activity. And I as a
   single AD cannot approve it, that is an IESG task.

   However, while the WG chairs, ADs and IESG are discussing the
   rechartering, the individuals of the WG of course can start working
   on things that seem obvious and usefull. Then by the time the charter
   gets approved, you may already have a good chunck of work done.

   So pls do not stop working while we are working the admin side.

Bert

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: Saturday, September 25, 2004 01:12
> To: [email-masked]
> Cc: [email-masked]; [email-masked]; [email-masked];
> [email-masked]
> Subject: Call For CAPWAP Objectives Draft Editor and 
> Requirements Input
> 
> 
> Hi All-
> 
> The chairs are now finalizing the re-charter proposal with 
> the ADs and Bert gave us the go-ahead to get started on the 
> Objectives draft.  We are looking for volunteers (by 
> Wednesday, 9/29) for editor of the CAPWAP Objectives draft.  
> This draft is a requirements draft for the CAPWAP protocol 
> and will define requirements in the form of Objectives, as 
> was discussed and agreed upon during the last IETF meeting:
> 
> Define a set of Objectives based on the architecture taxonomy 
> work that lists the requirements for an interoperable CAPWAP 
> protocol. This document will:
> 	a. Address the problems stated in the CAPWAP Problem 
> statement draft  
> 	b. Describe each objective, its benefit to the protocol 
> and how it satisfies the problem statement.
> 	c. Prioritize and classify the objectives into 3 categories:
> 		i.   Mandatory and Accepted 
> 		ii.  Desirable
> 		iii. Rejected
> 	d. Undergo review in IEEE as needed.
> 
> A risk in developing protocols by the "requirements"  
> approach is this phase tends to drag out and stalemate 
> occurs.  In order to prevent this, we will impose a hard 
> limit on the protocol requirements phase.  Bert has suggested 
> that if we can't meet this hard deadline, the WG will close.
> 
> With this in mind, the Objective draft editor will need to 
> meet the following deadlines.
> 	- first draft submitted by IETF 61.
> 	- Submission of the Objectives draft to IESG by Apr/May 
> 2005.  (To be finalized in the Charter)
> 
> If you do volunteer, please make sure you are availiable and 
> willing to put in the time required to meet these dates.   
> Please volunteer by Wednesday, 9/29, so we can get started on 
> this draft quickly.  
> 
> Thanks,
> Dorothy and Mani
> 
_______________________________________________
Capwap mailing list
[email-masked]
http://mail.frascone.com/mailman/listinfo/capwap