Re: [earlywarning] comment on draft-rosen-atoca-server-discovery

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Tue, 20 July 2010 12:03 UTC

Return-Path: <Hannes.Tschofenig@gmx.net>
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 F38A73A6C58 for <earlywarning@core3.amsl.com>; Tue, 20 Jul 2010 05:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 tagged_above=-999 required=5 tests=[AWL=1.116, BAYES_00=-2.599]
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 3YT+5yx2wrDd for <earlywarning@core3.amsl.com>; Tue, 20 Jul 2010 05:03:42 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 94E733A6BF7 for <earlywarning@ietf.org>; Tue, 20 Jul 2010 05:03:41 -0700 (PDT)
Received: (qmail invoked by alias); 20 Jul 2010 12:03:55 -0000
Received: from unknown (EHLO [172.30.172.109]) [213.162.68.136] by mail.gmx.net (mp012) with SMTP; 20 Jul 2010 14:03:55 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/whU4vxgTwzYBlVdSG1SIiDEMRXfOtlwZ/dM3YTG qRaJoHnsWAiu4r
Message-ID: <4C4590D4.8070601@gmx.net>
Date: Tue, 20 Jul 2010 14:04:36 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: "Thomson, Martin" <Martin.Thomson@andrew.com>
References: <8B0A9FCBB9832F43971E38010638454F03E9DCD280@SISPE7MB1.commscope.com>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F03E9DCD280@SISPE7MB1.commscope.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "earlywarning@ietf.org" <earlywarning@ietf.org>
Subject: Re: [earlywarning] comment on draft-rosen-atoca-server-discovery
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, 20 Jul 2010 12:03:43 -0000

Hi Martin,


please expand a bit on what you meant with the GeoRSS comment.

The reason for having GeoRSS mentioned in there is that GeoRSS is quite 
widely used for distributing alerts and there will always be different 
ways to distribute alerts.

Are you suggesting not to use GeoRSS?

Ciao
Hannes

On 15.07.2010 05:18, Thomson, Martin wrote:
> I like this.  It's simple enough that it could just work.
>
> GeoRSS seems like a doubling up.  You can already stuff a CAP alert into Atom.  That should suffice, since the CAP alert already contains information on location.
>
> Even using Atom leads to a double up on a number of parameters, like the originator (author) of the alert.  Both Atom and CAP provide fields for this.
>
> Care will be needed (specification) to ensure that this doesn't lead to un-interoperable implementations.
>
> The draft doesn't identify what aspects of the LoST extensions are useful.  I couldn't work it out either.  As far as I can tell, the extensions will at best be marginally useful.  Either way, this needs expansion.
>
> --Martin
> _______________________________________________
> earlywarning mailing list
> earlywarning@ietf.org
> https://www.ietf.org/mailman/listinfo/earlywarning
>