Re: [Atoca] I-D Action:draft-ietf-atoca-cap-00.txt

"Thomson, Martin" <Martin.Thomson@andrew.com> Mon, 18 October 2010 21:48 UTC

Return-Path: <Martin.Thomson@andrew.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 84AA63A69AD for <earlywarning@core3.amsl.com>; Mon, 18 Oct 2010 14:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.895
X-Spam-Level:
X-Spam-Status: No, score=-2.895 tagged_above=-999 required=5 tests=[AWL=-0.296, 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 MtgAm6TO5iQa for <earlywarning@core3.amsl.com>; Mon, 18 Oct 2010 14:48:25 -0700 (PDT)
Received: from csmailgw1.commscope.com (csmailgw1.commscope.com [198.135.207.244]) by core3.amsl.com (Postfix) with ESMTP id D90943A6AB6 for <earlywarning@ietf.org>; Mon, 18 Oct 2010 14:48:24 -0700 (PDT)
Received: from [10.86.20.102] ([10.86.20.102]:53360 "EHLO ACDCE7HC1.commscope.com") by csmailgw1.commscope.com with ESMTP id S35740952Ab0JRVty (ORCPT <rfc822; earlywarning@ietf.org>); Mon, 18 Oct 2010 16:49:54 -0500
Received: from SISPE7HC2.commscope.com (10.97.4.13) by ACDCE7HC1.commscope.com (10.86.20.102) with Microsoft SMTP Server (TLS) id 8.1.436.0; Mon, 18 Oct 2010 16:49:53 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC2.commscope.com ([fe80::58c3:2447:f977:57c3%10]) with mapi; Tue, 19 Oct 2010 05:49:51 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: Art Botterell <acb@incident.com>, "earlywarning@ietf.org" <earlywarning@ietf.org>
Date: Tue, 19 Oct 2010 05:49:49 +0800
Thread-Topic: [Atoca] I-D Action:draft-ietf-atoca-cap-00.txt
Thread-Index: Actuz3r7fx6LvwfCTAC7araQRLXALQAPlwPA
Message-ID: <8B0A9FCBB9832F43971E38010638454F03F31EA75C@SISPE7MB1.commscope.com>
References: <20101018123003.D1D0A3A6ADC@core3.amsl.com> <37FBCC74-36A9-4B5A-9F65-13EC903A24FF@incident.com>
In-Reply-To: <37FBCC74-36A9-4B5A-9F65-13EC903A24FF@incident.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw1.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Subject: Re: [Atoca] I-D Action:draft-ietf-atoca-cap-00.txt
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: Mon, 18 Oct 2010 21:48:26 -0000

Hi Art,

The ASN.1 definition (BER serialization? PER?) was something that I was unaware of.  That being the case, we should probably make a statement about it.  Support/don't support?  Mandatory to implement/optional/prohibited?  

If it is possible to carry such a serialization at all, it would seem that we'd need a new media type.

Regarding filtering, that might be a good idea, but the general pattern we've adopted in other groups is to advance filter work as a separate draft.

--Martin (Individual)

-----Original Message-----
From: earlywarning-bounces@ietf.org [mailto:earlywarning-bounces@ietf.org] On Behalf Of Art Botterell
Sent: Tuesday, 19 October 2010 1:19 AM
To: earlywarning@ietf.org
Subject: Re: [Atoca] I-D Action:draft-ietf-atoca-cap-00.txt

Looks good.

Maybe I should point out, for whatever it may be worth, that CAP is not only an XML specification.  There is also an ASN.1 serialization specified in versions 1.1 and 1.2 as part of the harmonization effort by which the ITU-T co-designated it as x.1303.  A detail, but thought I'd mention it for precision's sake.

Also, I'd suggest that a subscription filter might be added for alert source (<cap:sender>).  In addition to restricting sourcing to identified authoritative sources, which some consumers will wish to do, that might facilitate some sorts of proxy arrangements.

- Art


On Oct 18, 2010, at 10/18/10 5:30 AM, Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Authority-to-Citizen Alert Working Group of the IETF.
> 
> 
> 	Title           : Session Initiation Protocol (SIP) Event Package for the Common Alerting Protocol (CAP)
> 	Author(s)       : B. Rosen, et al.
> 	Filename        : draft-ietf-atoca-cap-00.txt
> 	Pages           : 22
> 	Date            : 2010-10-18
> 
> The Common Alerting Protocol (CAP) is an XML document format for
> exchanging emergency alerts and public warnings.  This document
> allows CAP documents to be distributed via the event notification
> mechanism available with the Session Initiation Protocol (SIP).
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-atoca-cap-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <Mail Attachment>_______________________________________________
> 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