IETF Logo Mail Archive

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

Art Botterell <acb@incident.com> Fri, 26 March 2010 16:30 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 5F9113A6BCE for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 09:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.28
X-Spam-Level: *
X-Spam-Status: No, score=1.28 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 aFFy3NyHc8W3 for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 09:30:46 -0700 (PDT)
Received: from smtp109.sbc.mail.gq1.yahoo.com (smtp109.sbc.mail.gq1.yahoo.com [67.195.14.39]) by core3.amsl.com (Postfix) with SMTP id 527F83A6C28 for <earlywarning@ietf.org>; Fri, 26 Mar 2010 09:25:58 -0700 (PDT)
Received: (qmail 94383 invoked from network); 26 Mar 2010 16:26:19 -0000
Received: from 99-182-125-96.lightspeed.frokca.sbcglobal.net (acb@99.182.125.96 with login) by smtp109.sbc.mail.gq1.yahoo.com with SMTP; 26 Mar 2010 09:26:19 -0700 PDT
X-Yahoo-SMTP: c09pd_2swBAlwYa9BknTHpHNRHUh4Oco4AeV8DAru96p
X-YMail-OSG: x6BFLGQVM1lW6Zqp03ANTHhN2miKB8_GYZdsk4Jd6DYs0WtgzVChByXFjAgXWlZv9SZcZzCIT27EVmUCZy_Zjh8OJY5fi8_M5fm6E3jZ8NCrUeyht3gQ93.MhR0ELZyBkk8e_o2jVy8BLwRm1KFjUe1.P1Ak_.iXgN5OwFBexLIAlrXk0Jqg9EDeCR5inhsiqeDXixuL0019wMhBp1Xoyd0FwBGRtXL92713fy9iOGzYhAJURe_gCmRXWdxY4DYk
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 A125D2946019 for <earlywarning@ietf.org>; Fri, 26 Mar 2010 09:26:16 -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: <C7D24EAC.2B5BC%br@brianrosen.net>
Date: Fri, 26 Mar 2010 09:26:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F548A082-D0BD-4FC9-B1B2-F63185E74658@incident.com>
References: <C7D24EAC.2B5BC%br@brianrosen.net>
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:30:47 -0000

On Mar 26, 2010, at 3/26/10 8:44 AM, Brian Rosen wrote:
> We're not at the mechanism state yet.

True, and that's not really what I meant.  My point was that the shapes of the problem and the constraints seem similar to the more general problem of multicasting, on which there's been a lot of prior work.

So perhaps it would be useful to enumerate the particular ways in which this problem ISN'T just an instance of multicasting.

- Art

v2.23.0 | Report a Bug | By Email