Protocol Action: 'Transmission of Syslog Messages over TCP' to Historic (draft-gerhards-syslog-plain-tcp-14.txt)
The IESG <iesg-secretary@ietf.org> Tue, 21 February 2012 23:32 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B15FB21E801A for <ietf-announce@ietfa.amsl.com>; Tue, 21 Feb 2012 15:32:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.636
X-Spam-Level:
X-Spam-Status: No, score=-102.636 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id noCjWKGU1SoY; Tue, 21 Feb 2012 15:32:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E51D821E8022; Tue, 21 Feb 2012 15:32:31 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Transmission of Syslog Messages over TCP' to Historic (draft-gerhards-syslog-plain-tcp-14.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p2
Message-ID: <20120221233231.13179.32311.idtracker@ietfa.amsl.com>
Date: Tue, 21 Feb 2012 15:32:31 -0800
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2012 23:32:39 -0000
The IESG has approved the following document: - 'Transmission of Syslog Messages over TCP' (draft-gerhards-syslog-plain-tcp-14.txt) as a Historic This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Dan Romascanu. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-gerhards-syslog-plain-tcp/ Technical Summary There have been many implementations and deployments of legacy syslog over TCP for many years. That protocol has evolved without being standardized and has proven to be quite interoperable in practice. The aim of this specification is to explain how TCP has been used as a transport for syslog messages. Working Group Summary The document is an individual submission and not associated with any Working Group. It is, however, a work that is of interest to the syslog Working Group which was concluded in October of 2010. The document has been discussed on the IETF mailing list that was used for the syslog Working Group. The WG mailing list seems content with the document. The document was also IETF last called. Document Quality There are at least six existing implementations of the protocol. Personnel Randy Presuhn is the Document Shepherd for this document. Dan Romascanu is the sponsoring AD. IESG Note The IESG does NOT RECOMMEND implementing or deploying syslog over plain tcp, which is documented in this document, because it lacks the ability to enable strong security [BCP61]. Syslog over TLS transport [RFC5425] is recommended for implementation so that security features are available to operators who want to deploy secure syslog, and those security features can be turned off for those who do not want them.