Re: The "nomap" Network Identifier Suffix

joel jaeggli <joelja@bogus.com> Wed, 27 November 2013 05:09 UTC

Return-Path: <joelja@bogus.com>
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 0F4141AE134 for <ietf@ietfa.amsl.com>; Tue, 26 Nov 2013 21:09:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 pW8t_I450FWs for <ietf@ietfa.amsl.com>; Tue, 26 Nov 2013 21:09:12 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 89B2B1AE12C for <ietf@ietf.org>; Tue, 26 Nov 2013 21:09:12 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id rAR596gJ057828 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 27 Nov 2013 05:09:06 GMT (envelope-from joelja@bogus.com)
Message-ID: <52957E6B.4060102@bogus.com>
Date: Tue, 26 Nov 2013 21:08:59 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:26.0) Gecko/20100101 Thunderbird/26.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>, Eric Burger <eburger@cs.georgetown.edu>
Subject: Re: The "nomap" Network Identifier Suffix
References: <i9n799hrr1vfp4bobt9tc55rn1aip73rts@hive.bjoern.hoehrmann.de> <3D4E298A-FE87-4FD1-BCC2-EF33E7BD4D99@cs.georgetown.edu> <B15E89D0-3C72-4A5C-9838-BBF305D92A59@mnot.net>
In-Reply-To: <B15E89D0-3C72-4A5C-9838-BBF305D92A59@mnot.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="RgBFxadOQ8abRvmRg9LWvdScESgbEKVRn"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Wed, 27 Nov 2013 05:09:07 +0000 (UTC)
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF-Discussion Discussion <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 05:09:16 -0000

On 11/26/13, 2:27 PM, Mark Nottingham wrote:
> Separate from the issues surrounding enforcing declared policy,
> putting metadata into identifiers seems like a bad practice.
> 
> Besides the issue of scalability — do we really want a SSID that
> looks like “mnot_nomap_guestsallowed_privacyguaranteed_prettyplease”
> — this proposal is squatting on ALL suffixes; someone who wants to
> define the “_guestsallowed” suffix, for example, now can’t do so
> because it’s in contention with _nomap.

32 octets is not a lot when you're trying to overload semantic meaning
on top of identifer, you'll run out fast.

> Never mind that it’s retroactively assigning semantics to potentially
> existing identifiers.
> 
> These issues seem very similar to those raised in the
> draft-nottingham-uri-get-off-my-lawn. It’s very tempting for us as
> standards bodies to encroach upon user-visible identifier space, but
> doing so brings a number of concrete technical problems, as well as a
> higher concern; that these name spaces are explicitly defined to be
> under user (or administrator) control, and taking that control away
> retroactively shouldn’t be something we do.
> 
> Cheers,
> 
> 
> On 26 Nov 2013, at 11:04 pm, Eric Burger <eburger@cs.georgetown.edu>
> wrote:
> 
>> Tastes like the ‘evil’ bit, in reverse.
>> 
>> On Nov 25, 2013, at 6:50 PM, Bjoern Hoehrmann <derhoermi@gmx.net>
>> wrote:
>> 
>>> Hi,
>>> 
>>> My smartphone can turn into a Wifi access point so I can easily
>>> use its Internet connection from my netbook. Problem is that
>>> nearby devices I do not control might report my whereabouts to
>>> third parties that map network equipment to geographic locations.
>>> A naming convention for net- works has been proposed to address
>>> this, append "_nomap" to the network name and "good actors" will
>>> ignore it. I thought it would be a good idea to document this
>>> convention in a better place than a single vendor's blog post, so
>>> two years ago today I published
>>> 
>>> http://tools.ietf.org/html/draft-hoehrmann-nomap-00
>>> 
>>> I think this is a "better than nothing" mechanism and I am not
>>> the most qualified person to document it, and there was pretty
>>> much no interest in the document when I announced it. Still,
>>> especially considering more and more organisations are collecting
>>> such data, I think this needs good documentation. I am looking
>>> for volunteers, suggestions, whatever helps getting that done
>>> without a lot of effort on my part...
>>> 
>>> Thanks! -- Björn Höhrmann · mailto:bjoern@hoehrmann.de ·
>>> http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon:
>>> +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll ·
>>> PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
>> 
> 
> -- Mark Nottingham   http://www.mnot.net/
> 
> 
> 
>