| Re: status of CAPWAP | <– Date –> <– Thread –> |
|
From: Pat Calhoun (pacalhou) (pcalhoun |
|
| Date: Sun, 25 Jan 2009 23:00:42 -0800 (PST) | |
Correct Dan, but publication will have many unintended consequences. >From what I am being told, this is actively being addressed now, so I would prefer we hold off a little longer. CAPWAP is not the only document that is being held up. We already have the RFC numbers if anyone needs to reference them (e.g., EPCGlobal), and the latest drafts can be used for anyone actively developing. Personally, if we believe these need to be published today, then I would instead ask that we force the RFC Editor to adopt the old rules - which applied when the spec was written. PatC -----Original Message----- From: Dan Harkins [mailto:dharkins [at] lounge.org] Sent: Saturday, January 24, 2009 1:27 PM To: capwap [at] frascone.com Subject: [Capwap] status of CAPWAP Hi, Last week Mani wrote: By the way, following this, at the request of at least one of the authors, the three CAPWAP protocol drafts (the RFCs-to-be: 5415, -5416 and -5417) in the RFC-Ed queue have been requested to be placed on hold until this matter is resolved by way of an early work-around from IETF, under discussion in the IETF list. I am concerned about this. If any protocol needs to be able to evolve, and create derivative works, it is CAPWAP. Wireless networking is a rapidly changing field and having a "standard" that cannot change with it makes that "standard" pointless. I politely and respectfully ask the chairs to gauge WG consensus on the matter of what we want to do with our drafts with respect to RFC 5378 and then to instruct the editor(s) to follow that consensus. If the editor(s) refuse(s) then I would expect he/she/they to be replaced with someone who is willing to implement the will of the WG. These drafts are not any one person's or any one company's property and the hangups of any person or company shouldn't trump the will of the WG. regards, Dan. _________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/capwap Archives: http://lists.frascone.com/pipermail/capwap
-
status of CAPWAP Dan Harkins, January 24 2009
- Re: status of CAPWAP Dave Nelson, January 24 2009
- Re: status of CAPWAP Pat Calhoun (pacalhou), January 25 2009
-
Re: status of CAPWAP Dan Harkins, January 26 2009
- Re: status of CAPWAP Pat Calhoun (pacalhou), January 27 2009
- Re: status of CAPWAP Dan Harkins, January 27 2009
- Re: status of CAPWAP David Harrington, January 28 2009
Results generated by Tiger Technologies using MHonArc.