Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC

The IESG <> Fri, 01 February 2013 13:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9FF2921F8B6C; Fri, 1 Feb 2013 05:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=-0.029, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id keYNOWszy1mD; Fri, 1 Feb 2013 05:24:22 -0800 (PST)
Received: from (localhost []) by (Postfix) with ESMTP id F050421F8B2B; Fri, 1 Feb 2013 05:24:21 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <>
Date: Fri, 01 Feb 2013 05:24:21 -0800
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 01 Feb 2013 13:24:22 -0000

The IESG has received a request from the Protocol to Access WS database
WG (paws) to consider the following document:
- 'Protocol to Access White Space (PAWS) Database: Use Cases and
  <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> as Informational

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2013-02-15. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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.  An obvious
   requirement is that these additional transmissions do not interfere
   with the assigned use of the spectrum.  One approach to using white
   space spectrum at a given time and location is to verify spectrum
   availability with a database that manages spectrum sharing and
   provides spectrum-availability information.  The IETF has undertaken
   to develop a Protocol to Access Spectrum Database [1] for such a
   management database.

   This document describes a number of possible use cases of white space
   spectrum and technology as well as a set of requirements for the
   database query protocol.  The concept of white spaces is described
   along with the problems that need to be addressed to enable white
   space spectrum for additional uses without causing interference to
   currently assigned use.  Use of white space is enabled by querying a
   database that stores information about spectrum availability at any
   given location and time.

The file can be obtained via

IESG discussion can be tracked via

The following IPR Declarations may be related to this I-D: