Fwd: Second Last Call: <draft-ietf-paws-protocol-14.txt> (Protocol to Access White-Space (PAWS) Databases) to Proposed Standard

Mark Nottingham <mnot@mnot.net> Thu, 07 August 2014 00:51 UTC

Resent-Date: Thu, 07 Aug 2014 00:48:03 +0000
Resent-Message-Id: <E1XFBsB-0006jW-Ap@frink.w3.org>
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 07 Aug 2014 10:47:18 +1000
References: <20140806210932.26762.11590.idtracker@ietfa.amsl.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <111B5E38-C232-4C8A-9DDC-6166C8DEE788@mnot.net>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Received-SPF: pass client-ip=216.86.168.183; envelope-from=mnot@mnot.net; helo=mxout-08.mxes.net
Subject: Fwd: Second Last Call: <draft-ietf-paws-protocol-14.txt> (Protocol to Access White-Space (PAWS) Databases) to Proposed Standard
Archived-At: <http://www.w3.org/mid/111B5E38-C232-4C8A-9DDC-6166C8DEE788@mnot.net>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

FYI. This document is using HTTPS here:
  http://tools.ietf.org/html/draft-ietf-paws-protocol-14#section-7

Anyone care to review? After a quick scan, it appears to be profiling HTTP a bit, and I note it doesn't seem define a media type for its payload.

Cheers,


Begin forwarded message:

> From: The IESG <iesg-secretary@ietf.org>
> Subject: Second Last Call: <draft-ietf-paws-protocol-14.txt> (Protocol to Access White-Space (PAWS) Databases) to Proposed Standard
> Date: 7 August 2014 7:09:32 am AEST
> To: IETF-Announce <ietf-announce@ietf.org>
> Cc: paws@ietf.org
> Reply-To: ietf@ietf.org
> Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/y770cFpNzb_B5r4AFg1q5uFHQ0Y
> 
> 
> 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) Databases'
>  <draft-ietf-paws-protocol-14.txt> as Proposed Standard
> 
> A prior Last Call was made for version -12 of this document. Comments
> received during that discussion lead to extensive edits to the document,
> which could benefit from a second review.
> 
> 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@ietf.org mailing lists by 2014-08-20. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>   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".
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-paws-protocol/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-paws-protocol/ballot/
> 
> 
> The following IPR Declarations may be related to this I-D:
> 
>   http://datatracker.ietf.org/ipr/2203/
>   http://datatracker.ietf.org/ipr/2340/
>   http://datatracker.ietf.org/ipr/2239/
> 
> 
> 

--
Mark Nottingham   https://www.mnot.net/

Fwd: Second Last Call: <draft-ietf-paws-protocol-… Mark Nottingham