IETF Logo Mail Archive

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

Brian Rosen <br@brianrosen.net> Fri, 26 March 2010 15:44 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 9A6973A6B0C for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 08:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.361
X-Spam-Level: **
X-Spam-Status: No, score=2.361 tagged_above=-999 required=5 tests=[AWL=-0.323, 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 FQHfs3GuY4jl for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 08:44:27 -0700 (PDT)
Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [67.18.150.162]) by core3.amsl.com (Postfix) with ESMTP id E14D53A695A for <earlywarning@ietf.org>; Fri, 26 Mar 2010 08:44:27 -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 1NvBiF-0003gx-4C; Fri, 26 Mar 2010 10:44:43 -0500
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 26 Mar 2010 11:44:44 -0400
From: Brian Rosen <br@brianrosen.net>
To: Art Botterell <acb@incident.com>, earlywarning@ietf.org
Message-ID: <C7D24EAC.2B5BC%br@brianrosen.net>
Thread-Topic: [earlywarning] What problem is ATOCA trying to address?
Thread-Index: AcrM+0FsxOxW3sk2vkyi+mpntS85dg==
In-Reply-To: <EB0E9151-20A6-4576-AFE7-CEDE3FFEF79A@incident.com>
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
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:44:28 -0000

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

v2.23.0 | Report a Bug | By Email