Re: US patent on an IPv6 geolocation header extension

Tom Herbert <tom@herbertland.com> Thu, 18 January 2018 19:47 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD2312D82F for <ipv6@ietfa.amsl.com>; Thu, 18 Jan 2018 11:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 7Bg8ZFWA_q2t for <ipv6@ietfa.amsl.com>; Thu, 18 Jan 2018 11:47:20 -0800 (PST)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9894412946D for <ipv6@ietf.org>; Thu, 18 Jan 2018 11:47:20 -0800 (PST)
Received: by mail-qt0-x235.google.com with SMTP id d54so21154767qtd.4 for <ipv6@ietf.org>; Thu, 18 Jan 2018 11:47:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=y6D/tjU5oZl5KNC1qCHDogGZlghkhqiXtAlrJGaoXCg=; b=OAfRjTHEmPwkNXSC5rnK79ooe+JSDGj9SZRQnE0ulRfxgxA8Ps6xh4UzlNCbmUySXo mwlwnYOjxUnRPHJDjHfUiv5D2yQZG97DclbtN6bFIJcQqRFMDt5iQORZg2mMii1D53D3 y7dnSZZfHa/MavbUI4kv8MNklw981jxym9c/Fmq+IaP4RKug0ubgLIwLxCGPVBR5INXK E+mVY1JGUFDWgH8BEulR1z9KHHIE0EMPf1UHnjd7rfNa+H/CShKAXqYWzbXlfcPH9mVv +EDpi8y9FgF/Q6096Ysck3HgsTKciuHUdrwdz5z1oIHPuukeZEHOSUlf7muFwr6zTxTE 62Xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=y6D/tjU5oZl5KNC1qCHDogGZlghkhqiXtAlrJGaoXCg=; b=jr4mEOUx7vo3Kc7m8Yeb6zzdyFFJOWVcPgWx/Q1SYz2zTsESrzZSd4K4aiv/GGhlLr AaTH4OrGYMZNps46yjdwi2QiTbLUPc+x+rgvR8JOOzy/as5EBvEH5Z09yAhUMzcCa0l9 wy9X+iSR+BWI9AeuBOhTYBZ795KITayf7GgP2YjdYQ0aE/2ToQ3S2+PAyElsfr3vqlJK m4RSdC9yXfGXKaQBaz83c0J2UONnchrQDR6ddkEp350cJQaYpNiIS2nBQZTGoJIyu74M 7hp3W+j9lA/Hq/i8oz6iBo7k+ueCOHvDYhtG9TYeo6qpK0DAECfjfdvL/X9DpWEbqtKB 3PYw==
X-Gm-Message-State: AKwxyte+zF/GY5gq8+n1dvM5Zokbjv1wHCSstqvl7sucJzIyxS7BbggH XGWWcUcOdh4zvKbqeO63efo4R4DSDOpUbThBey3fnQTZ
X-Google-Smtp-Source: ACJfBovmTIH5R1X7MY/5K/zls1t59YEcoKXZd+ofvttBdZ9BB2+oWFeg7LYSAmzKRK34E4T5kdphImBigqw6QPRg73s=
X-Received: by 10.55.137.132 with SMTP id l126mr8947779qkd.270.1516304839669; Thu, 18 Jan 2018 11:47:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.43.103 with HTTP; Thu, 18 Jan 2018 11:47:19 -0800 (PST)
In-Reply-To: <6e5ae242d1234b85b5fdd7bed8496717@XCH15-06-08.nw.nos.boeing.com>
References: <alpine.OSX.2.21.1801151335550.1660@ary.qy> <CAO42Z2wvamS0yNpVa9+7jvr+XszQ=1fDW3JNAz-9O=PihhbowQ@mail.gmail.com> <c166dc83c586411993edc382aed8b920@XCH15-01-07.nw.nos.boeing.com> <CALx6S372Da87O=PKnG7Ed1iS9dAWFi_AcF9a_Jwucf1Pq1ZDpw@mail.gmail.com> <6e5ae242d1234b85b5fdd7bed8496717@XCH15-06-08.nw.nos.boeing.com>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 18 Jan 2018 11:47:19 -0800
Message-ID: <CALx6S35mi3pqw0TFVh3yDUSSy2M0qb2sK=cpvge1ThSnmiQf1w@mail.gmail.com>
Subject: Re: US patent on an IPv6 geolocation header extension
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Lp_8CHM85Y8ineqBB-xKlCgyrKo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jan 2018 19:47:22 -0000

On Thu, Jan 18, 2018 at 11:33 AM, Templin, Fred L
<Fred.L.Templin@boeing.com> wrote:
>> Right, my first question would be "How is users' privacy protected?".
>
> One solution is to conceal the geo information via VPN encryption for
> transmission over public networks like the Internet. In private networks
> such as a corporate enterprise, the geo information could go in the clear.
>
Or alternatively encrypt or at least obfuscate the location
information so only trusted parties can read it. That would be similar
to the intent of tickets in our FAST proposal
(https://tools.ietf.org/html/draft-herbert-fast-00) where data in
extension headers is only interpretable by the origin network. Now
that I think about it, geo-location could be probably be encoded in a
FAST ticket.

Tom

> Fred
>
>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Tom Herbert
>> Sent: Thursday, January 18, 2018 11:25 AM
>> To: Manfredi, Albert E <albert.e.manfredi@boeing.com>
>> Cc: 6man WG <ipv6@ietf.org>
>> Subject: Re: US patent on an IPv6 geolocation header extension
>>
>> On Thu, Jan 18, 2018 at 11:04 AM, Manfredi, Albert E
>> <albert.e.manfredi@boeing.com> wrote:
>> > -----Original Message-----
>> > From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Mark Smith
>> >
>> >> Here's some prior art from 2013.
>> >>
>> >> "Enhancing Location Based IP Services"
>> >> https://tools.ietf.org/html/draft-add-location-to-ipv6-header-01
>> >
>> > I thought that rang a bell (reminded me of something). Wasn't there some who disliked the idea intensely, just because it disclosed
>> geo location without the use being aware as the user might be, if that feature was in an app? I seem to remember some acrimony
>> involved.
>>
>> Right, my first question would be "How is users' privacy protected?".
>> Geo-location of individuals is very sensitive data. In fact, one of
>> the goals of ILA is to eliminate the possibility of inferring any
>> accurate location of a node from IP addresses.
>>
>> Tom
>>
>> >
>> > Bert
>> >
>> >
>> > --------------------------------------------------------------------
>> > IETF IPv6 working group mailing list
>> > ipv6@ietf.org
>> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> > --------------------------------------------------------------------
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>