Architecture for Control and Provisioning of Wireless Access Points(CAPWAP)
draft-mani-capwap-arch-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mahalingam Mani , Bob O'Hara | ||
Last updated | 2003-10-22 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
While conventional wisdom has it that Wireless Access Points are strictly Layer 2 bridges, such devices today perform some higher layer functions of routers or switches in wired Infrastructure in addition to bridging the wired and wireless networks. For example, in 802.11 networks, Access Points can function as Network Access Servers. For this reason, Access Points have IP addresses and can function as IP devices.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)