[paws] RFC 7545 on Protocol to Access White-Space (PAWS) Databases
rfc-editor@rfc-editor.org Wed, 20 May 2015 00:52 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: paws@ietfa.amsl.com
Delivered-To: paws@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 886A51ACE36; Tue, 19 May 2015 17:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rB1kxK1SbOul; Tue, 19 May 2015 17:52:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6C48D1ACE29; Tue, 19 May 2015 17:52:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3A648180452; Tue, 19 May 2015 17:50:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150520005053.3A648180452@rfc-editor.org>
Date: Tue, 19 May 2015 17:50:53 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/paws/huGlNzciIz1b_3mYe0fv5lNPfYg>
Cc: paws@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [paws] RFC 7545 on Protocol to Access White-Space (PAWS) Databases
X-BeenThere: paws@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Protocol to Access White Space database \(PAWS\)" <paws.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/paws>, <mailto:paws-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/paws/>
List-Post: <mailto:paws@ietf.org>
List-Help: <mailto:paws-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/paws>, <mailto:paws-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 May 2015 00:52:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7545
Title: Protocol to Access White-Space (PAWS)
Databases
Author: V. Chen, Ed., S. Das, L. Zhu,
J. Malyar, P. McCann
Status: Standards Track
Stream: IETF
Date: May 2015
Mailbox: vchen@google.com,
sdas@appcomsci.com,
lei.zhu@huawei.com,
jmalyar@iconectiv.com,
peter.mccann@huawei.com
Pages: 90
Characters: 188634
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-paws-protocol-20.txt
URL: https://www.rfc-editor.org/info/rfc7545
DOI: http://dx.doi.org/10.17487/RFC7545
Portions of the radio spectrum that are allocated to licensees are
available for non-interfering use. This available spectrum is called
"white space". Allowing secondary users access to available spectrum
"unlocks" existing spectrum to maximize its utilization and to
provide opportunities for innovation, resulting in greater overall
spectrum utilization.
One approach to managing spectrum sharing uses databases to report
spectrum availability to devices. To achieve interoperability among
multiple devices and databases, a standardized protocol must be
defined and implemented. This document defines such a protocol, the
"Protocol to Access White-Space (PAWS) Databases".
This document is a product of the Protocol to Access WS database Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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