IETF Logo Mail Archive

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

"Rosen, Brian" <Brian.Rosen@neustar.biz> Thu, 14 November 2013 19:40 UTC

Return-Path: <brian.rosen@neustar.biz>
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 1DB7311E8127 for <geopriv@ietfa.amsl.com>; Thu, 14 Nov 2013 11:40:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.254
X-Spam-Level:
X-Spam-Status: No, score=-6.254 tagged_above=-999 required=5 tests=[AWL=0.345, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5n1dk1ZxOkiN for <geopriv@ietfa.amsl.com>; Thu, 14 Nov 2013 11:40:03 -0800 (PST)
Received: from neustar.com (smartmail.neustar.com [156.154.25.104]) by ietfa.amsl.com (Postfix) with ESMTP id 7BA3411E8133 for <geopriv@ietf.org>; Thu, 14 Nov 2013 11:39:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1384457937; x=1699815381; q=dns/txt; h=From:Subject:Date:Message-ID:Content-Language: Content-Type:Content-ID:Content-Transfer-Encoding; bh=pYQ60CKEpN eLZ8RO3s2dLetP4ipoV+aNIHr9Fmip1NM=; b=XVtGeSLZ5jgHvoyarANBE3Ff8e Lx4BPOkd3uq5UGXuK39wZHCjBU3cI3kRHwOl1WH/Dj3CKWSnr9lg77AiSCxA==
Received: from ([10.31.58.69]) by chihiron1.nc.neustar.com with ESMTP with TLS id J041123128.27939833; Thu, 14 Nov 2013 14:38:56 -0500
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.5]) by stntexhc10.cis.neustar.com ([169.254.4.132]) with mapi id 14.02.0342.003; Thu, 14 Nov 2013 14:39:21 -0500
From: "Rosen, Brian" <Brian.Rosen@neustar.biz>
To: James Polk <jmpolk@cisco.com>, Andrew Newton <andy@hxr.us>
Thread-Topic: [Geopriv] review of draft-google-self-published-geofeeds
Thread-Index: AQHO4Wbh9q1Juh2Sn0Cbk0vBVmVrgJolchyA//+cvQA=
Date: Thu, 14 Nov 2013 19:39:21 +0000
Message-ID: <CEAA9085.1853E%brian.rosen@neustar.biz>
In-Reply-To: <201311141934.rAEJYZdY018364@rcdn-core-6.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [10.33.193.19]
x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA==
x-ems-stamp: nFwC6CKtKbWHsh6gnAGl3g==
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <28EF206139F7CE40961B0DE976AAEFF8@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: GEOPRIV WG <geopriv@ietf.org>
Subject: Re: [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 19:40:07 -0000

Yeah, they have that.  They also have ³state² = A1 and A3 (city).  They
don¹t have A2 (county) and A4 (what we would call unincorporated parts of
a county, or division of a city).

Their country is the same as ours (ISO 2 digit code).  If they adopt A1-A4
from PIDF as well, they should be able to get what they want.

Brian

On 11/14/13, 2:34 PM, "James Polk" <jmpolk@cisco.com> wrote:

>don't forget <country></country>
>
>At 12:25 PM 11/14/2013, Rosen, Brian wrote:
>>FYI I suggested in the meeting that they consider adopting A1-A4
>>from PIDF, unmodified, to solve this problem.  I don't think postal
>>codes are the right way to do it.
>>
>>Brian
>>
>>
>>On Nov 14, 2013, at 1:20 PM, Andrew Newton <andy@hxr.us> wrote:
>>
>> > 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
>> > _______________________________________________
>> > Geopriv mailing list
>> > Geopriv@ietf.org
>> > https://www.ietf.org/mailman/listinfo/geopriv
>>
>>_______________________________________________
>>Geopriv mailing list
>>Geopriv@ietf.org
>>https://www.ietf.org/mailman/listinfo/geopriv
>

v2.23.0 | Report a Bug | By Email