Protocol to Access White-Space (PAWS) Databases: Use Cases and Requirements
RFC 6953
|
| Document |
Type |
|
RFC - Informational
(May 2013; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 6953 (Informational)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Pete Resnick
|
|
IESG note |
|
Document Shepherd is Gabor Bajko (Gabor.Bajko@nokia.com).
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
IANA - Review Needed
|
|
IANA action state |
|
No IC
|
Internet Engineering Task Force (IETF) A. Mancuso, Ed.
Request for Comments: 6953 Google
Category: Informational S. Probasco
ISSN: 2070-1721
B. Patil
Cisco Systems
May 2013
Protocol to Access White-Space (PAWS) Databases:
Use Cases and Requirements
Abstract
Portions of the radio spectrum that are assigned to a particular use
but are unused or unoccupied at specific locations and times are
defined as "white space". The concept of allowing additional
transmissions (which may or may not be licensed) in white space is a
technique to "unlock" existing spectrum for new use. This document
includes the problem statement for the development of a protocol to
access a database of white-space information followed by use cases
and requirements for that protocol. Finally, requirements associated
with the protocol are presented.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6953.
Mancuso, et al. Informational [Page 1]
RFC 6953 PAWS Use Cases and Requirements May 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Introduction to White Space . . . . . . . . . . . . . . . 3
1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.1. In Scope . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.2. Out of Scope . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions Used in This Document . . . . . . . . . . . . . . 5
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 5
3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Global Applicability . . . . . . . . . . . . . . . . . . . 6
3.2. Database Discovery . . . . . . . . . . . . . . . . . . . . 8
3.3. Device Registration . . . . . . . . . . . . . . . . . . . 8
3.4. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.5. Data Model Definition . . . . . . . . . . . . . . . . . . 9
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. Master-Slave White-Space Networks . . . . . . . . . . . . 9
4.2. Offloading: Moving Traffic to a White-Space Network . . . 11
4.3. White Space Serving as Backhaul . . . . . . . . . . . . . 13
4.4. Rapid Network Deployment during Emergencies . . . . . . . 14
4.5. White Space Used for Local TV Broadcaster . . . . . . . . 15
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1. Data Model Requirements . . . . . . . . . . . . . . . . . 16
5.2. Protocol Requirements . . . . . . . . . . . . . . . . . . 17
5.3. Operational Requirements . . . . . . . . . . . . . . . . . 19
5.4. Guidelines . . . . . . . . . . . . . . . . . . . . . . . . 19
6. Security Considerations . . . . . . . . . . . . . . . . . . . 20
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.1. Normative References . . . . . . . . . . . . . . . . . . . 22
Show full document text