Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript.
Please enable Javascript for full functionality.
The BSD Syslog Protocol
draft-ietf-syslog-syslog-12
The information below is for an old version of the document that is already published as an RFC.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3164.
|
|---|---|---|
| Author | Chris M. Lonvick | |
| Last updated | 2013年03月02日 (Latest revision 2001年05月31日) | |
| RFC stream | Internet Engineering Task Force (IETF) | |
| Intended RFC status | Informational | |
| Formats | ||
| Additional resources | Mailing list discussion | |
| Stream | WG state | (None) |
| Document shepherd | (None) | |
| IESG | IESG state | Became RFC 3164 (Informational) |
| Consensus boilerplate | Unknown | |
| Telechat date | (None) | |
| Responsible AD | (None) | |
| Send notices to | (None) |
draft-ietf-syslog-syslog-12
A new Request for Comments is now available in online RFC libraries. RFC 3164 Title: The BSD Syslog Protocol Author(s): C. Lonvick Status: Informational Date: August 2001 Mailbox: clonvick@cisco.com Pages: 29 Characters: 72951 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-syslog-syslog-12.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3164.txt This document describes the observed behavior of the syslog protocol. This protocol has been used for the transmission of event notification messages across networks for many years. While this protocol was originally developed on the University of California Berkeley Software Distribution (BSD) TCP/IP system implementations, its value to operations and management has led it to be ported to many other operating systems as well as being embedded into many other networked devices. This document is a product of the Security Issues in Network Event Logging Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.