RFC 6953 on Protocol to Access White-Space (PAWS) Databases: Use Cases and Requirements

rfc-editor@rfc-editor.org Wed, 22 May 2013 15:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06A4521F90F1; Wed, 22 May 2013 08:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.326
X-Spam-Level:
X-Spam-Status: No, score=-102.326 tagged_above=-999 required=5 tests=[AWL=0.274, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3B8AG2MjP1P; Wed, 22 May 2013 08:28:29 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 90D9621F90EE; Wed, 22 May 2013 08:28:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 496C7B1E009; Wed, 22 May 2013 08:27:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6953 on Protocol to Access White-Space (PAWS) Databases: Use Cases and Requirements
From: rfc-editor@rfc-editor.org
Message-Id: <20130522152756.496C7B1E009@rfc-editor.org>
Date: Wed, 22 May 2013 08:27:56 -0700
Cc: paws@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 15:28:30 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6953

        Title:      Protocol to Access White-Space (PAWS) 
                    Databases: Use Cases and Requirements 
        Author:     A. Mancuso, Ed.,
                    S. Probasco, B. Patil
        Status:     Informational
        Stream:     IETF
        Date:       May 2013
        Mailbox:    amancuso@google.com, 
                    scott@probasco.me, 
                    basavpat@cisco.com
        Pages:      23
        Characters: 53560
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-paws-problem-stmt-usecases-rqmts-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6953.txt

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

This document is a product of the Protocol to Access WS database Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC