Protocol to Access White Space Database:Security Considerations
draft-wu-paws-secutity-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yizhuang Wu, Yang Cui | ||
| Last updated | 2013-04-25 (Latest revision 2012-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
This document analyses common security threats of the Protocol to Access White Space database (PAWS), and describes their potential impacts on message exchanges between master device and white space database when implementing PAWS. Meanwhile, the corresponding countermeasures are also introduced in this document. The PAWS is used for retrieving the available white space information at a given location and time from a white space database.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)