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

Art Botterell <artbotterell@gmail.com> Mon, 17 January 2011 03:43 UTC

Return-Path: <artbotterell@gmail.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 35A543A6E6F for <earlywarning@core3.amsl.com>; Sun, 16 Jan 2011 19:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level:
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 EQdg-bxrhGJs for <earlywarning@core3.amsl.com>; Sun, 16 Jan 2011 19:43:42 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id DB8CD3A6DA6 for <earlywarning@ietf.org>; Sun, 16 Jan 2011 19:43:41 -0800 (PST)
Received: by yxt33 with SMTP id 33so2024978yxt.31 for <earlywarning@ietf.org>; Sun, 16 Jan 2011 19:46:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:in-reply-to:mime-version :content-type:message-id:content-transfer-encoding:cc:from:subject :date:to:x-mailer; bh=JSAcpfhbSo42vq7O42WcsWsism9U4rWlQdGxQI3MWTE=; b=PQrxWc0DLBInUd11e/kHKK9kw5hkaDS85BukMdYUTiQu0sQRfp0CZJ5CcpQ8CRLJGI Y/yn9LJELRKqNvWplUeOJgut6r6+3febSTZNqZR7nKQokblOk2WU62A45GY0S6Oo7cNI V6bv15S+SED1PVX9XnYl/zdhUyZ6AQmcdal9s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=eXlPL+mi69OEQnowy0j786FKsdHlXtkLZMouO77vuZGynQWmE9FcnHZ2AhO5VDbwPY +9z20tJ/daDajrY/Cp+dcE1l5XxngNawA/xIAQI9lrVz/cGgMl3Yjbp5hcZvbWHAThCk l3ZJCd6BUfSKtqilAGTJZOiHVp33frgC7LLQ0=
Received: by 10.150.198.7 with SMTP id v7mr3784479ybf.328.1295235973320; Sun, 16 Jan 2011 19:46:13 -0800 (PST)
Received: from [10.10.1.90] ([200.6.58.236]) by mx.google.com with ESMTPS id w24sm1896188ybk.9.2011.01.16.19.46.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 16 Jan 2011 19:46:11 -0800 (PST)
References: <AC859123-98E0-4188-8898-0CBBDA567FBC@gmx.net> <A7EF592C-E85F-4FD1-9F69-C59327D735AC@gmail.com> <1285F7FB-FFBE-4B49-87F8-FCDCDF1F1AD3@gmx.net>
In-Reply-To: <1285F7FB-FFBE-4B49-87F8-FCDCDF1F1AD3@gmx.net>
Mime-Version: 1.0 (iPad Mail 8C148)
Content-Type: text/plain; charset=us-ascii
Message-Id: <8DB1F455-6444-4FC6-841A-60242CAAE0BC@gmail.com>
Content-Transfer-Encoding: quoted-printable
From: Art Botterell <artbotterell@gmail.com>
Date: Sun, 16 Jan 2011 23:20:37 -0400
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: iPad Mail (8C148)
X-Mailman-Approved-At: Sun, 16 Jan 2011 21:03:52 -0800
Cc: Igor Faynberg <igor.faynberg@alcatel-lucent.com>, "earlywarning@ietf.org" <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 03:43:44 -0000

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
>