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

Art Botterell <artbotterell@gmail.com> Sat, 15 January 2011 21:54 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 716D43A6D49 for <earlywarning@core3.amsl.com>; Sat, 15 Jan 2011 13:54:30 -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 yn4kxeizX6Uc for <earlywarning@core3.amsl.com>; Sat, 15 Jan 2011 13:54:29 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id A4D673A6C53 for <earlywarning@ietf.org>; Sat, 15 Jan 2011 13:54:29 -0800 (PST)
Received: by qyk34 with SMTP id 34so620190qyk.10 for <earlywarning@ietf.org>; Sat, 15 Jan 2011 13:56:58 -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:x-mailer:from :subject:date:to; bh=uSYS/+iQ543H7+4pLelK6AfEAbmSg8mv9eUxmtpaY5o=; b=apqhkALURsI14nzFHEhDf5kchic0SX+cG2nJ+DgmVY8qOqMzTBAoa3n2YWzxwgOlSe mhk/6DMfEQ7pkyoVZrtRWqjYGmshRV2LVfP9sZ16EspzheCfyyYIv+t+0Kzwn8XZgfi0 33M91VpD5JhBQSzzt7sbexFgEzAGoDO98IBTg=
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:x-mailer:from:subject:date:to; b=Li1EfhJa8VdgaWKHpogIbPw6NxVIsKRN++E+ATwnUAEhz01GAIm6JC4gWRpfWEAI70 s/O9/tl6j8m4swUlxSggrLlkqGoEmlPmOQ9SBhMfbXLszqqS5VStJLjBxKjYy1L7yg4A DoHx/2Ny9VnONyICpW+FVWzhVe6crjtv6o2lE=
Received: by 10.229.83.198 with SMTP id g6mr2134098qcl.157.1295128476673; Sat, 15 Jan 2011 13:54:36 -0800 (PST)
Received: from [172.18.65.6] ([12.185.22.226]) by mx.google.com with ESMTPS id q12sm1792227qcu.42.2011.01.15.13.54.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 15 Jan 2011 13:54:35 -0800 (PST)
References: <AC859123-98E0-4188-8898-0CBBDA567FBC@gmx.net>
In-Reply-To: <AC859123-98E0-4188-8898-0CBBDA567FBC@gmx.net>
Mime-Version: 1.0 (iPad Mail 8C148)
Content-Type: text/plain; charset=us-ascii
Message-Id: <A7EF592C-E85F-4FD1-9F69-C59327D735AC@gmail.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (8C148)
From: Art Botterell <artbotterell@gmail.com>
Date: Sat, 15 Jan 2011 13:58:14 -0800
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailman-Approved-At: Sun, 16 Jan 2011 14:55:04 -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: Sat, 15 Jan 2011 21:54:30 -0000

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