Re: [secdir] Secdir Review of draft-ietf-paws-protocol

Catherine Meadows <> Tue, 08 July 2014 16:17 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 87E9C1B2B88; Tue, 8 Jul 2014 09:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id f0AVti-PUJsU; Tue, 8 Jul 2014 09:17:52 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CDB901B2B87; Tue, 8 Jul 2014 09:17:51 -0700 (PDT)
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id s68GHo2D024037 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Jul 2014 12:17:50 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_881663D6-920F-4515-98FE-B506B5772880"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Catherine Meadows <>
In-Reply-To: <>
Date: Tue, 08 Jul 2014 12:17:50 -0400
Message-Id: <>
References: <>
X-Mailer: Apple Mail (2.1878.6)
X-CCS-MailScanner: No viruses found.
X-CCS-MailScanner-Info: See:
Subject: Re: [secdir] Secdir Review of draft-ietf-paws-protocol
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 08 Jul 2014 16:17:53 -0000

I am resending this, because I got one of the email addresses wrong.


Catherine Meadows
Naval Research Laboratory
Code 5543
4555 Overlook Ave., S.W.
Washington DC, 20375
phone: 202-767-3490
fax: 202-404-7942

On Jul 8, 2014, at 12:10 PM, Catherine Meadows <> wrote:

> I have reviewed this document as part of the security directorate's 
> ongoing effort to review all IETF documents being processed by the 
> IESG.  These comments were written primarily for the benefit of the 
> security area directors.  Document editors and WG chairs should treat 
> these comments just like any other last call comments.
> This ID describes a protocol, PAWS,  that allows wireless devices to access currently unused portions of the radio spectrum.
> The protocol works between a geospatial database and a device with geolocation capabilities.  The device reports its location
> and other relevant information to the database, which in turns gives it information about which portions of the spectrum is available to it.
> This removes the responsibility for managing the complex information about spectrum available from the device and to the database,
> which is better equipped to handle it.  
> The ID has a very thorough and well-written Security Considerations section, which  covers the security threats against such a protocol.  They identify two
> main threats
>  By using the PAWS protocol, the Master Device and the Database expose
> themselves to the following risks:
> o Accuracy: The Master Device receives incorrect spectrum availability
> information.
> o Privacy: An unauthorized entity intercepts identifying data for
> the Master Device or its Slave Devices, such as serial number and
> location.
> Note that core PAWS does not address client authentication, on the grounds that unauthorized clients could find out the existence of white
> space on their own without the help of PAWS, and in that case there would be nothing preventing them from using it. The ID does point out though that client authentication may be required by specific regulatory domains,
> and so it is possible for the Database to require client authentication, e.g. by TLS.  The authors appropriately point out the limitations of using TLS for authentication, particularly
> when the keys are trusted to small ubiquitous devices.   
> I believe this draft is ready.
> Catherine Meadows
> Naval Research Laboratory
> Code 5543
> 4555 Overlook Ave., S.W.
> Washington DC, 20375
> phone: 202-767-3490
> fax: 202-404-7942
> email: