Protocol to Access White-Space (PAWS) Databases
RFC 7545

 
Document Type RFC - Proposed Standard (May 2015; No errata)
Last updated 2015-05-19
Stream IETF
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Gabor Bajko
Shepherd write-up Show (last changed 2014-02-04)
IESG IESG state RFC 7545 (Proposed Standard)
Telechat date
Responsible AD Pete Resnick
IESG note This document had a second Last Call. There are unlikely to be more Last Call comments, so feel free to review before Last Call completes.
Send notices to paws-chairs@ietf.org, draft-ietf-paws-protocol@ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                      V. Chen, Ed.
Request for Comments: 7545                                        Google
Category: Standards Track                                         S. Das
ISSN: 2070-1721                           Applied Communication Sciences
                                                                  L. Zhu
                                                                  Huawei
                                                               J. Malyar
                                                               iconectiv
                                                               P. McCann
                                                                  Huawei
                                                                May 2015

            Protocol to Access White-Space (PAWS) Databases

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 is an Internet Standards Track document.

   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).  Further information on
   Internet Standards is available in 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/rfc7545.

Chen, et al.                 Standards Track                    [Page 1]
RFC 7545                          PAWS                          May 2015

Copyright Notice

   Copyright (c) 2015 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.

Chen, et al.                 Standards Track                    [Page 2]
RFC 7545                          PAWS                          May 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   5
     2.1.  Conventions Used in This Document . . . . . . . . . . . .   5
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Multi-ruleset Support . . . . . . . . . . . . . . . . . .   8
   4.  Protocol Functionalities  . . . . . . . . . . . . . . . . . .   9
     4.1.  Database Discovery  . . . . . . . . . . . . . . . . . . .  11
       4.1.1.  Preconfiguration  . . . . . . . . . . . . . . . . . .  11
       4.1.2.  Configuration Update: Database URI Changes  . . . . .  11
       4.1.3.  Error Handling  . . . . . . . . . . . . . . . . . . .  12
     4.2.  PAWS Version  . . . . . . . . . . . . . . . . . . . . . .  12
     4.3.  Initialization  . . . . . . . . . . . . . . . . . . . . .  12
       4.3.1.  INIT_REQ  . . . . . . . . . . . . . . . . . . . . . .  13
       4.3.2.  INIT_RESP . . . . . . . . . . . . . . . . . . . . . .  14
     4.4.  Device Registration . . . . . . . . . . . . . . . . . . .  15
       4.4.1.  REGISTRATION_REQ  . . . . . . . . . . . . . . . . . .  16
       4.4.2.  REGISTRATION_RESP . . . . . . . . . . . . . . . . . .  17
     4.5.  Available Spectrum Query  . . . . . . . . . . . . . . . .  18
       4.5.1.  AVAIL_SPECTRUM_REQ  . . . . . . . . . . . . . . . . .  21
       4.5.2.  AVAIL_SPECTRUM_RESP . . . . . . . . . . . . . . . . .  23
       4.5.3.  AVAIL_SPECTRUM_BATCH_REQ  . . . . . . . . . . . . . .  26
Show full document text