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

Henning Schulzrinne <hgs@cs.columbia.edu> Fri, 26 March 2010 16:16 UTC

Return-Path: <hgs@cs.columbia.edu>
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 E6C1B3A6B9B for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 09:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.952
X-Spam-Level:
X-Spam-Status: No, score=-3.952 tagged_above=-999 required=5 tests=[AWL=1.517, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4]
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 wLpNQK-32L57 for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 09:16:23 -0700 (PDT)
Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by core3.amsl.com (Postfix) with ESMTP id 3FC5F3A68D4 for <earlywarning@ietf.org>; Fri, 26 Mar 2010 09:14:17 -0700 (PDT)
Received: from dhcp-wireless-open-abg-26-78.meeting.ietf.org (dhcp-wireless-open-abg-26-78.meeting.ietf.org [130.129.26.78]) (user=hgs10 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o2QGEbfq012817 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 26 Mar 2010 12:14:38 -0400 (EDT)
References: <C7D24EAC.2B5BC%br@brianrosen.net>
In-Reply-To: <C7D24EAC.2B5BC%br@brianrosen.net>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
Message-Id: <8136DC6D-FD55-4A9F-A81B-902584B3DF6D@cs.columbia.edu>
Content-Transfer-Encoding: quoted-printable
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Fri, 26 Mar 2010 12:14:37 -0400
To: Brian Rosen <br@brianrosen.net>
X-Mailer: Apple Mail (2.1077)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
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 16:16:25 -0000

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. Simple example: The WiFi network in Panera Bread is unlikely to be reachable by single multicast along with the 3GPP network covering that same region, and may even be logically run from some corporate HQ.

Henning

On Mar 26, 2010, at 11:44 AM, Brian Rosen wrote:

> 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
>