draft-ietf-paws-problem-stmt-usecases-rqmts-14.txt   draft-ietf-paws-problem-stmt-usecases-rqmts-15.txt 
PAWS A. Mancuso, Ed. PAWS A. Mancuso, Ed.
Internet-Draft Google Internet-Draft Google
Intended status: Informational S. Probasco Intended status: Informational S. Probasco
Expires: September 5, 2013 B. Patil Expires: September 14, 2013 B. Patil
March 4, 2013 March 13, 2013
Protocol to Access White Space (PAWS) Database: Use Cases and Protocol to Access White Space (PAWS) Database: Use Cases and
Requirements Requirements
draft-ietf-paws-problem-stmt-usecases-rqmts-14 draft-ietf-paws-problem-stmt-usecases-rqmts-15
Abstract Abstract
Portions of the radio spectrum that are assigned to a particular use Portions of the radio spectrum that are assigned to a particular use
but are unused or unoccupied at specific locations and times are but are unused or unoccupied at specific locations and times are
defined as "white space." The concept of allowing additional defined as "white space." The concept of allowing additional
transmissions (which may or may not be licensed) in white space is a transmissions (which may or may not be licensed) in white space is a
technique to "unlock" existing spectrum for new use. This document technique to "unlock" existing spectrum for new use. This document
includes the problem statement for the development of a protocol to includes the problem statement for the development of a protocol to
access a database of whitespace information followed by use cases and access a database of whitespace information followed by use cases and
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 5, 2013. This Internet-Draft will expire on September 14, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 2, line 24 skipping to change at page 2, line 24
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Introduction to White Space . . . . . . . . . . . . . . . 3 1.1. Introduction to White Space . . . . . . . . . . . . . . . 3
1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.1. In Scope . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.1. In Scope . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.2. Out of Scope . . . . . . . . . . . . . . . . . . . . . 4 1.2.2. Out of Scope . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology Used in this Document . . . . . . . . . . . . . . 4 2. Terminology Used in this Document . . . . . . . . . . . . . . 5
3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 5 3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Global Applicability . . . . . . . . . . . . . . . . . . . 6 3.1. Global Applicability . . . . . . . . . . . . . . . . . . . 6
3.2. Database Discovery . . . . . . . . . . . . . . . . . . . . 7 3.2. Database Discovery . . . . . . . . . . . . . . . . . . . . 7
3.3. Device Registration . . . . . . . . . . . . . . . . . . . 8 3.3. Device Registration . . . . . . . . . . . . . . . . . . . 8
3.4. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.4. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.5. Data Model Definition . . . . . . . . . . . . . . . . . . 8 3.5. Data Model Definition . . . . . . . . . . . . . . . . . . 9
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. Master-slave White Space Networks . . . . . . . . . . . . 9 4.1. Master-slave White Space Networks . . . . . . . . . . . . 9
4.2. Offloading: Moving Traffic to a White Space Network . . . 11 4.2. Offloading: Moving Traffic to a White Space Network . . . 11
4.3. White Space Serving as Backhaul . . . . . . . . . . . . . 13 4.3. White Space Serving as Backhaul . . . . . . . . . . . . . 13
4.4. Rapid Network Deployment During Emergencies . . . . . . . 14 4.4. Rapid Network Deployment During Emergencies . . . . . . . 14
4.5. White Space Used for Local TV Broadcaster . . . . . . . . 15 4.5. White Space Used for Local TV Broadcaster . . . . . . . . 15
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 16 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1. Data Model Requirements . . . . . . . . . . . . . . . . . 16 5.1. Data Model Requirements . . . . . . . . . . . . . . . . . 16
5.2. Protocol Requirements . . . . . . . . . . . . . . . . . . 17 5.2. Protocol Requirements . . . . . . . . . . . . . . . . . . 17
5.3. Operational Requirements . . . . . . . . . . . . . . . . . 19 5.3. Operational Requirements . . . . . . . . . . . . . . . . . 19
skipping to change at page 4, line 42 skipping to change at page 4, line 42
database when they change their locations or operating parameters. database when they change their locations or operating parameters.
This will allow them to receive permission to operate in their new This will allow them to receive permission to operate in their new
locations and/or with their new operating parameters, and to send locations and/or with their new operating parameters, and to send
acknowledgments to the database that include information on their new acknowledgments to the database that include information on their new
operating parameters. operating parameters.
1.2.2. Out of Scope 1.2.2. Out of Scope
The following topics are out of scope for this specification: The following topics are out of scope for this specification:
1. Co-existence and interference avoidance of white space devices 1. It is the device's responsibility to query the database for new
within the same spectrum. spectrum when the device moves, changes operating parameters,
loses connectivity, etc. Other synchronization mechanisms are
out of scope.
2. Provisioning (releasing new spectrum for white space use). 2. A rogue device may operate without contacting the database to
obtain available spectrum. Hence, enforcement of spectrum usage
by devices is out of scope.
3. The protocol defines communications between the database and
devices. The protocol for communications between devices is out
of scope.
4. Co-existence and interference avoidance of white space devices
within the same spectrum is out of scope.
5. Provisioning (releasing new spectrum for white space use) is out
of scope.
2. Terminology Used in this Document 2. Terminology Used in this Document
Database A database is an entity that contains current information Database A database is an entity that contains current information
about available spectrum at a given location and time as well as about available spectrum at a given location and time as well as
other types of information related to spectrum availability and other types of information related to spectrum availability and
usage. usage.
Device Class Identifies classes of devices including fixed, mobile, Device Class Identifies classes of devices including fixed, mobile,
portable, etc... May also indicate if the device is indoor or portable, etc... May also indicate if the device is indoor or
outdoor. outdoor.
Device ID An identifier for a device. Device ID An identifier for a device.
skipping to change at page 23, line 20 skipping to change at page 23, line 20
Mountain View, CA 94043 Mountain View, CA 94043
US US
Email: amancuso@google.com Email: amancuso@google.com
Scott Probasco Scott Probasco
Email: scott@probasco.me Email: scott@probasco.me
Basavaraj Patil Basavaraj Patil
2250 East President George Bush Highway
Richardson, TX 75082
US
Email: bpatil@ovi.com Email: basavpat@cisco.com
 End of changes. 10 change blocks. 
9 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/