Re: [earlywarning] (no subject)

creed@opengeospatial.org Fri, 26 March 2010 14:56 UTC

Return-Path: <creed@opengeospatial.org>
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 227773A68A7 for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 07:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.819
X-Spam-Level:
X-Spam-Status: No, score=-0.819 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 7P3G4b1IV-Cc for <earlywarning@core3.amsl.com>; Fri, 26 Mar 2010 07:56:48 -0700 (PDT)
Received: from mail.opengeospatial.org (mail.opengeospatial.org [66.244.86.40]) by core3.amsl.com (Postfix) with ESMTP id 0B1773A6827 for <earlywarning@ietf.org>; Fri, 26 Mar 2010 07:56:47 -0700 (PDT)
Received: from mail.opengeospatial.org (localhost [127.0.0.1]) by mail.opengeospatial.org (8.13.8/8.13.8/Debian-3+etch1) with ESMTP id o2QEv5un006962; Fri, 26 Mar 2010 10:57:05 -0400
Received: from 198.123.49.132 (SquirrelMail authenticated user creed) by mail.opengeospatial.org with HTTP; Fri, 26 Mar 2010 10:57:05 -0400 (EDT)
Message-ID: <62345.198.123.49.132.1269615425.squirrel@mail.opengeospatial.org>
In-Reply-To: <016DD2D0-90AB-487F-8530-011FEFA67DA6@g11.org.uk>
References: <FDFC6E6B2064844FBEB9045DF1E3FBBC315B91@BD01MSXMB016.US.Cingular.Net> <C7D1712F.2B4B9%br@brianrosen.net> <FDFC6E6B2064844FBEB9045DF1E3FBBC315B9C@BD01MSXMB016.US.Cingular.Net> <016DD2D0-90AB-487F-8530-011FEFA67DA6@g11.org.uk>
Date: Fri, 26 Mar 2010 10:57:05 -0400
From: creed@opengeospatial.org
To: ken carlberg <carlberg@g11.org.uk>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: ClamAV 0.92.1/10628/Fri Mar 26 09:57:50 2010 on mail.opengeospatial.org
X-Virus-Status: Clean
Cc: "DALY, BRIAN K (ATTCINW)" <bd2985@att.com>, earlywarning@ietf.org
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 14:56:49 -0000

Absolutely agree! The OGC Members have developed and are working alerting
and warning applications in many countries. Many different
infrastructures, policies, and endpoints. FCC rules do not apply :-)

Carl


> please, let's remember not to be U.S. centric.
>
> -ken
>
>
> On Mar 25, 2010, at 8:03 PM, DALY, BRIAN K (ATTCINW) wrote:
>
>> They are connected to the wireless network and under FCC rules the CMSP
>> has responsibility for delivering emergency alerts to those devices
>> under FCC Part 10 rules and the CMSP election to provide those alerts.
>>
>> So no, this work does not apply. CMAS applies to those devices.
>>
>> Brian Daly
>>
>> From: Brian Rosen [mailto:br@brianrosen.net]
>> Sent: Thursday, March 25, 2010 5:00 PM
>> To: DALY, BRIAN K (ATTCINW); earlywarning@ietf.org
>> Subject: Re: [earlywarning] (no subject)
>>
>> Are they connected to the Internet?
>>
>> If they are, it would apply.  If they aren’t, then it wouldn’t apply.
>>
>> Brian
>>
>>
>> On 3/25/10 7:51 PM, "DALY, BRIAN K (ATTCINW)" <BD2985@att.com> wrote:
>>
>> That will not apply to devices connected to wireless cellular networks.
>>
>>
>> From: Brian Rosen [mailto:br@brianrosen.net]
>> Sent: Thursday, March 25, 2010 4:50 PM
>> To: DALY, BRIAN K (ATTCINW); earlywarning@ietf.org
>> Subject: Re: [earlywarning] (no subject)
>>
>> Once again, this is NOT about a solution limited to wireless cellular
>> networks.  It is about a solution for internet connected endpoints of
>> all kinds.
>>
>> Brian
>>
>>
>> On 3/25/10 7:46 PM, "DALY, BRIAN K (ATTCINW)" <BD2985@att.com> wrote:
>> Keith – We agree with you, and to further the point, in wireless
>> cellular IP networks a point to point solution would be problematic.
>> Cell Broadcast is used for CMAS because SMS cannot be used for any real
>> time alerting – it was not designed for that application and has serious
>> limitations, as the FCC CMSAAC studied.
>>
>> When it comes to the evolved packet core and IMS, again a point to point
>> solution  will cause significant congestion on the network and a
>> broadcast/multicast solution must be used to effectively deliver alert
>> messages. Thus things like location and “priority” are already handled
>> in the delivery network.
>>
>> ATIS and 3GPP will be studying how to support multimedia alerts in the
>> future, as recommended by the FCC CMSAAC. This is all beyond the scope
>> of this work effort.
>>
>> Regards,
>> Brian
>>
>> Date: Thu, 25 Mar 2010 03:13:24 +0100
>> From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
>> Subject: Re: [earlywarning] Updated Charter Text for ATOCA
>> To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>,
>>       "earlywarning@ietf.org" <earlywarning@ietf.org>
>> Message-ID:
>>       <EDC0A1AE77C57744B664A310A0B23AE20D1639BB@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
>>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> What I am not seeing here is any separation of the problem from the one
>> that cell broadcast attempts to solve. Fundamentally, cell broadcast, as
>> exists on all GSM, UTRAN and E-UTRAN based cell phones and is being used
>> for Tsunami warning and Public Warning, exists and is not going to
>> substantially change. The major limitation here is is length of message,
>> and what does get transmitted will be very much dependent on that
>> restriction.
>>
>> Moreover I have heard from a number of governmental bodies that they are
>> happy with that situation and are not envisaging further standardisation
>> in that area outside of 3GPP.
>>
>> So my view at the moment is that there is no point in IETF trying to
>> address the scope of what is already specified in cell broadcast (from
>> base station to end mobile).
>>
>> regards
>>
>> Keith
>>
>>
>>
>> _______________________________________________
>> 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
>