Re: [paws] Alissa Cooper's Discuss on draft-ietf-paws-protocol-14: (with DISCUSS and COMMENT)

Vincent Chen <vchen@google.com> Fri, 22 August 2014 20:28 UTC

Return-Path: <vchen@google.com>
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 6C1D61A0660 for <paws@ietfa.amsl.com>; Fri, 22 Aug 2014 13:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level:
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] 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 rUgOamLUNQGZ for <paws@ietfa.amsl.com>; Fri, 22 Aug 2014 13:28:41 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A3271A6F32 for <paws@ietf.org>; Fri, 22 Aug 2014 13:28:41 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id hq11so12917122vcb.16 for <paws@ietf.org>; Fri, 22 Aug 2014 13:28:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EvoFGGnLy2m3CkQvQOqx1nwfLdwaJb+RF3lHzchupGQ=; b=SQPxMMR0z5GJb2YbgL/Q2mPklYv2srkSdAzQ6YEt1JhQM2BSIzoLqO/R9vP826QEoZ dDOAjKC1vytuYcaPBIpAuPanTwJ1J/qNV55q4SYp5UEzmOV5mx6kfAkhF4eW/n9Dy5rc cDTriHmIQTaYeOLkWlzS3og8ZPCxnlBs65fANIyIk0l3jOlpoPyWCXtbok7+K8+KST1e ++A9mQD7f5mY+InKvsGROIcjaGVVsw3yBYtg2ZHx0gJrdZ+yfMnDJz0x81Z0LuCNp8pK f3n4DZoJ65v/XoADvQR+GMXpgQRMYsfmLrLvMPjj3p7WoGX9GV2bOgfzVAc6GWrzE616 0r8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=EvoFGGnLy2m3CkQvQOqx1nwfLdwaJb+RF3lHzchupGQ=; b=b/1yukmL+jSOupj7kyUvk/nv2shma5AVH9235ENwQHN+XpFiorLchScGK7rr9hNboY PvRI1dSqXuZYgLgMc5YBaht4kKYQ2IW1uL6klvNw1mw50e7sQYOXS3PJwXfTmhQtWEs9 fHoCu+1h7D4XLvC/U29x8dJ2ln1YFR4V/+jaoB4OSz6Y5IU8MXRCVWgo/lzZ4GZW2WvL /MW0k36hjuS2VecwYIX1KnHwjxJ2vUBuUFl5dZlLaTJq9ZP1hSNIYuoynvlOPv1M7qIq 5A4o1YCQjyTPyBLQrY1fGVlB7/JKelDWg+IrGwVpkWwDJkMN5MhGmsc+Aq/pUQC8RSt4 mhDQ==
X-Gm-Message-State: ALoCoQmWGlbj3WDikkVGxO8mtPLlj52JACbW/j1Z5qLBOoLFwRh24OMdSNTZ4qFNMz5wQvkSy9DP
MIME-Version: 1.0
X-Received: by 10.220.172.8 with SMTP id j8mr2085039vcz.32.1408739320486; Fri, 22 Aug 2014 13:28:40 -0700 (PDT)
Received: by 10.52.177.226 with HTTP; Fri, 22 Aug 2014 13:28:40 -0700 (PDT)
In-Reply-To: <53F61768.7030007@qti.qualcomm.com>
References: <20140820165236.31862.86067.idtracker@ietfa.amsl.com> <CABEV9ROW=KhQDCU5=X+SrtPAAOwd0QgvKJh_-owQ4b1CvdNvog@mail.gmail.com> <53F61768.7030007@qti.qualcomm.com>
Date: Fri, 22 Aug 2014 13:28:40 -0700
Message-ID: <CABEV9RMXR6c4=dnCwQbU=6H97kzpT-rUTmpUD5+B1o0CtL4AeA@mail.gmail.com>
From: Vincent Chen <vchen@google.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary="001a11c3678cc7724d05013daea5"
Archived-At: http://mailarchive.ietf.org/arch/msg/paws/fFQk-TrhJ29h0nSa5v9MfqGBOXk
Cc: "paws@ietf.org" <paws@ietf.org>, "paws-chairs@tools.ietf.org" <paws-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-paws-protocol@tools.ietf.org
Subject: Re: [paws] Alissa Cooper's Discuss on draft-ietf-paws-protocol-14: (with DISCUSS and COMMENT)
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: Fri, 22 Aug 2014 20:28:43 -0000

On Thu, Aug 21, 2014 at 8:59 AM, Pete Resnick <presnick@qti.qualcomm.com>
wrote:

>  On 8/21/14 2:59 AM, Vincent Chen wrote:
>
> = Section 5.2 =
>> I'd like to discuss why the device serial number needs to be included in
>> the device descriptor, rather than some (perhaps persistent) randomly
>> generated device identifier that is used only in the context of this
>> protocol (which would better protect the privacy of the user of the
>> device, since the whitespaces database administrator wouldn't be able to
>> correlate the device's spectrum requests with other activities linked to
>> the serial number). It's not really clear why serial number is collected
>> since both this document and RFC 6953 note the protocol does not defend
>> against abuse or mis-use of spectrum.
>>
>
>  The regulator want to have the ability to black list ranges of serial
> numbers, if it
> determines that a series was defective. The Databases must use the serial
> number
> to determine it can return available spectrum.
>
>
> But that makes this a "required by ruleset but not by protocol" issue,
> right?
>

I think this comes back to the question you asked during the drafting of
RFC 6953:

>> Are there any potential implementers of this protocol (or potential
regulatory bodies) that *don't* care about [serial number], manufacturer or
model or etc.?

There were no solid answers to that question. I suppose the most flexible
is to make it optional at the
protocol layer and required by ruleset, as you suggest.


>
> pr
>
> --
> Pete Resnick <http://www.qualcomm.com/~presnick/> <http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>


-- 
-vince