Securing LWAPP with DTLS
draft-kelly-capwap-lwapp-dtls-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Scott G. Kelly , Eric Rescorla | ||
| Last updated | 2005-12-13 | ||
| 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
The LWAPP protocol defines interactions between wireless termination points and wireless access controllers. Communications between these components must be secured, and the current specification provides for transport security using proprietary mechanisms which are embedded in the protocol. This document describes an alternative approach which eliminates the embedded security, and instead uses DTLS as a secure, tightly-integrated wrapper.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)