Alert and Notification Format
draft-kocheisen-alert-format-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jean Tessier , Jocelyn Cloutier | ||
| Last updated | 1999-10-20 | ||
| 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
The Alert Format defines the MIME type message/alert. It describes how alerts and notifications are formatted in order that they can be sent and received by alert transport agents and alert receivers. The alert format is transport independent. However, in most parts it simply extends RFC 822 [RFC822] and uses RFC 2045 [MIME1], such that any RFC 822 or RFC 2045 message represents a simple and valid alert.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)