idnits 2.17.1 draft-ietf-syslog-syslog-12.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3164 5 Title: The BSD Syslog Protocol 6 Author(s): C. Lonvick 7 Status: Informational 8 Date: August 2001 9 Mailbox: clonvick@cisco.com 10 Pages: 29 11 Characters: 72951 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-syslog-syslog-12.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3164.txt 18 This document describes the observed behavior of the syslog 19 protocol. This protocol has been used for the transmission of 20 event notification messages across networks for many years. While 21 this protocol was originally developed on the University of 22 California Berkeley Software Distribution (BSD) TCP/IP system 23 implementations, its value to operations and management has led 24 it to be ported to many other operating systems as well as being 25 embedded into many other networked devices. 27 This document is a product of the Security Issues in Network Event 28 Logging Working Group of the IETF. 30 This memo provides information for the Internet community. It does 31 not specify an Internet standard of any kind. Distribution of this 32 memo is unlimited. 34 This announcement is sent to the IETF list and the RFC-DIST list. 35 Requests to be added to or deleted from the IETF distribution list 36 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 37 added to or deleted from the RFC-DIST distribution list should 38 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 40 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 41 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 42 help: ways_to_get_rfcs. For example: 44 To: rfc-info@RFC-EDITOR.ORG 45 Subject: getting rfcs 47 help: ways_to_get_rfcs 49 Requests for special distribution should be addressed to either the 50 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 51 specifically noted otherwise on the RFC itself, all RFCs are for 52 unlimited distribution.echo 53 Submissions for Requests for Comments should be sent to 54 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 55 Authors, for further information.