Re: The "nomap" Network Identifier Suffix

SM <sm@resistor.net> Wed, 27 November 2013 07:25 UTC

Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E7241AE22C for <ietf@ietfa.amsl.com>; Tue, 26 Nov 2013 23:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
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 zLkRBmznMyFK for <ietf@ietfa.amsl.com>; Tue, 26 Nov 2013 23:25:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CB7351AE159 for <ietf@ietf.org>; Tue, 26 Nov 2013 23:25:25 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id rAR7PCHo027938; Tue, 26 Nov 2013 23:25:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1385537119; bh=GcfxCBdWgWIs47e6Bi2EXtMYIgPfbxdJ1tTqXXgXxLc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hRT6HUQQtdGizsBV4ce5/zbGa8RGaHlTSiwey7vAU5as4fZEjnX82bxSZQeeXeeZC XlWyc68DnzhiMMPo+857Avv+qqhDndWPu0P6058Uz2lt7Tnb5mGNUI7LD8Ihk+51PJ naj5Z48NRsgyUwuO2+vgha0F84Om9C04fKU3Q3KY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1385537119; i=@resistor.net; bh=GcfxCBdWgWIs47e6Bi2EXtMYIgPfbxdJ1tTqXXgXxLc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=40dz/a4kdnLRy22giQsYJWDcYdXECOu7Kxi9P5iP/MXaQdDjuYZQRVT2XMBEzabJN xJiT8a9B7rY4bzz2E2356eegVbCrHPJ/FmipJMqxmpZ4wg/gmMlOhYf+eEOKqW2tmA mqMyZQQnitew+QivuEU8l0xX8SfNh2+SLqueOVbQ=
Message-Id: <6.2.5.6.2.20131126213911.0ccc26d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 26 Nov 2013 22:55:20 -0800
To: Richard Barnes <rlb@ipv.sx>, Mark Nottingham <mnot@mnot.net>, Bjoern Hoehrmann <derhoermi@gmx.net>
From: SM <sm@resistor.net>
Subject: Re: The "nomap" Network Identifier Suffix
In-Reply-To: <CAL02cgT2LPy37d4EdYtMzCAtT9Q458+ZEfsC1xshVS6j_tVJFg@mail.g mail.com>
References: <i9n799hrr1vfp4bobt9tc55rn1aip73rts@hive.bjoern.hoehrmann.de> <3D4E298A-FE87-4FD1-BCC2-EF33E7BD4D99@cs.georgetown.edu> <B15E89D0-3C72-4A5C-9838-BBF305D92A59@mnot.net> <CAL02cgT2LPy37d4EdYtMzCAtT9Q458+ZEfsC1xshVS6j_tVJFg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Eric Burger <eburger@cs.georgetown.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Nov 2013 07:25:27 -0000

At 19:51 26-11-2013, Richard Barnes wrote:
>be able to.  The people who would deploy this sort of policy 
>mechanism cannot change the 802.11 protocols their WiFi chipsets 
>use, but they *can* change an SSID or parse an SSID.  If you wait 
>IEEE to make a standard, and vendors to build it, and ... well, I'll 
>see you in a few years.

The proposal has been implemented in the Securifi Almond WiFi 
Router.  It is also supported by Mozilla and Google.

draft-hoehrmann-nomap-00 does not contain any occurrence of the word 
"privacy".  According to the Dutch Data Protection Authority, "Google 
has complied with the requirement to inform those involved, both 
online and off-line, about the processing of WiFi data and about the 
possibility of registering their refusal by means of an opt-out 
possibility".  I suggest having some text to discuss the privacy 
angle.  The draft could discuss the pros and cons of the identifier convention.

>Yes, it's a hack, but the Internet lives on hacks.  And people are 
>using it, so what's the harm in documenting it?  To make an analogy, 
>how many RFCs for v4/v6 transition schemes do we have that slam an 
>IPv4 address into an IPv6 address?

A lot. :-)

Regards,
-sm