Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-TGAF] Fw: [ieee-ietf-coord] FW: [paws] LastCall: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol toAccess White Space (PAWS) Database: UseCases and Requirements) to Informational RFC



FYI,
  If you have a comment for the IETF please let them know, and please cc
Dorothy Stanley as well.
Thanks,
Jon

----- Original Message ----- From: "Romascanu, Dan (Dan)" <dromasca@xxxxxxxxx>
To: <ieee-ietf-coord@xxxxxxxx>
Sent: Monday, February 04, 2013 2:04 AM
Subject: [ieee-ietf-coord] FW: [paws] LastCall: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol toAccess White Space (PAWS) Database: UseCases and Requirements) to Informational RFC


This document is relevant to item #9 in the list of the areas of cooperation between the IETF and IEEE 802. Please make sure that all relevant IEEE 802 WGs are aware about the ongoing IETF Last Call.

Thanks and Regards,

Dan




-----Original Message-----
From: paws-bounces@xxxxxxxx [mailto:paws-bounces@xxxxxxxx] On Behalf Of The IESG
Sent: Friday, February 01, 2013 3:24 PM
To: IETF-Announce
Cc: paws@xxxxxxxx
Subject: [paws] 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 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
  Requirements'
<draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> as Informational RFC

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 ietf@xxxxxxxx mailing lists by 2013-02-15. Exceptionally, comments may be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning of the Subject line to allow automated sorting.

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.  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
http://datatracker.ietf.org/doc/draft-ietf-paws-problem-stmt-usecases-rqmts/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-paws-problem-stmt-usecases-rqmts/ballot/


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

  http://datatracker.ietf.org/ipr/1614/



_______________________________________________
paws mailing list
paws@xxxxxxxx
https://www.ietf.org/mailman/listinfo/paws
_______________________________________________
ieee-ietf-coord mailing list
ieee-ietf-coord@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ieee-ietf-coord