IETF Logo Mail Archive

Re: [earlywarning] [CAP] Definition of Warning Categories

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Wed, 15 July 2009 19:10 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 495823A69CD for <earlywarning@core3.amsl.com>; Wed, 15 Jul 2009 12:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372, 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 CqShV2zXYaw6 for <earlywarning@core3.amsl.com>; Wed, 15 Jul 2009 12:10:52 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 5A8AF3A6A56 for <earlywarning@ietf.org>; Wed, 15 Jul 2009 12:10:52 -0700 (PDT)
Received: (qmail invoked by alias); 15 Jul 2009 17:22:49 -0000
Received: from a91-154-108-144.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.108.144] by mail.gmx.net (mp026) with SMTP; 15 Jul 2009 19:22:49 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/XBjtUHN7X0p/SzY004SlaWL05XSnNRYNMbdIulN FnBiUkkT0MwrKN
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
To: acb@incident.com
References: <82AE05D27DEDB04488869E55FDAB71FDA1C0FB@s-gov-mail-4.govaxa.ai> <18ee01ca0322$b7a97d30$501ca20a@nsnintra.net> <30076E62-60BC-4488-9F10-33686E82E657@incident.com> <34E56644D3334E8D876CD9368814657E@xppc1> <XFE-SJC-211xvjPkQTG00001d60@xfe-sjc-211.amer.cisco.com> <EDC0A1AE77C57744B664A310A0B23AE20702F355@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4A5DD81E.7090803@netmagic.com> <021501ca0551$bca043b0$1116a20a@nsnintra.net> <2e53e6590907151002k4b12905di6e29ac0bbda8721c@mail.gmail.com>
Date: Wed, 15 Jul 2009 20:25:07 +0300
Message-ID: <022b01ca0571$33de2400$1116a20a@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <2e53e6590907151002k4b12905di6e29ac0bbda8721c@mail.gmail.com>
thread-index: AcoFbgMZx0rAXyhDSIeq94f6rP5cPgAAeEow
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.63
Cc: earlywarning@ietf.org
Subject: Re: [earlywarning] [CAP] Definition of Warning Categories
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: Wed, 15 Jul 2009 19:10:54 -0000

Hi Art, 

~snip~

#	What we're really talking about here seems to be how to apply SIP to
urgent one-to-many notifications.  Maybe if it were explicit that narrower,
more technical goal would be more tractable.

For me the scope of the work is quite narrow.

I re-wrote the requirements, terminology and framework document
http://tools.ietf.org/id/draft-norreys-ecrit-authority2individuals-requireme
nts-03.txt
based also on your feedback to re-scope the work. 

Then, there is the SIP CAP document 
http://tools.ietf.org/html/draft-rosen-sipping-cap-04
(It needs to get re-written a bit to better incorporate the new terminology.
Maybe requesting specific warning categories is a bad idea and needs to be
deleted.)

There is also a document
http://tools.ietf.org/id/draft-rosen-ecrit-lost-early-warning-01.txt that
may be needed to discover servers dynamically. But this is clearly more into
the future.

Looking at the XMPP work
http://xmpp.org/extensions/xep-0127.html
we could get away with only a single document, namely the SIP CAP stuff.

I would scope the initial work in that way. 

Ciao
Hannes	

	- Art

v2.23.0 | Report a Bug | By Email