IETF Logo Mail Archive

Re: The "nomap" Network Identifier Suffix

Dave Cridland <dave@cridland.net> Wed, 27 November 2013 13:14 UTC

Return-Path: <dave@cridland.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 8963A1AE1C8 for <ietf@ietfa.amsl.com>; Wed, 27 Nov 2013 05:14:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 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, SPF_PASS=-0.001] 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 knUfUAOLBguC for <ietf@ietfa.amsl.com>; Wed, 27 Nov 2013 05:14:26 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDBE1AE1B8 for <ietf@ietf.org>; Wed, 27 Nov 2013 05:14:25 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id n7so5113936lam.7 for <ietf@ietf.org>; Wed, 27 Nov 2013 05:14:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eR8cKnQBnKBLSrSc1334SufblI+5DZnpZIIvsHT+U94=; b=El6vBrixuq7HZc/mlPh5bLd2Z5RXcLy2ZrO/Hm2FlGtJOa2APTTiqaaGHl6sA+GsmA 1dqUGye4al/WLGUobsP2bG9Bpc0amrx57IeK17rGv0nX7dt3Yxlf73x3mz73H3Pclica K/ncJmAG4/THo09ikzlrBNK+ZYTuh5U351Yys=
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=eR8cKnQBnKBLSrSc1334SufblI+5DZnpZIIvsHT+U94=; b=kbHS5AQK8iWGVPg7WpdPG9PjR8pshq0u/qPyXqIkcCK/fSq/fiBw0wZeVM/4O+YNEl +gDVbcBg2SmzhqhSqRySTJfd4YGAOfylCK0VdVSDXKjDrwdmb4sRb1yQ4CmwQF93R6F8 yfREUnC0tuvqnukW3G+5uXMzg5qobu1AE/DiAuSkwnR5A3z/zBPU4MvlAVbJ1c7bxV92 hg7rfOBg1+PemX15m2Z3KYxUamf5z2/ISl7Iez/P8VHGJQeYJ4N0hZ0gaec+g2SRAoWz cOKkrhsRApJfveQEFZrk8pLZG/T0ltjgexYeiyt1p9eVza/J5gf0CT25WoO/uFWMBqTW WweA==
X-Gm-Message-State: ALoCoQnCxfbxJdTjTHGjmkiYYit5iSxQU7RklN0sgbI7V8fXZCGTSpHrKRzl/YRBdbfKO4nz4czp
MIME-Version: 1.0
X-Received: by 10.152.8.199 with SMTP id t7mr27598075laa.21.1385558064849; Wed, 27 Nov 2013 05:14:24 -0800 (PST)
Received: by 10.114.183.47 with HTTP; Wed, 27 Nov 2013 05:14:24 -0800 (PST)
In-Reply-To: <i9n799hrr1vfp4bobt9tc55rn1aip73rts@hive.bjoern.hoehrmann.de>
References: <i9n799hrr1vfp4bobt9tc55rn1aip73rts@hive.bjoern.hoehrmann.de>
Date: Wed, 27 Nov 2013 13:14:24 +0000
Message-ID: <CAKHUCzxjQhOCYc9n3T4RSpyKStqbJu3bWMkARDV90Fp8iyq5Mw@mail.gmail.com>
Subject: Re: The "nomap" Network Identifier Suffix
From: Dave Cridland <dave@cridland.net>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: multipart/alternative; boundary="089e0158ace045734604ec286089"
Cc: "ietf@ietf.org 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 13:14:27 -0000

I'm not a fan of the suffixes, but I appreciate the goal.

FWIW, every time I run up certain mobile hotspots, my online presence is
instantly translated through space (sadly not time) to various hotels and
places around the UK. Sadly, my offline presence cannot be so translated,
otherwise I would save a small fortune in air fares, not to mention the
convenience.

This isn't, though, a security issue. If I have geoloc info going out, I'm
entirely happy for it to say where I am. I'm just not happy when it tells
everyone I'm in a Travelodge in Kingston - not because I'm ashamed of ever
having been there (although perhaps I should be) but because it's simply
inconvenient.

I'd be happy if either geoloc knew to ignore the access point as a location
beacon, or else it actually teleported me. The latter is actually
preferable, but the former's good as well.

Dave.

v2.23.0 | Report a Bug | By Email