RE: [Syslog] Notes on TLS transport

Miao Fuyou <miaofy@huawei.com> Tue, 08 August 2006 01:26 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GAGMI-0006yB-FC; Mon, 07 Aug 2006 21:26:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GAGMH-0006y6-1q for syslog@ietf.org; Mon, 07 Aug 2006 21:26:13 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAGMF-0005I0-A9 for syslog@ietf.org; Mon, 07 Aug 2006 21:26:13 -0400
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J3N000N9O3XHQ@szxga03-in.huawei.com> for syslog@ietf.org; Tue, 08 Aug 2006 09:28:46 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J3N00FKEO3XEF@szxga03-in.huawei.com> for syslog@ietf.org; Tue, 08 Aug 2006 09:28:45 +0800 (CST)
Received: from m19684 ([10.111.12.140]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J3N00263O6M2T@szxml04-in.huawei.com> for syslog@ietf.org; Tue, 08 Aug 2006 09:30:26 +0800 (CST)
Date: Tue, 08 Aug 2006 09:18:32 +0800
From: Miao Fuyou <miaofy@huawei.com>
Subject: RE: [Syslog] Notes on TLS transport
In-reply-to: <20060807034541.13121222425@laser.networkresonance.com>
To: syslog@ietf.org
Message-id: <00f901c6ba88$911440a0$8c0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: Aca50utioaRZSX13SC6e3n4933UtuwAs/0sg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc:
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

 
> 
> S 5.3:
>    All Syslog messages MUST be sent as TLS "application data".  There
>    MAY be multiple Syslog message in the same TLS record.  The
>    application data is defined with the following ABNF [3] expression:
> 
> TLS's abstraction is as a stream, so this isn't really the business
> of htis spec.
> 

I agree to Eric's opinion. If syslog procotol has a mechanism to delimit
message, we will never need to address same issue across different
documents: syslog-tls, syslog-ssh, or syslog-tcp etc (perhaps with different
mechanisms). 




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