Reliable Delivery for syslog
draft-ietf-syslog-rfc3195bis-00
| Document | Type | Expired Internet-Draft (syslog WG) | |
|---|---|---|---|
| Last updated | 2007-11-08 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-syslog-rfc3195bis-00.txt
Abstract
The syslog protocol describes a number of service options related to propagating event messages. This memo describes a mapping of the syslog protocol to TCP connections, useful for reliable delivery of event messages through the use of a BEEP profile. The earlier RAW and COOKED BEEP syslog profiles are deprecated. The use of syslog over BEEP provides robustness and security in message delivery that is unavailable to the usual UDP-based syslog protocol, by providing encryption and authentication over a connection-oriented protocol.
Authors
Darren New
(dnew@san.rr.com)
Marshall Rose
(mrose+mtr.mxcomp@dbc.mtview.ca.us)
Eliot Lear
(lear@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)