IETF Logo Mail Archive

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

Art Botterell <acb@incident.com> Fri, 26 March 2010 16:40 UTC

Return-Path: <acb@incident.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 B2A9B3A6BA9 for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 09:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.373
X-Spam-Level: *
X-Spam-Status: No, score=1.373 tagged_above=-999 required=5 tests=[AWL=-0.093, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334, UNPARSEABLE_RELAY=0.001]
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 yUtiU+rKUTWL for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 09:40:01 -0700 (PDT)
Received: from smtp105.sbc.mail.gq1.yahoo.com (smtp105.sbc.mail.gq1.yahoo.com [67.195.14.108]) by core3.amsl.com (Postfix) with SMTP id 942AC3A6B5A for <earlywarning@ietf.org>; Fri, 26 Mar 2010 09:36:13 -0700 (PDT)
Received: (qmail 67046 invoked from network); 26 Mar 2010 16:36:34 -0000
Received: from 99-182-125-96.lightspeed.frokca.sbcglobal.net (acb@99.182.125.96 with login) by smtp105.sbc.mail.gq1.yahoo.com with SMTP; 26 Mar 2010 09:36:34 -0700 PDT
X-Yahoo-SMTP: c09pd_2swBAlwYa9BknTHpHNRHUh4Oco4AeV8DAru96p
X-YMail-OSG: mL4fVMYVM1l.p6yO9z2rs2asx2IAXtqNu4cZI9OZu_s1x_8.7QldXrdFM8nmVFzSmPkttgq2SP2_ABA2IjmN_HS46M6D8mQyk1bgAJLGiqf8YErGs8zytR9wJfoHEFeskA4nZue4oCUpd1TtnUoth.d3Dbpo2CPqclgUNeYLBfVQyrGCFgk3pBMEC6nC4La6A42eW9o_1KeTa6KLVgCv79fob_iABDY.vNGGBn43rzXr6gOkv1qBk8poDAW2J.tk
X-Yahoo-Newman-Property: ymail-3
Received: from [127.0.0.1] (localhost [127.0.0.1]) by postfix.incident.com (Postfix) with ESMTP id A1A2C29460F4 for <earlywarning@ietf.org>; Fri, 26 Mar 2010 09:36:32 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1077)
From: Art Botterell <acb@incident.com>
In-Reply-To: <8136DC6D-FD55-4A9F-A81B-902584B3DF6D@cs.columbia.edu>
Date: Fri, 26 Mar 2010 09:36:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <424647DE-DA3B-4141-A1A1-060B7F7195E5@incident.com>
References: <C7D24EAC.2B5BC%br@brianrosen.net> <8136DC6D-FD55-4A9F-A81B-902584B3DF6D@cs.columbia.edu>
To: earlywarning@ietf.org
X-Mailer: Apple Mail (2.1077)
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:40:01 -0000

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

v2.23.0 | Report a Bug | By Email