Re: [earlywarning] global CAP community

[Richard Barnes <rbarnes at bbn.com>]

I wonder if it might ultimately be a good idea to deprecate the word 
"authority" for the purposes of these technical discussions, in favor of 
a more neutral term.  "Alert originator" or something like that.  The 
only characteristics of the authority/originator that this group needs 
to care about are

(1) That it's the source of alerts that the system distributes

(2) That it will need to be able to authenticate to the distribution 
system (in order to support the application of authorization policies)

Whether the entity that fulfills those criteria is a government, a 
corporation, or my Twitter feed really isn't important, as long as the 
appropriate credentials and policies have been set up.

--Richard



Brian Rosen wrote:
> Thanks for the reference to X.1303.
>
> I think we need to confine our discussions on this list to "authority to
> citizen" (although that wording is changing), and our use of CAP will be
> limited to that context.
>
> Brian
>
> -----Original Message-----
> From: earlywarning-bounces at ietf.org [mailto:earlywarning-bounces at ietf.org]
> On Behalf Of Tony Rutkowski
> Sent: Thursday, April 30, 2009 5:54 PM
> To: earlywarning at ietf.org
> Subject: [earlywarning] global CAP community
>
> Hi all,
>
> Glad to see this working group get under way.  There is a large and diverse
> global CAP community.
>
> Because the "authority" is often (but not always as Art notes) government in
> nature, or implemented pursuant to government requirements, the
> intergovernmental - industry organizations like ITU-T have been
> significantly involved.  At the domestic level, legislation like the US WARN
> Act also affect these implementations.
>
> I have attached the ITU-T X-series version of CAP 1.1.  It's a copy of the
> OASIS version, plus a translation into ASN.1 (for those who love that syntax
> or find it useful for compact applications).  It's also what most
> governmental authorities will reference in most jurisdictions.
>
> As the rapporteur of working group Q.4/17 in ITU-T, I'll try and stay
> involved in this IETF WG and keep you apprised of things happening there and
> contribute to your work.
>
> Because CAP is flexible, extensible, and ubiquitous, it's worth considering
> its application in diverse contexts.  For example, what would others think
> of using CAP in conjunction with dispersing cybersecurity forensics (think
> IODEF or CAPEX) or vulnerability
> information?   If so, what is there some larger ontology that needs
> to be developed?
>
> cheers,
> tony
>
> --
> Tony Rutkowski | Netmagic Associates LLC | Ashburn VA | mob: +1 703.999.8270
>
>
> _______________________________________________
> earlywarning mailing list
> earlywarning at ietf.org
> https://www.ietf.org/mailman/listinfo/earlywarning