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

Disagree - we have designed an optimized system for commercial mobile devices that will deliver alerts to devices on those networks in an efficient manner. Regardless of what IETF does CMAS will continue to be the method operators will use for delivering alerts to any device connected to the network where the operator supports CMAS. That is fact.
Brian K. Daly
-------
Sent from my Blackberry

----- Original Message -----
From: David R Oran <oran@cisco.com>
To: DALY, BRIAN K (ATTCINW)
Cc: Art Botterell <acb@incident.com>; earlywarning@ietf.org <earlywarning@ietf.org>
Sent: Fri Mar 26 13:10:11 2010
Subject: Re: [earlywarning] What problem is ATOCA trying to address?

On Mar 26, 2010, at 3:56 PM, DALY, BRIAN K (ATTCINW) wrote:

> Agree Art - Twitter is like SMS - no guarantee, unreliable, and prone to
> congestion. While in general it is good to try to get the message out as
> many ways as possible, at least one should be deemed "reliable".
> 
Sometimes reliability is the enemy of resilience. I would argue we're mostly shooting for the latter, and the former is often over-rated, especially if people start thinking it will work when needed and don't think more broadly, like maybe the cell tower just fell down.

That's why I think it's extremely short-sighted to try to "exempt" any particular device from the general IETF solution, and we should view the particular L2-specific mechanisms as optimizations to reduce load/congestion.

It also makes sense to view the cell-broadcast capability as an "underlay" for delivery of the more general Internet-generated and managed emergency alerts as opposed to some parallel and un-coordinated capability. 

Cheers, DaveO.

> Brian
> 
> -----Original Message-----
> From: earlywarning-bounces@ietf.org
> [mailto:earlywarning-bounces@ietf.org] On Behalf Of Art Botterell
> Sent: Friday, March 26, 2010 9:37 AM
> To: earlywarning@ietf.org
> Subject: Re: [earlywarning] What problem is ATOCA trying to address?
> 
> On Mar 26, 2010, at 3/26/10 9:14 AM, Henning Schulzrinne wrote:
>> And to bore everyone again with the same thing: In many cases,
> notifications are routinely sent to people outside a specific area or
> beyond a single network.
> 
> Which is why I thought it might be useful to reflect on WHY, after all
> these years, IP multicast has such limited scope, and on whether similar
> constraints might apply here.
> 
> Meanwhile, unicast approaches like Twitter rarely try to reach everyone
> on a particular local network, and they don't have any strict
> constraints on latency or even reliability, so I'd be cautious about
> assuming their suitability in emulation of a multicasting function.
> Anyone who's ever tried to text on New Year's Eve or Mother's Day should
> be able to relate.
> 
> - Art
> _______________________________________________
> 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