IETF Logo Mail Archive

RE: US patent on an IPv6 geolocation header extension

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Thu, 18 January 2018 19:04 UTC

Return-Path: <albert.e.manfredi@boeing.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 917CD129C56 for <ipv6@ietfa.amsl.com>; Thu, 18 Jan 2018 11:04:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 p1OLTX-rVY-I for <ipv6@ietfa.amsl.com>; Thu, 18 Jan 2018 11:04:30 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 2F80B1241F5 for <ipv6@ietf.org>; Thu, 18 Jan 2018 11:04:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id w0IJ4SFM019127; Thu, 18 Jan 2018 12:04:28 -0700
Received: from XCH15-01-08.nw.nos.boeing.com (xch15-01-08.nw.nos.boeing.com [137.136.239.158]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w0IJ4MX3019107 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 18 Jan 2018 12:04:22 -0700
Received: from XCH15-01-07.nw.nos.boeing.com (137.136.239.154) by XCH15-01-08.nw.nos.boeing.com (137.136.239.158) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 18 Jan 2018 11:04:21 -0800
Received: from XCH15-01-07.nw.nos.boeing.com ([137.136.239.154]) by XCH15-01-07.nw.nos.boeing.com ([137.136.239.154]) with mapi id 15.00.1347.000; Thu, 18 Jan 2018 11:04:21 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Mark Smith <markzzzsmith@gmail.com>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: US patent on an IPv6 geolocation header extension
Thread-Topic: US patent on an IPv6 geolocation header extension
Thread-Index: AQHTkEnW1HKpV9np4kKPnUFd/NL1VaN5/NKA
Date: Thu, 18 Jan 2018 19:04:21 +0000
Message-ID: <c166dc83c586411993edc382aed8b920@XCH15-01-07.nw.nos.boeing.com>
References: <alpine.OSX.2.21.1801151335550.1660@ary.qy> <CAO42Z2wvamS0yNpVa9+7jvr+XszQ=1fDW3JNAz-9O=PihhbowQ@mail.gmail.com>
In-Reply-To: <CAO42Z2wvamS0yNpVa9+7jvr+XszQ=1fDW3JNAz-9O=PihhbowQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/cwtBRzqsXERbXcMdQf95c0a_wLk>
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:04:32 -0000

-----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.

Bert

v2.23.0 | Report a Bug | By Email