Encoding of Secure Common Alert Protocol Entities (ESCAPE)
draft-barnes-atoca-escape-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Richard Barnes , Andrew Chi | ||
| Last updated | 2013-04-13 (Latest revision 2012-10-10) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Recipients of emergency alerts need to be able to verify that an alert they receive was issued by an authorized source. The Common Alerting Protocol (CAP) provides a standard way of encoding alert information. This document describes a security wrapper for Common Alerting Protocol objects to allow alerts to be signed by alert originators. Please send feedback to the atoca@ietf.org mailing list.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)