Protocol to Access White Space (PAWS) Database: Use Cases and Requirements
draft-ietf-paws-problem-stmt-usecases-rqmts-14

The information below is for an old version of the document
Document Type Active Internet-Draft (paws WG)
Last updated 2013-03-04
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document
Consensus Yes
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Has enough positions to pass.
Responsible AD Pete Resnick
IESG note Document Shepherd is Gabor Bajko (Gabor.Bajko@nokia.com).
Send notices to paws-chairs@tools.ietf.org, draft-ietf-paws-problem-stmt-usecases-rqmts@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
PAWS                                                     A. Mancuso, Ed.
Internet-Draft                                                    Google
Intended status: Informational                               S. Probasco
Expires: September 5, 2013                                      B. Patil
                                                           March 4, 2013

     Protocol to Access White Space (PAWS) Database: Use Cases and
                              Requirements
             draft-ietf-paws-problem-stmt-usecases-rqmts-14

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 whitespace information followed by use cases and
   requirements for that protocol.  Finally, requirements associated
   with the protocol are presented.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 September 5, 2013.

Copyright Notice

Mancuso, et al.         Expires September 5, 2013               [Page 1]
Internet-Draft          paws-use-cases-and-reqmts             March 2013

   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.  Terminology Used in this Document  . . . . . . . . . . . . . .  4
   3.  Problem Statement  . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Global Applicability . . . . . . . . . . . . . . . . . . .  6
     3.2.  Database Discovery . . . . . . . . . . . . . . . . . . . .  7
     3.3.  Device Registration  . . . . . . . . . . . . . . . . . . .  8
     3.4.  Protocol . . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.5.  Data Model Definition  . . . . . . . . . . . . . . . . . .  8
   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.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 20
Show full document text