Re: [earlywarning] What problem is ATOCA trying to address?

Brian Rosen <br@brianrosen.net> Fri, 26 March 2010 15:24 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: earlywarning@core3.amsl.com
Delivered-To: earlywarning@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42A693A691C for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 08:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.325
X-Spam-Level: **
X-Spam-Status: No, score=2.325 tagged_above=-999 required=5 tests=[AWL=-0.359, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xdMKgeaOCXdq for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 08:24:56 -0700 (PDT)
Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [67.18.150.162]) by core3.amsl.com (Postfix) with ESMTP id 994713A695C for <earlywarning@ietf.org>; Fri, 26 Mar 2010 08:24:54 -0700 (PDT)
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=[192.168.129.39]) by ebru.winwebhosting.com with esmtpa (Exim 4.69) (envelope-from <br@brianrosen.net>) id 1NvBPI-0002Zn-Fy; Fri, 26 Mar 2010 10:25:08 -0500
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 26 Mar 2010 11:25:11 -0400
From: Brian Rosen <br@brianrosen.net>
To: creed@opengeospatial.org, "SENNETT, DEWAYNE A (ATTCINW)" <DS2225@att.com>
Message-ID: <C7D24A17.2B5B1%br@brianrosen.net>
Thread-Topic: [earlywarning] What problem is ATOCA trying to address?
Thread-Index: AcrM+IZDZSi3GXUF4E2f5kBzmfnlIQ==
In-Reply-To: <62524.198.123.49.132.1269616538.squirrel@mail.opengeospatial.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
Cc: earlywarning@ietf.org
Subject: Re: [earlywarning] What problem is ATOCA trying to address?
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for Authority-to-Individuals \(Early Warning\) Emergency " <earlywarning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/earlywarning>
List-Post: <mailto:earlywarning@ietf.org>
List-Help: <mailto:earlywarning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 15:24:57 -0000

'course CAP should just borrow PIDF-LO and thus be able to send an alert
about the hospital at 123 Main (that is, a civic "where").

Thanks for the info, should be a useful update of CAP/EDXL.

Brian


On 3/26/10 11:15 AM, "creed@opengeospatial.org" <creed@opengeospatial.org>
wrote:

> Apologies for the slight digression. Not to be contentious, but CAP is
> only part of the application payload solution. Other countries are using
> other encodings instead of CAP (such as SMS) or are using additional
> application solutions in addition to CAP (such as GeoRSS or GeoSMS).
> 
> Something also to be aware of WRT CAP. The OASIS EM TC has defined a set
> of requirements for an enhanced OASIS "where" model (geographic) that will
> be encoded as a GML application schema. The plan is to be consistent with
> the PIDF-LO geodetic GML schema as well as GeoRSS GML. This work adds
> additional geometries and other elements such as multipoints. These
> requirements were provided by the CAP implementation community and will be
> incorporated (perhaps by extension) in CAP 2.0 and future revisions of
> EDXL.
> 
> Cheers
> 
> Carl
> 
>> It is not clear exactly what problem ATOCA is trying to solve.
>> 
>> The first item needed for alerting is a common alerting message. This has
>> been defined as the CAP protocol which has been adopted by ITU. The
>> current version is CAP 1.1 and version 1.2 is expected soon.
>> 
>> The second item needed is transport of CAP messages. Various techniques
>> already exist and Brian Rosen has already introduced a draft into ECRIT to
>> define how to deliver CAP via SIP.
>> 
>> The third item is distribution of the alert information. Various
>> techniques already exist such as multicast, cell broadcast, MBMS, EAS,
>> CMAS etc..
>> 
>> The fourth item is authentication and authorization of the alert
>> origination. The functionality is country specific and these countries
>> also have defined methods and procedures to address this.
>> 
>> So what item remains to be addressed by ATOCA?
>> 
>> <--------------------------->
>> DeWayne Sennett, AT&T Services, Inc.
>> Sent from my BlackBerry
>> _______________________________________________
>> earlywarning mailing list
>> earlywarning@ietf.org
>> https://www.ietf.org/mailman/listinfo/earlywarning
>> 
> 
> 
> _______________________________________________
> earlywarning mailing list
> earlywarning@ietf.org
> https://www.ietf.org/mailman/listinfo/earlywarning