IETF Logo Mail Archive

Re: [earlywarning] (no subject)

Art Botterell <acb@incident.com> Fri, 26 March 2010 01:49 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 971BA3A68C0 for <earlywarning@core3.amsl.com>; Thu, 25 Mar 2010 18:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.725
X-Spam-Level:
X-Spam-Status: No, score=0.725 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 0Hwj3XsYa8zO for <earlywarning@core3.amsl.com>; Thu, 25 Mar 2010 18:49:28 -0700 (PDT)
Received: from smtp126.sbc.mail.sp1.yahoo.com (smtp126.sbc.mail.sp1.yahoo.com [69.147.65.185]) by core3.amsl.com (Postfix) with SMTP id B291E3A67F2 for <earlywarning@ietf.org>; Thu, 25 Mar 2010 18:49:28 -0700 (PDT)
Received: (qmail 23410 invoked from network); 26 Mar 2010 01:49:50 -0000
Received: from 99-182-125-96.lightspeed.frokca.sbcglobal.net (acb@99.182.125.96 with login) by smtp126.sbc.mail.sp1.yahoo.com with SMTP; 25 Mar 2010 18:49:49 -0700 PDT
X-Yahoo-SMTP: c09pd_2swBAlwYa9BknTHpHNRHUh4Oco4AeV8DAru96p
X-YMail-OSG: _atzdtYVM1kQC3qpanyrNWK5JqN275MNkWm7I.PmWoRaZKqhPwBlXBu.JB3xDuDAe15wICPYBz9FYZp6BEbuRPQdcvfB13VHinn1mLeDAyMRYx.Ab_r3lCwqPsd1_T0LfgkaPID6_baPKdpgoADaoZOIIHdHHWWQaLnSHjNxK3xB5.79eimAZOJ.GYXNYiTtqMwCsNnO319Dlu6oVHPMVs100rBuQvC16ZlmQE0oNRP62uFC0KzDykZVb0FhZbTg
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 43F92294346C for <earlywarning@ietf.org>; Thu, 25 Mar 2010 18:49:47 -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: <5A55A45AE77F5941B18E5457ECAC81880120DFB13541@SISPE7MB1.commscope.com>
Date: Thu, 25 Mar 2010 18:49:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <93214F63-3643-4FA0-9E57-D48CD58CEE5E@incident.com>
References: <FDFC6E6B2064844FBEB9045DF1E3FBBC093CB9@BD01MSXMB016.US.Cingular.Net> <5A55A45AE77F5941B18E5457ECAC81880120DFB13541@SISPE7MB1.commscope.com>
To: earlywarning@ietf.org
X-Mailer: Apple Mail (2.1077)
Subject: Re: [earlywarning] (no subject)
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 01:49:29 -0000

On Mar 25, 2010, at 3/25/10 6:40 PM, Winterbottom, James wrote:
> ...it is quite possible that alerts could be received by either or both means at the same time.

FWIW that problem already arises in a variety of transport domains, so CAP addresses it at the application level.  Alerts have unique identifiers for that purpose, and also to allow the mapping of subsequent update and cancellation messages.

- Art

v2.23.0 | Report a Bug | By Email