IETF Logo Mail Archive

Re: [paws] WG Review: Protocol to Access White Space database (paws)

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 20 April 2011 15:41 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5EC4DE07ED; Wed, 20 Apr 2011 08:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rejY80qsxMqn; Wed, 20 Apr 2011 08:40:59 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes.out.tigertech.net [74.114.88.72]) by ietfc.amsl.com (Postfix) with ESMTP id F3366E06C4; Wed, 20 Apr 2011 08:40:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 4ECAF430107; Wed, 20 Apr 2011 08:40:56 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-50-206.clppva.btas.verizon.net [71.161.50.206]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 2BCD74300F7; Wed, 20 Apr 2011 08:40:55 -0700 (PDT)
Message-ID: <4DAEFE86.7030000@joelhalpern.com>
Date: Wed, 20 Apr 2011 11:40:54 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>, <4DADFE6D.3050107@cs.tcd.ie>, <88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com> <BLU152-w2BA09DCB1336E2DDEF33E93930@phx.gbl>
In-Reply-To: <BLU152-w2BA09DCB1336E2DDEF33E93930@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: paws@ietf.org, "iesg@ietf.org" <iesg@ietf.org>, ietf@ietf.org, scott.probasco@nokia.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2011 15:41:00 -0000

Building from Bernard's note, it strikes me that if we are going to get 
into device identity, we probably need to be communicating with (liaise) 
3GPP/3GPP2, because they have very strong views on that topic.  (Whether 
one agrees or disagrees with their biases, talking to them seems important.)

Yours,
Joel

On 4/20/2011 10:55 AM, Bernard Aboba wrote:
> When I hear the term "device identity spoofing", IEEE 802.1ar comes to
> mind (see http://standards.ieee.org/getieee802/download/802.1AR.-2009.pdf).
>
> In addition to the liaisons with IEEE 802.19, 802.22 and IEEE 802.11af,
> is there a liaison contemplated to IEEE 802.1 relating to "device identity"?
>

v2.23.0 | Report a Bug | By Email