Re: [Atoca] Requirement D2: "Large Audience"

"DALY, BRIAN K (ATTCINW)" <BD2985@att.com> Mon, 17 January 2011 06:33 UTC

Return-Path: <BD2985@att.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 29C8F3A6E7D for <earlywarning@core3.amsl.com>; Sun, 16 Jan 2011 22:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.251
X-Spam-Level:
X-Spam-Status: No, score=-106.251 tagged_above=-999 required=5 tests=[AWL=0.348, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 9OQYQp33C9w6 for <earlywarning@core3.amsl.com>; Sun, 16 Jan 2011 22:33:28 -0800 (PST)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id D91713A6E7B for <earlywarning@ietf.org>; Sun, 16 Jan 2011 22:33:27 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: BD2985@att.com
X-Msg-Ref: server-13.tower-161.messagelabs.com!1295246160!30297142!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.112.25]
Received: (qmail 15263 invoked from network); 17 Jan 2011 06:36:00 -0000
Received: from sbcsmtp3.sbc.com (HELO tlph064.enaf.dadc.sbc.com) (144.160.112.25) by server-13.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Jan 2011 06:36:00 -0000
Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1]) by tlph064.enaf.dadc.sbc.com (8.14.4/8.14.4) with ESMTP id p0H6ZxJM025189; Mon, 17 Jan 2011 00:36:00 -0600
Received: from td03xsmtp008.US.Cingular.Net (td03xsmtp008.us.cingular.net [135.179.64.42]) by tlph064.enaf.dadc.sbc.com (8.14.4/8.14.4) with ESMTP id p0H6ZqLS024680; Mon, 17 Jan 2011 00:35:52 -0600
Received: from bd01xsmtp004.US.Cingular.Net ([135.163.18.45]) by td03xsmtp008.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 17 Jan 2011 00:35:52 -0600
Received: from BD01MSXMB016.US.Cingular.Net ([135.214.27.50]) by bd01xsmtp004.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.4675); Sun, 16 Jan 2011 22:35:51 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Sun, 16 Jan 2011 22:35:51 -0800
Message-ID: <FDFC6E6B2064844FBEB9045DF1E3FBBC024A1E59@BD01MSXMB016.US.Cingular.Net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Atoca] Requirement D2: "Large Audience"
Thread-Index: Acu2BF5AO+s86cIvQzGY8TjhOO8dIAAADPpAAAMNqmY=
From: "DALY, BRIAN K (ATTCINW)" <BD2985@att.com>
To: <Martin.Thomson@andrew.com>, <artbotterell@gmail.com>, <hannes.tschofenig@gmx.net>
X-OriginalArrivalTime: 17 Jan 2011 06:35:51.0824 (UTC) FILETIME=[C9017900:01CBB610]
Cc: earlywarning@ietf.org
Subject: Re: [Atoca] Requirement D2: "Large Audience"
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for the IETF Authority-to-Citizen Alert \(atoca\) working group." <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: Mon, 17 Jan 2011 06:33:31 -0000

That would have to be dependent on the regional requirement and delivery mechanism. For example in the US it is not a requirement for EAS or CMAS nor can it be provided.
Brian K. Daly
   Sent to you by AT&T... 
   America's Fastest Mobile Broadband
       Network.  Rethink Possible.
   +1.425.580.6873
-------
Sent from my Blackberry

----- Original Message -----
From: earlywarning-bounces@ietf.org <earlywarning-bounces@ietf.org>;
To: Art Botterell <artbotterell@gmail.com>;; Hannes Tschofenig <hannes.tschofenig@gmx.net>;
Cc: earlywarning@ietf.org <earlywarning@ietf.org>;
Sent: Sun Jan 16 21:12:05 2011
Subject: Re: [Atoca] Requirement D2: "Large Audience"

Interesting tidbit from the Australian warning system discussions: the originating systems (the first relay) provides a report to the emergency authority on the number of deliveries.  That suggests that feedback occurs at some level.

I don't know whether this sort of reporting is something that would be part of a requirement, but I'll try to find out.

--Martin

On 2011-01-17 at 14:20:37, Art Botterell wrote:
> Mainly I was just suggesting one way of looking at the "how large is
> 'large'" question.  Although it does highlight some of Martin's
> questions about how to adapt a session initiation protocol to a one-to-
> very-many application, if that's what we have in mind.  As he rightly
> points out, responses don't only happen at the application level.
> 
> Thanks!
> 
> - Art
> 
> On Jan 16, 2011, at 11:22 AM, Hannes Tschofenig
> <hannes.tschofenig@gmx.net>; wrote:
> 
> > Hi Art,
> >
> > that's an interesting comment particularly since we do not have a
> requirement for responses by receivers (or Recipients) of alert
> messages. I am not sure to whom they would sent their response to. To
> the originator, to some gateway, etc?
> >
> > Ciao
> > Hannes
> >
> > On Jan 15, 2011, at 11:58 PM, Art Botterell wrote:
> >
> >> One difference in "broadcast" delivery is that it's frequntly
> impractical and/or undesirable to try to track individual deliveries or
> process individual responses.
> >>
> >> Thanks!
> >>
> >> - Art
> >>
> >> On Jan 15, 2011, at 11:30 AM, Hannes Tschofenig
> <hannes.tschofenig@gmx.net>; wrote:
> >>
> >>> Hi all,
> >>>
> >>> during the ATOCA meeting at IETF#79 Igor raised a question
> regarding requirement D2:
> >>> "
> >>> Req-D2:
> >>>
> >>>    The protocol solution MUST allow delivery of messages
> >>>    simultaneously to a large audience.
> >>> "
> >>>
> >>> He was asking whether there is a need to put a number for large
> audience there.
> >>>
> >>> Maybe Igor has a specific number in mind that would matter from a
> protocol design perspective but I do not have such a number that would
> provide a meaningful distinction.
> >>>
> >>> There is, however, the question what types of problems we expect
> with very large number of alert message receivers and how we document
> this aspect in the requirements document.
> >>>
> >>> Suggestions? Thoughts?
> >>>
> >>> Ciao
> >>> Hannes
> >>>
> >>> _______________________________________________
> >>> 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


_______________________________________________
earlywarning mailing list
earlywarning@ietf.org
https://www.ietf.org/mailman/listinfo/earlywarning