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

creed@opengeospatial.org Fri, 26 March 2010 15:15 UTC

Return-Path: <creed@opengeospatial.org>
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 570093A695A for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 08:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.258
X-Spam-Level:
X-Spam-Status: No, score=0.258 tagged_above=-999 required=5 tests=[AWL=-0.687, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
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 e+maYfJzP50k for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 08:15:24 -0700 (PDT)
Received: from mail.opengeospatial.org (mail.opengeospatial.org [66.244.86.40]) by core3.amsl.com (Postfix) with ESMTP id 336203A6827 for <earlywarning@ietf.org>; Fri, 26 Mar 2010 08:15:16 -0700 (PDT)
Received: from mail.opengeospatial.org (localhost [127.0.0.1]) by mail.opengeospatial.org (8.13.8/8.13.8/Debian-3+etch1) with ESMTP id o2QFFbHw009508; Fri, 26 Mar 2010 11:15:38 -0400
Received: from 198.123.49.132 (SquirrelMail authenticated user creed) by mail.opengeospatial.org with HTTP; Fri, 26 Mar 2010 11:15:38 -0400 (EDT)
Message-ID: <62524.198.123.49.132.1269616538.squirrel@mail.opengeospatial.org>
In-Reply-To: <BE16D422273834438B43B6F7D730220F0798DC78@BD01MSXMB015.US.Cingular.Net >
References: <BE16D422273834438B43B6F7D730220F0798DC78@BD01MSXMB015.US.Cingular.Net>
Date: Fri, 26 Mar 2010 11:15:38 -0400
From: creed@opengeospatial.org
To: "SENNETT, DEWAYNE A (ATTCINW)" <DS2225@att.com>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: ClamAV 0.92.1/10628/Fri Mar 26 09:57:50 2010 on mail.opengeospatial.org
X-Virus-Status: Clean
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:15:25 -0000

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
>