[Geopriv] review of draft-google-self-published-geofeeds

Andrew Newton <andy@hxr.us> Thu, 14 November 2013 18:20 UTC

Return-Path: <andy@hxr.us>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 118CA11E814D for <geopriv@ietfa.amsl.com>; Thu, 14 Nov 2013 10:20:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VKWjwLWhMKf8 for <geopriv@ietfa.amsl.com>; Thu, 14 Nov 2013 10:20:12 -0800 (PST)
Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by ietfa.amsl.com (Postfix) with ESMTP id 11AB911E817F for <geopriv@ietf.org>; Thu, 14 Nov 2013 10:20:12 -0800 (PST)
Received: by mail-pa0-f48.google.com with SMTP id bj1so2407023pad.7 for <geopriv@ietf.org>; Thu, 14 Nov 2013 10:20:11 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=KmHL9SCZ5qt+f3YhVg6YVTtFZa3TWQxOaT1ru61hwlE=; b=AccOogFnhe8EQDsUPGbIp7O+kk2tM0l07nRwByFjLjEzS3jzWW76BZMIONrh85nxxi 6SoR2ST6VvCgkm9n0y94tEa8wnN9zptxMj3NzSlfzmg4O76aJtk+hAtrO0ldwaP+42LI hHx3k7CfXSwTgFLyDfe7AQ8QJVKuaHaC0gBCWNcEIhjSS4ovP6N9Mdid1WbMMlUYQlLG TPFq0uf3qFYJajHa0iyGNkCHrZQEjLEIPd0SGqVuIcvz+F/RyWHTAbsuYEs+SCBT1vFB bpUnoQxqc2SJYbfiKsHzEPFUKjYjimjnt/HNG0WrFk0zoZnfNvpdyLECYz9zfx3Wftjz 70bg==
X-Gm-Message-State: ALoCoQm6lfoDv3pP5Ndy6eZ3JWGdAiyEq0SFOyGlCpSRyu4/K6XHTMIMt/ibsGvZ4u1u5dwlUtT5
MIME-Version: 1.0
X-Received: by 10.67.3.3 with SMTP id bs3mr2821171pad.46.1384453211809; Thu, 14 Nov 2013 10:20:11 -0800 (PST)
Received: by 10.68.33.138 with HTTP; Thu, 14 Nov 2013 10:20:11 -0800 (PST)
X-Originating-IP: [192.149.252.11]
Date: Thu, 14 Nov 2013 13:20:11 -0500
Message-ID: <CAAQiQRen_WTKwCFs5QQMOOQK4+Zr+p+c3KXkbr4CwH60Mx-XYw@mail.gmail.com>
From: Andrew Newton <andy@hxr.us>
To: geopriv@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [Geopriv] review of draft-google-self-published-geofeeds
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Nov 2013 18:20:18 -0000

Alissa, et al,

I have reviewed the geofeeds document. Here's my feedback (which has
already been given to the document authors):

1) Section 3.2 is about using the RIR Whois system as a bootstrap for
finding the CSV file. It might be useful to mention that the IETF
WEIRDS
working group is in the process of specifying RDAP, a replacement for
Whois. Section 5.2 of draft-ietf-weirds-json-response-06 discusses the
linking system for RDAP, which simply re-uses the RFC 5988 IANA
registry. Therefore it would be useful for RDAP and other protocols if
there is an RFC 5988 link relationship registered for geofeeds.

2) Similar to the above, registration of a media type would be useful
for referencing the geofeeds. Something along the lines of
application/geofeed+csv.

3) We might want to consider offering the ability for specifying sets
of postal codes for situations where a single postal code might be too
specific for certain contexts. This might address some privacy
concerns, and may offer the ability to reduce redundant lines in the
CSV file (e.g. Where a network prefix can be found in 2 zip codes).

-andy