Re: US patent on an IPv6 geolocation header extension

joel jaeggli <joelja@bogus.com> Thu, 18 January 2018 19:52 UTC

Return-Path: <joelja@bogus.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 CB41A1270FC for <ipv6@ietfa.amsl.com>; Thu, 18 Jan 2018 11:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=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 NJdU828qxtWD for <ipv6@ietfa.amsl.com>; Thu, 18 Jan 2018 11:52:08 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C132127011 for <ipv6@ietf.org>; Thu, 18 Jan 2018 11:52:08 -0800 (PST)
Received: from MBP.local (c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id w0IJq5JP081980 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 18 Jan 2018 19:52:06 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209] claimed to be MBP.local
Subject: Re: US patent on an IPv6 geolocation header extension
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Mark Smith <markzzzsmith@gmail.com>
Cc: 6man WG <ipv6@ietf.org>
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>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <d7e43251-2c44-b235-bc4c-baadf659f370@bogus.com>
Date: Thu, 18 Jan 2018 11:52:00 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <c166dc83c586411993edc382aed8b920@XCH15-01-07.nw.nos.boeing.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6jyb44WvN2NKWiFiobND2rZkXhw>
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:52:10 -0000


On 1/18/18 11:04 AM, Manfredi, Albert E 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.
If you add this sort of thing at an intermediate hop, you have all of
the attendant problems of unstated or lack of consent that go along with
adding host identifiers of any kind (we largely have IETF consensus not
to work on host-identiers). If you add it only on the endpoint, consent
can be achieved in various ways. Protecting that information from
mid-point observers is an important consideration that would tend to
preclude embedding it for use by the network or transport layers.

Applications have no problems reporting to each other where they are
without recourse to lower-layer signaling.
> Bert
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>