Re: The "nomap" Network Identifier Suffix

Richard Barnes <rlb@ipv.sx> Tue, 26 November 2013 20:13 UTC

Return-Path: <rlb@ipv.sx>
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 ECA971ADFA1 for <ietf@ietfa.amsl.com>; Tue, 26 Nov 2013 12:13:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 Kw__53BpKMRi for <ietf@ietfa.amsl.com>; Tue, 26 Nov 2013 12:13:39 -0800 (PST)
Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by ietfa.amsl.com (Postfix) with ESMTP id 202DB1ADF2F for <ietf@ietf.org>; Tue, 26 Nov 2013 12:13:39 -0800 (PST)
Received: by mail-oa0-f54.google.com with SMTP id h16so6557324oag.41 for <ietf@ietf.org>; Tue, 26 Nov 2013 12:13:38 -0800 (PST)
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=NZ1ti0wOn0+RZVcd/3mpVQDRqQHKiHUXbmsd9XqxPu4=; b=gn35Qb+aZ16Cg9A2M85CrXJLlR+6etm2eAK3ZLF1cV0HUTkEf7T8L/xygj64EduqAw jWPfW7tF+yak30dNnNAXgkvyMBuz/blnzems07A+T8byoc604JQa21i9TqGrOQ4dNd8i kytHTai7UhMGUOCsWMXG6iT4KNdfBuYaHKEMvIOSoXA6730ixtH5XDHkm88LnDBYJe+a rEMGy+X/J76xQAIjJLCwI+lOTpSHtf3zimnedcmw2ZaBPIM/PbKe7uN+qjWra1wOcHal NF4BnsKndXtKBA663nlvew+f3NNMt5YHAxtIb8lClnuL17aPFtBp2m4Lal/aiQ0jQ/92 EoZw==
X-Gm-Message-State: ALoCoQmpmfjHgAytf2hdWHbR6fKc0zj1IKcjGPg7V3j/egFWCjoTlINKTKyAYhsaW47jOxAgSTxa
MIME-Version: 1.0
X-Received: by 10.182.28.35 with SMTP id y3mr7223634obg.55.1385496818729; Tue, 26 Nov 2013 12:13:38 -0800 (PST)
Received: by 10.60.31.74 with HTTP; Tue, 26 Nov 2013 12:13:38 -0800 (PST)
In-Reply-To: <3D4E298A-FE87-4FD1-BCC2-EF33E7BD4D99@cs.georgetown.edu>
References: <i9n799hrr1vfp4bobt9tc55rn1aip73rts@hive.bjoern.hoehrmann.de> <3D4E298A-FE87-4FD1-BCC2-EF33E7BD4D99@cs.georgetown.edu>
Date: Tue, 26 Nov 2013 15:13:38 -0500
Message-ID: <CAL02cgQ7JXG-iRKWyT_eTGT4Ak8ag6FS-z+++yRJztU-tkBb_w@mail.gmail.com>
Subject: Re: The "nomap" Network Identifier Suffix
From: Richard Barnes <rlb@ipv.sx>
To: Eric Burger <eburger@cs.georgetown.edu>
Content-Type: multipart/alternative; boundary="089e015388f6b7d90004ec1a1dac"
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: Tue, 26 Nov 2013 20:13:41 -0000

I think that's a little facile.

The evil bit is ridiculous because evil people have no incentive to set it
(thus nobody would ever look for it to be set).  With the _nomap suffix,
the people who would need to set it have an incentive to do so, and at
least in certain cases, the entities that might consume it have incentives
to obey it as well.


On Tue, Nov 26, 2013 at 7:04 AM, 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/
>
>