Re: [OPSAWG] WG LC: draft-ietf-opsawg-finding-geofeeds

Randy Bush <randy@psg.com> Mon, 01 February 2021 20:47 UTC

Return-Path: <randy@psg.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7BF83A147D; Mon, 1 Feb 2021 12:47:30 -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, SPF_HELO_NONE=0.001, 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 ZLIe5-OlX6MJ; Mon, 1 Feb 2021 12:47:29 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 1F65B3A147B; Mon, 1 Feb 2021 12:47:29 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1l6g6W-0004rR-NL; Mon, 01 Feb 2021 20:47:24 +0000
Date: Mon, 01 Feb 2021 12:47:24 -0800
Message-ID: <m27dnrfrc3.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>
Cc: <opsawg@ietf.org>, <opsawg-chairs@ietf.org>, <draft-ietf-opsawg-finding-geofeeds@ietf.org>
In-Reply-To: <075b01d6f8d8$c189db70$449d9250$@olddog.co.uk>
References: <06bf01d6f884$18acfd10$4a06f730$@olddog.co.uk> <m2h7mvfv0p.wl-randy@psg.com> <075b01d6f8d8$c189db70$449d9250$@olddog.co.uk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/OJzVaGNV6JWNtwmBKW0y5KweRNg>
Subject: Re: [OPSAWG] WG LC: draft-ietf-opsawg-finding-geofeeds
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2021 20:47:31 -0000

> So perhaps modifying your paragraph to...
> 
>     RFC8805 geofeed data may reveal the approximate location of an IP
>     address, which might in turn reveal the approximate location of an
>     individual user.  As noted in section 4 of RFC8805, publishers of
>     geolocation feeds are advised to have fully considered any and all
>     privacy implications of the disclosure.  Further, operators who publish
>     geolocation information are strongly encouraged to inform affected
>     users/customers of this fact and of the potential privacy-related
>     consequences and trade-offs.  In publishing pointers to geofeed files
>     as described in this document the operator should be aware of these
>     privacy concerns and be cautious.

done.  thanks.

best to ignore the games of flavors of rfcs.

randy