Re: [earlywarning] Beijing agenda slots

sob@harvard.edu (Scott O. Bradner) Tue, 14 September 2010 14:47 UTC

Return-Path: <sob@harvard.edu>
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 2A4913A69BA for <earlywarning@core3.amsl.com>; Tue, 14 Sep 2010 07:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.151
X-Spam-Level:
X-Spam-Status: No, score=-102.151 tagged_above=-999 required=5 tests=[AWL=0.449, BAYES_00=-2.599, 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 Cla15ju+M-iK for <earlywarning@core3.amsl.com>; Tue, 14 Sep 2010 07:47:34 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id C3D573A696B for <earlywarning@ietf.org>; Tue, 14 Sep 2010 07:47:33 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id E01443322B7; Tue, 14 Sep 2010 10:47:58 -0400 (EDT)
To: br@brianrosen.net, keith.drage@alcatel-lucent.com
In-Reply-To: <187678B3-3621-44C5-94E4-AC2D208139BD@brianrosen.net>
Message-Id: <20100914144758.E01443322B7@newdev.eecs.harvard.edu>
Date: Tue, 14 Sep 2010 10:47:58 -0400
From: sob@harvard.edu
Cc: earlywarning@ietf.org
Subject: Re: [earlywarning] Beijing agenda slots
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: Tue, 14 Sep 2010 14:47:35 -0000

I think I agree with Brian - some information on how existing systems work also will
also help us to understand carrier and regulatory expectations.

Scott

----
From: Brian Rosen <br@brianrosen.net>
Date: Tue, 14 Sep 2010 10:44:42 -0400
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Cc: "earlywarning@ietf.org" <earlywarning@ietf.org>
Subject: Re: [earlywarning] Beijing agenda slots

I think it would be interesting to learn more about how it works.

I think we would like our work to be able to take advantage of any layer 2 mechanisms available that increase the rate at which notifications can be delivered to intended recipients.  Understanding how this particular layer 2 mechanism works may be helpful in making sure our higher level protocol work might use it if the operators cared to.

Brian

On Sep 14, 2010, at 10:30 AM, DRAGE, Keith (Keith) wrote:

> Can I suggest you read the charter of ATOCA before introducing 4G discussions to the meetings.
> 
> It is not the function of ATOCA to define a replacement for cell broadcast systems of warning.
> 
> Keith 
> 
>> -----Original Message-----
>> From: earlywarning-bounces@ietf.org 
>> [mailto:earlywarning-bounces@ietf.org] On Behalf Of Mark Wood
>> Sent: Tuesday, September 14, 2010 10:23 AM
>> To: Thomson, Martin
>> Cc: earlywarning@ietf.org
>> Subject: Re: [earlywarning] Beijing agenda slots
>> 
>> 
>> Hi People;
>> 
>> I am Mark Wood, the convener of the ITU-T SG2 liaison on 
>> "multicast address space harmonization for civic purposes".
>> 
>> As a matter of reference for your kind attention, I can take 
>> a few minutes to describe the mechanism of cell broadcasting 
>> in 2nd and 3rd generation mobile networks and explain the 
>> ITU-T SG2 liaison, so that we can discuss if any of the 
>> discoveries made there are of any relevance to the ATOCA 
>> deliberations or not.
>> 
>> The ITU is not seeking any infuence over IETF deliberations, 
>> but the process at ITU has been on going for 4 years, and a 
>> lot of discoveries were made in that time which you may find 
>> interesting.
>> 
>> The next ITU-T SG2 meeting is the week after the IETF, so I 
>> will be in a position to relay to them any thoughts or 
>> observations that you may have.
>> At the last ITU meeting Nov 2009, questions were raised on 
>> the matter of 4G mobile networks and how they would 
>> accommodate public warnings, so your deliberations will be of 
>> great interest to the delegates at ITU. I will of course 
>> relay to you any outcomes that the November meeting of ITU 
>> may produce.
>> 
>> May I also suggest that ATOCA be added as a 'Liason' to the 
>> ITU process and visa versa.
>> 
>> By November, member states of ITU may have submitted more 
>> liaisons of their own to ITU, which we may be able to 
>> reference for informational purposes.
>> 
>> I intend to attend the whole IETF in Beijing, so I will be 
>> available to gladly answer any questions.
>> 
>> Mark Wood DRCF.
>> 
>> 
>> 
>> 
>> 
>> 
>> On Tue, September 14, 2010 2:04 am, Thomson, Martin wrote:
>>> We've requested a time slot for ATOCA at the Beijing meeting.
>>> 
>>> If you would like to request some time on the agenda, 
>> please let us know.
>>> We're expecting to spend some time on the following drafts:
>>> 
>>>  draft-rosen-atoca-cap
>>>  draft-rosen-atoca-server-discovery
>>>  draft-schulzrinne-atoca-requirements
>>> 
>>> Expect a draft agenda in the next few weeks.
>>> 
>>> The ATOCA chairs,
>>> Scott and Martin
>>> _______________________________________________
>>> earlywarning mailing list
>>> earlywarning@ietf.org
>>> https://www.ietf.org/mailman/listinfo/earlywarning
>>> 
>> 
>> 
>> --
>> Mark Wood, CTO Cellcast Corp. mark.wood@cellcastcorp.com
>> +44 7 818 400 124
>> 
>> _______________________________________________
>> 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