IETF Logo Mail Archive

Re: [Syslog] stream transport wasdraft-ietf-syslog-transport-tls-01.txt

Darren J Moffat <Darren.Moffat@Sun.COM> Tue, 20 June 2006 08:53 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsbz9-000864-V4; Tue, 20 Jun 2006 04:53:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsbz8-00081n-8f for syslog@ietf.org; Tue, 20 Jun 2006 04:53:22 -0400
Received: from gmpea-pix-1.sun.com ([192.18.1.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fsbz6-0003Hd-Rr for syslog@ietf.org; Tue, 20 Jun 2006 04:53:22 -0400
Received: from d1-emea-06.sun.com ([192.18.2.116]) by gmpea-pix-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k5K8rFI9017272 for <syslog@ietf.org>; Tue, 20 Jun 2006 09:53:20 +0100 (BST)
Received: from conversion-daemon.d1-emea-06.sun.com by d1-emea-06.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J1500901HUMHJ00@d1-emea-06.sun.com> (original mail from Darren.Moffat@Sun.COM) for syslog@ietf.org; Tue, 20 Jun 2006 09:53:15 +0100 (BST)
Received: from [129.150.120.103] by d1-emea-06.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J15003MKI0QVP00@d1-emea-06.sun.com>; Tue, 20 Jun 2006 09:53:15 +0100 (BST)
Date: Tue, 20 Jun 2006 09:51:50 +0100
From: Darren J Moffat <Darren.Moffat@Sun.COM>
Subject: Re: [Syslog] stream transport wasdraft-ietf-syslog-transport-tls-01.txt
In-reply-to: <027c01c69410$656456a0$e8726e0a@china.huawei.com>
To: Miao Fuyou <miaofy@huawei.com>
Message-id: <4497B726.7000301@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format="flowed"; charset="ISO-8859-1"
Content-transfer-encoding: 7bit
References: <027c01c69410$656456a0$e8726e0a@china.huawei.com>
User-Agent: Mail/News 1.5.0.2 (X11/20060515)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: syslog@ietf.org
X-BeenThere: syslog@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/syslog>
List-Post: <mailto:syslog@lists.ietf.org>
List-Help: <mailto:syslog-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=subscribe>
Errors-To: syslog-bounces@lists.ietf.org

Miao Fuyou wrote:
> Yes, maybe it is favorable to have Syslog over TCP and Syslog over DTLS for
> Syslog working group. But, there will be several transport documents for the
> working group:
> 1, Syslog over UDP, already there and favorable for implementers
> 2, Syslog over TCP, what is the benefit? 
> 3, Syslog over TLS
> 4, Syslog over DTLS, I reckon implementer would like it, but does IESG
> satisfy to this transport? 
> With so many transport, implementer will be puzzled. Which is recommended by
> the working group? The current ones are option 1 and 3.

Or what about syslog using GSSAPI since that would allow Kerberos or a 
DTLS based GSSAPI mechanism.

-- 
Darren J Moffat

_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog

v2.23.0 | Report a Bug | By Email