Re: [atoca] Next milestone

Art Botterell <acb@incident.com> Tue, 25 September 2012 20:47 UTC

Return-Path: <artbotterell@gmail.com>
X-Original-To: atoca@ietfa.amsl.com
Delivered-To: atoca@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6944F1F0CE0 for <atoca@ietfa.amsl.com>; Tue, 25 Sep 2012 13:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.229
X-Spam-Level:
X-Spam-Status: No, score=-3.229 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bidfylbOGRED for <atoca@ietfa.amsl.com>; Tue, 25 Sep 2012 13:46:59 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id DA40D1F0C67 for <atoca@ietf.org>; Tue, 25 Sep 2012 13:46:59 -0700 (PDT)
Received: by pbbro8 with SMTP id ro8so728967pbb.31 for <atoca@ietf.org>; Tue, 25 Sep 2012 13:46:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=rFQZZsk8EuNwl9sPvR5Q5s45LaYYmjzCkyjJyBC3gGM=; b=tRwh1mXeO7HiCDJPRYzD0UNQ3F4O/2AOiAlzLb/hTFHCGCaHsrCz3D+utOyBup8rlu oRtDcmv2n36cZVjh7Zz1Jbvz3ZUtVJh4btUvTd/rXXnSYdA1jM92z8DytpRJL2V82m/9 XyDkSjpLWjhiIJmrwpurI3C4gEW2RqgR2gwOaWjZq23TdpuL3WwNakYHXVcGeaKwXcEU t5S+KIig004YtmabFSOKdzGglA0JNpDHIjvtNZ/Lm6tr0WjSogcpHNxEg8OvQ1NB57kL IiED9AKfdhiuwmKHag3vpZw7/2l4C9441AJcNAHjHmCqmmSP5yW0tLKJpo6WvW7vsuv2 Lmlg==
Received: by 10.68.138.198 with SMTP id qs6mr29508802pbb.151.1348606019678; Tue, 25 Sep 2012 13:46:59 -0700 (PDT)
Received: from [192.168.1.69] (99-182-125-96.lightspeed.frokca.sbcglobal.net. [99.182.125.96]) by mx.google.com with ESMTPS id y11sm821872pbv.66.2012.09.25.13.46.54 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Sep 2012 13:46:56 -0700 (PDT)
Sender: Art Botterell <artbotterell@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Art Botterell <acb@incident.com>
In-Reply-To: <20120925191748.29FBB21F84CE@ietfa.amsl.com>
Date: Tue, 25 Sep 2012 13:46:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <929000B5-1ED9-4C7E-B2F0-7CD83D3FC019@incident.com>
References: <20120925191748.29FBB21F84CE@ietfa.amsl.com>
To: "Mark Wood" <mark.wood@drcf.net>
X-Mailer: Apple Mail (2.1283)
Cc: atoca@ietf.org
Subject: Re: [atoca] Next milestone
X-BeenThere: atoca@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for the IETF Authority-to-Citizen Alert \(atoca\) working group." <atoca.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/atoca>, <mailto:atoca-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/atoca>
List-Post: <mailto:atoca@ietf.org>
List-Help: <mailto:atoca-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/atoca>, <mailto:atoca-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2012 20:47:00 -0000

On Sep 25, 2012, at 12:17 PM, Mark Wood wrote:
> 
> Actually the only component that really needs to translate from FIPS to
> WGS84 is the Aggregator/Gateway system. This is because it needs to apply
> policy to the proposed message on the basis of sovereignty of the territory
> under the polygon. 

This is another interesting and somewhat subtle point.  To what extent... and to what end... is it appropriate and/or necessary to "clip" warning geometries to reflect political boundaries?  I'd suggest that that's a political consideration, not a technical necessity nor a universal requirement.

From the perspective of public service it might actually be more useful to convert the other way... given a hazard polygon, compute the list of jurisdictions (in this case, U.S. counties represented as FIPS-based strings) than the other way around.  That could provide support for legacy systems that can't target any more precisely than the county level, and also provide notification of all jurisdictions touched by an alert, even if the alert came from a different source (an adjoining jurisdiction, say, or a national meteorological agency.)

The arguments for limiting alerts to the originating jurisdiction strike me as possibly less noble.  Certainly government agencies tend to be jealous and exclusive about their privileges, but hazards don't care.  And am I not entitled to prompt warning of a nearby hazard just because there happens to be an administrative boundary in-between?  Will the county line protect me somehow?

Indeed, mechanisms aimed at political turf protection were one of the major sources of delay and warning failure in the 2004 Indian Ocean tsunami.

So... how to strike the balance between the privileges of authority and those of citizenship?  The answer is that it's not actually up to us  Different countries and different cultures will have different values and legal frameworks.  So we probably want to be cautious about trying to instantiate any particular value system in technology.

- Art