Capwap Mailing List: RE: Proposed WG Charter

[Bob O'Hara (bob]

Cheng,

I believe that the only one that can "approve" an IEEE standard is the
IEEE Standards Board.  The list of approved IEEE standards and
amendments is 802.11-1999, 802.11a-1999, 802.11b-1999, 802.11d-2001,
802.11g-2003, and 802.11h-2003.  Recommended Practice 802.11F-2003 is
also approved.

I cannot speak for the WG, but I would presume that the WG would decide
to include, or not, a newly approved IEEE 802.11 standard on a case by
case basis, dependent on both the impact of such inclusion or exclusion
on the market acceptance of the resultant IETF standard and the work to
incorporate support for the newly approved IEEE 802.11 standard.

 -Bob O'Hara
 

-----Original Message-----
From: Cheng Hong [mailto:hcheng [at] psl.com.sg] 
Sent: Sunday, September 21, 2003 11:34 PM
To: James Kempf; LWAPP
Subject: RE: [Lwapp] Proposed WG Charter


Hi Jak,

>   - Dependence on yet to be approved IEEE 802.11 work or drafts,

Would like to have some clarification on this. What is the definiation
of
the approved IEEE802.11 work or draft? Approved by who?

Also, if during the WG's time frame, new drafts was approved by IEEE,
should
the drafts in CAPWAP be modified accordingly?

BR

Cheng

> -----Original Message-----
> From: lwapp-admin [at] frascone.com [mailto:lwapp-admin [at] frascone.com]On
> Behalf Of James Kempf
> Sent: Saturday, August 30, 2003 3:22 AM
> To: LWAPP
> Subject: [Lwapp] Proposed WG Charter
>
>
> Folks,
>
> Below is a charter for the WG that Dorothy and I would like to propose
to
> Randy. Please send comments if you have any.
>
>             jak
>
> +++++++++++++++++++++++++++++++++++++++++++++++
> Control and Provisioning of Wireless Access Points (CAPWAP)
> ===============================================
>
> Area:
> -----
> OPS
>
> Chairs:
> -------
> TBD
>
> Mailing List:
> -------------
> List:               lwapp [at] frascone.com
> Subscribe:     lwapp-request [at] frascone.com
> Body:            subscribe in Subject line
> Archive:        http://mail.frascone.com/pipermail/public/lwapp/
>
> Description of Working Group:
> -----------------------------
> As the size and complexity of IEEE 802.11 wireless networks has
increased,
> problems in the deployment, management, and usability of these
> networks have
> become evident. draft-calhoun-capwap-problem-statement-00.txt
> describes some
> of those problems. In addition, security considerations have become
> increasingly important as IEEE 802.11 networks have been deployed in
> situations where their use in accessing sensitive data must be
restricted
> for business or other reasons. While there are many possible
approaches to
> solving these problems, most of them involve IP-level protocols in
some
> fashion. To the extent changes to existing IETF protocols are
necessary or
> new IP-level protocols must be standardized to facilitate
> interoperability,
> this work is an appropriate topic for the IETF.
>
> The charter of the CAPWAP Working Group is to investigate and design a
> protocol for the purpose of simplifying the deployment, management,
and
> usability of IEEE 802.11 wireless networks. The Working Group will
attempt
> to utilize existing IETF protocols where possible, but will engage in
new
> design if necessary. The Working Group's designs will focus on the
"split
> AP" architecture. The split AP architecture centralizes
> processing of access
> point (AP) management functions, such as inter-AP configuration
> and control,
> and non-realtime host functions, such as data transport and host
> authentication, in a management entity, typically an access
> router (AR). The
> IEEE 802.11 APs continue to perform real-time host functions. The
split AP
> architecture does not involve any changes in IEEE 802.11 standards,
since
> the IEEE 802.11 specification says nothing about the architecture of
the
> IEEE 802.11 access point. This new architecture has been adopted by
many
> manufacturers, each with some variation. Creating an
> interoperable protocol
> between the AP and the AR will benefit the network operator community
by
> allowing operators to build networks with equipment from a collection
of
> vendors.
>
> Specific Working Group work items are:
>
>   - Clear problem statement and description of the split AP
architecture,
>   - CAPWAP security requirements, defining the needs for security
between
>     the AP and the AR, both for host data transport and for AP-AR
> signalling
>     and control,
>   - A protocol for implementing the split AP architecture, including
the
>     following functionality:
>     . Discovery of ARs by APs (this work should point to existing IETF
>       standards, if possible)
>     . Auto-organization of APs and ARs into a managed wireless
>       access network, including failover if an AR should fail,
>     . A tunneling protocol for IEEE 802.11 non-realtime host-related
>       signalling and data between the AP and the AR,
>     . Support for configuration of the AP by the AR, including secure
>       download and booting of code to the AP (some aspects of this
task
>       may involve existing IETF standards),
>     . Security for both tunneled host data and AR-AP signaling,
> as necessary
>       to address the requirements (this work may involve
> utilizing existing
>       IETF standards).
>
> The intent of the CAPWAP Working Group is to complete the protocol
> specification as quickly as possible and to serve as a forum for
> facilitating the testing of interoperability, in typical IETF fashion.
>
> While not specifically a work item, the Working Group will attempt to
make
> all designs as independent of the IEEE 802.11 radio protocol as
> possible, so
> that the protocol might, in the future be used with other radio
protocols.
> However, in any situation where a tradeoff between simplicity/speed of
> design completion and extensibility is required, the Working
> Group will opt
> for the former. The Working Group will also co-ordinate closely with
the
> IEEE 802.11 WG.
>
> Specific nongoals of this work are:
>
>   - Support for general, inter-subnet micromobility,
>   - Interoperable APIs for downloaded AP code images,
>   - Any IP-layer work that would require changes to the IEEE 802.11
MAC
> layer,
>   - Dependence on yet to be approved IEEE 802.11 work or drafts,
>   - Support for an inter-AP communication protocol, like IEEE 802.11f,
>   - Direct joint development of protocols with the IEEE 802.11 WG.
>
> Working Group protocol documents and the security requirements
> will be sent
> to the Security Area Advisory Group (SAAG) for review prior to
> submission to
> the IESG.
>
> Goals and Milestones:
> ---------------------
>
> Mar. 2004  Complete problem statement draft and architecture
> description and
>             submit to IESG for publication as Informational.
>
> Mar. 2004  Complete security requirements and submit to SAAG for
review.
>            Submit to IESG for publication as Informational when
> SAAG review
>            is complete.
>
> Nov. 2004  First draft of CAPWAP protocol complete and ready for
review.
>
> Mar. 2005  Complete CAPWAP protocol and submit to SAAG for review.
>            Submit to IESG for publication as Proposed Standard when
SAAG
>            review is complete.
>
>
>
>
> _______________________________________________
> Lwapp mailing list
> Lwapp [at] frascone.com
> http://mail.frascone.com/mailman/listinfo/lwapp
>

_______________________________________________
Lwapp mailing list
Lwapp [at] frascone.com
http://mail.frascone.com/mailman/listinfo/lwapp