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

"DALY, BRIAN K (ATTCINW)" <BD2985@att.com> Fri, 26 March 2010 19:49 UTC

Return-Path: <BD2985@att.com>
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 5AA873A6A2A for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 12:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.3
X-Spam-Level:
X-Spam-Status: No, score=-105.3 tagged_above=-999 required=5 tests=[AWL=0.170, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 HUs44cZpQ+6g for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 12:49:28 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id 6933E3A6778 for <earlywarning@ietf.org>; Fri, 26 Mar 2010 12:49:28 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: BD2985@att.com
X-Msg-Ref: server-15.tower-129.messagelabs.com!1269632990!25192591!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.112.25]
Received: (qmail 5276 invoked from network); 26 Mar 2010 19:49:51 -0000
Received: from sbcsmtp3.sbc.com (HELO tlph064.enaf.dadc.sbc.com) (144.160.112.25) by server-15.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Mar 2010 19:49:51 -0000
Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1]) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id o2QJnn7R010900; Fri, 26 Mar 2010 14:49:50 -0500
Received: from td03xsmtp005.US.Cingular.Net (td03xspare20-new.us.cingular.net [135.179.64.44] (may be forged)) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id o2QJnjDq010803; Fri, 26 Mar 2010 14:49:45 -0500
Received: from bd01xsmtp004.US.Cingular.Net ([135.163.18.45]) by td03xsmtp005.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Mar 2010 14:49:45 -0500
Received: from BD01MSXMB016.US.Cingular.Net ([135.214.27.50]) by bd01xsmtp004.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Mar 2010 12:49:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Fri, 26 Mar 2010 12:49:43 -0700
Message-ID: <FDFC6E6B2064844FBEB9045DF1E3FBBC093CBE@BD01MSXMB016.US.Cingular.Net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [earlywarning] What problem is ATOCA trying to address?
thread-index: AcrNHXrCL0rzhC4WQbKu9qvVvT4b+g==
From: "DALY, BRIAN K (ATTCINW)" <BD2985@att.com>
To: br@brianrosen.net, acb@incident.com, earlywarning@ietf.org
X-OriginalArrivalTime: 26 Mar 2010 19:49:43.0254 (UTC) FILETIME=[7ADD2760:01CACD1D]
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 19:49:29 -0000

It is not that simple. For example if you attempt to run Twitter over a wireless network and try to handle a large number of alerts (consider the EAN case) then congestion will result in delays. This is why SMS does not work and as more data enabled devices are used multicast/broadcast is essential.
------Original Message------
From: Brian Rosen
To: Art Botterell
To: earlywarning@ietf.org
Subject: Re: [earlywarning] What problem is ATOCA trying to address?
Sent: Mar 26, 2010 8:44 AM

We're not at the mechanism state yet.  While I imagine that the mechanisms
may include something that is "if you have multicast, use it", I don't think
that would be enough because multicast is not enabled in way too many
networks.  Sites like Twitter show us that we can get enough messages sent
out in reasonable periods of time without multicast.

Brian


On 3/26/10 11:34 AM, "Art Botterell" <acb@incident.com> wrote:

> On Mar 26, 2010, at 3/26/10 6:42 AM, Marc Linsner wrote:
>> Any IP device, any IP network, any message (not just Fed. Gov't), all under
>> end-user control (opt-in, opt-out, additional locations, etc.).
> 
> So is it possible we're really just revisiting IP multicast?
> 
> - 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


Brian K. Daly
-------
Sent from my Blackberry