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

Matt Lepinski <mlepinski@bbn.com> Fri, 17 August 2012 18:50 UTC

Return-Path: <mlepinski@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 7CD0F11E80E1 for <atoca@ietfa.amsl.com>; Fri, 17 Aug 2012 11:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 r4JsYSPxsuJS for <atoca@ietfa.amsl.com>; Fri, 17 Aug 2012 11:50:07 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id DAFF711E80A5 for <atoca@ietf.org>; Fri, 17 Aug 2012 11:50:06 -0700 (PDT)
Received: from mail.bbn.com ([128.33.0.48]:34179) by smtp.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mlepinski@bbn.com>) id 1T2RcP-0005dY-Bw for atoca@ietf.org; Fri, 17 Aug 2012 14:50:01 -0400
Received: from [128.89.254.21] by mail.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <mlepinski@bbn.com>) id 1T2RcP-0003jy-7q for atoca@ietf.org; Fri, 17 Aug 2012 14:50:01 -0400
Message-ID: <502E9276.2060003@bbn.com>
Date: Fri, 17 Aug 2012 14:50:30 -0400
From: Matt Lepinski <mlepinski@bbn.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: atoca@ietf.org
References: <CABkgnnXaDp-3D4msWLXQo8WCxojqMLp04ZSLa2P8YfXrGCGzOA@mail.gmail.com>
In-Reply-To: <CABkgnnXaDp-3D4msWLXQo8WCxojqMLp04ZSLa2P8YfXrGCGzOA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 18:50:07 -0000

This sounds like a good path forward.

I believe that draft-barnes-atoca-escape-00 is a very rough first cut at 
a secure transport/delivery agnostic mechanism for authenticating 
CAP-formatted alerts.

Note that draft-barnes-atoca-escape-00 has a section devoted to open 
questions. If you have an answer to any of these questions, or 
additional questions not considered in the draft please send mail to the 
list. Also, if this is totally the wrong approach for authenticating CAP 
alerts, please send mail to the list.

- Matt Lepinski

On 8/17/2012 2:34 PM, Martin Thomson wrote:
> The ATOCA WG needs you.
>
> It has been determined that providing a means of authenticating alerts
> is critical to the working group.
>
> Please submit internet drafts containing proposals that address this
> problem before September 12.
>
> Such a proposal must be able to carry CAP-formatted alerts in such a
> way that the source(s) of the alert can be authenticated by
> recipients.  Attributing trust to that source is not necessarily
> within scope, nor is it necessary to describe a protocol or delivery
> architecture.
>
> A submission made earlier than this date will give us more time to
> discuss it.  That is good if we are to meet our later milestones for
> adoption and publication.
> _______________________________________________
> atoca mailing list
> atoca@ietf.org
> https://www.ietf.org/mailman/listinfo/atoca
>