IETF Logo Mail Archive

Re: [atoca] Call for submissions: Secure Alert Format

"Richard L. Barnes" <rbarnes@bbn.com> Fri, 17 August 2012 22:20 UTC

Return-Path: <rbarnes@bbn.com>
X-Original-To: atoca@ietfa.amsl.com
Delivered-To: atoca@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3C711E80D1 for <atoca@ietfa.amsl.com>; Fri, 17 Aug 2012 15:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.579
X-Spam-Level:
X-Spam-Status: No, score=-106.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Q54m306RTDw for <atoca@ietfa.amsl.com>; Fri, 17 Aug 2012 15:20:20 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 8E83911E80A4 for <atoca@ietf.org>; Fri, 17 Aug 2012 15:20:20 -0700 (PDT)
Received: from ros-dhcp192-1-51-103.bbn.com ([192.1.51.103]:58977) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1T2Utt-0008Yy-Ig; Fri, 17 Aug 2012 18:20:17 -0400
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <CABkgnnW76T3PSMx-fPJHTE7kurGMy1mJOXZDm6fBpQV2GpzFtQ@mail.gmail.com>
Date: Fri, 17 Aug 2012 18:20:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CFFEC72-1B54-4906-938D-1EDBB67CBF6F@bbn.com>
References: <CABkgnnXaDp-3D4msWLXQo8WCxojqMLp04ZSLa2P8YfXrGCGzOA@mail.gmail.com> <502E9627.4030008@stpeter.im> <22E8EC45-F535-4304-8C80-B2E17F59902C@bbn.com> <CABkgnnW76T3PSMx-fPJHTE7kurGMy1mJOXZDm6fBpQV2GpzFtQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: atoca@ietf.org
Subject: Re: [atoca] Call for submissions: Secure Alert Format
X-BeenThere: atoca@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for the IETF Authority-to-Citizen Alert \(atoca\) working group." <atoca.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/atoca>, <mailto:atoca-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/atoca>
List-Post: <mailto:atoca@ietf.org>
List-Help: <mailto:atoca-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/atoca>, <mailto:atoca-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 22:20:21 -0000

>> I think we were thinking of things in kind of the other direction:
>> 1. Define a general signed alert format
>> 2. Define a way to transport those over XMPP (XEP-0127-bis)
> 
> And we are doing 1, just 1.
> 
> If this succeeds, we can talk about doing 2, or something else.

Yep, that's what I meant.  Just outlining the broader MO.


> I should also point out that CAP does specify a signing capability
> based on XMLDsig.  One potential outcome is that a profile of XMLDsig
> is developed that can be used in this context.  Based on what I know
> of XMLDsig, that seems unlikely, but this is ultimately a decision for
> the working group.

Do you know if any of the real CAP implementations out there use this mechanism?

v2.23.0 | Report a Bug | By Email