| Architecture v.s. Protocol (was: Re: [Lwapp] Another Way to Think about CAPWAP) | <– Date –> <– Thread –> |
|
From: James Kempf (kempf |
|
| Date: Tue, 18 Nov 2003 16:32:32 -0600 (CST) | |
>But I agree with Jerome (and the current charter)
>that we should be focusing on the requirements and architecture at the
>moment, without too much assumptions on any specific protocol solution.
That is what the current charter says. If we want the WG to get chartered,
we need to clarify the problem statement and work on refining the
architecture.
jak
- RE: Another Way to Think about CAPWAP, (continued)
- RE: Another Way to Think about CAPWAP Mani, Mahalingam (Mahalingam), November 18 2003
- RE: Another Way to Think about CAPWAP Sadot, Emek (Emek), November 18 2003
- RE: Another Way to Think about CAPWAP Pat R. Calhoun, November 18 2003
-
RE: Another Way to Think about CAPWAP Yang, Lily L, November 18 2003
- Architecture v.s. Protocol (was: Re: [Lwapp] Another Way to Think about CAPWAP) James Kempf, November 18 2003
- RE: Another Way to Think about CAPWAP Sadot, Emek (Emek), November 19 2003
- RE: Another Way to Think about CAPWAP Sadot, Emek (Emek), November 19 2003
- RE: Another Way to Think about CAPWAP Pat R. Calhoun, November 19 2003
- RE: Another Way to Think about CAPWAP Jerome Moisand, November 19 2003
Results generated by Tiger Technologies using MHonArc.