Protocol to Access White-Space (PAWS) Databases
draft-ietf-paws-protocol-13
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (paws WG)
|
|
Authors |
|
Vincent Chen
,
Subir Das
,
Lei Zhu
,
John Malyar
,
Pete McCann
|
|
Last updated |
|
2014-07-29
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Gabor Bajko
|
|
Shepherd write-up |
|
Show
(last changed 2014-02-04)
|
IESG |
IESG state |
|
Waiting for AD Go-Ahead::AD Followup
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Pete Resnick
|
|
Send notices to |
|
paws-chairs@tools.ietf.org, draft-ietf-paws-protocol@tools.ietf.org
|
IANA |
IANA review state |
|
Version Changed - Review Needed
|
PAWS V. Chen, Ed.
Internet-Draft Google
Intended status: Standards Track S. Das
Expires: January 31, 2015 Applied Communication Sciences
L. Zhu
Huawei
J. Malyar
iconectiv (formerly Telcordia Interconnection Solutions)
P. McCann
Huawei
July 30, 2014
Protocol to Access White-Space (PAWS) Databases
draft-ietf-paws-protocol-13
Abstract
Portions of the radio spectrum that are allocated to licensees are
available for non-interfering use. This available spectrum is called
"White Space." Allowing secondary users access to available spectrum
"unlocks" existing spectrum to maximize its utilization and to
provide opportunities for innovation, resulting in greater overall
spectrum utilization.
One approach to managing spectrum sharing uses databases to report
spectrum availability to devices. To achieve interoperability among
multiple devices and databases, a standardized protocol must be
defined and implemented. This document defines such a protocol, the
"Protocol to Access White Space (PAWS) Databases".
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 31, 2015.
Chen, et al. Expires January 31, 2015 [Page 1]
Internet-Draft paws-protocol July 2014
Copyright Notice
Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4
2.1. Conventions Used in This Document . . . . . . . . . . . . 4
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Multi-ruleset Support . . . . . . . . . . . . . . . . . . 7
4. Protocol Functionalities . . . . . . . . . . . . . . . . . . 8
4.1. Database Discovery . . . . . . . . . . . . . . . . . . . 9
4.2. PAWS Version . . . . . . . . . . . . . . . . . . . . . . 10
4.3. Initialization . . . . . . . . . . . . . . . . . . . . . 11
4.3.1. INIT_REQ . . . . . . . . . . . . . . . . . . . . . . 11
4.3.2. INIT_RESP . . . . . . . . . . . . . . . . . . . . . . 12
4.4. Device Registration . . . . . . . . . . . . . . . . . . . 13
4.4.1. REGISTRATION_REQ . . . . . . . . . . . . . . . . . . 14
4.4.2. REGISTRATION_RESP . . . . . . . . . . . . . . . . . . 15
4.5. Available Spectrum Query . . . . . . . . . . . . . . . . 16
4.5.1. AVAIL_SPECTRUM_REQ . . . . . . . . . . . . . . . . . 19
4.5.2. AVAIL_SPECTRUM_RESP . . . . . . . . . . . . . . . . . 21
4.5.3. AVAIL_SPECTRUM_BATCH_REQ . . . . . . . . . . . . . . 23
4.5.4. AVAIL_SPECTRUM_BATCH_RESP . . . . . . . . . . . . . . 26
4.5.5. SPECTRUM_USE_NOTIFY . . . . . . . . . . . . . . . . . 27
4.5.6. SPECTRUM_USE_RESP . . . . . . . . . . . . . . . . . . 28
4.6. Device Validation . . . . . . . . . . . . . . . . . . . . 29
4.6.1. DEV_VALID_REQ . . . . . . . . . . . . . . . . . . . . 30
4.6.2. DEV_VALID_RESP . . . . . . . . . . . . . . . . . . . 31
Show full document text