RE: [Syslog] delineated datagrams
Miao Fuyou <miaofy@huawei.com> Mon, 24 July 2006 13:33 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G50Yz-0005E5-Je; Mon, 24 Jul 2006 09:33:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G50Yy-0005E0-2C for syslog@ietf.org; Mon, 24 Jul 2006 09:33:36 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G50Yx-0007yC-3i for syslog@ietf.org; Mon, 24 Jul 2006 09:33:36 -0400
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J2W00MQLTQQ7A@szxga01-in.huawei.com> for syslog@ietf.org; Mon, 24 Jul 2006 21:35:15 +0800 (CST)
Received: from huawei.com ([172.24.1.18]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J2W00M3DTQQYO@szxga01-in.huawei.com> for syslog@ietf.org; Mon, 24 Jul 2006 21:35:14 +0800 (CST)
Received: from m19684 ([10.111.12.140]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J2W005Q7TR8EU@szxml03-in.huawei.com> for syslog@ietf.org; Mon, 24 Jul 2006 21:35:35 +0800 (CST)
Date: Mon, 24 Jul 2006 21:32:44 +0800
From: Miao Fuyou <miaofy@huawei.com>
Subject: RE: [Syslog] delineated datagrams
In-reply-to: <577465F99B41C842AAFBE9ED71E70ABA174CC2@grfint2.intern.adiscon.com>
To: 'Rainer Gerhards' <rgerhards@hq.adiscon.com>, 'Tom Petch' <nwnetworks@dial.pipex.com>, syslog@ietf.org
Message-id: <00f801c6af25$a5423c30$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: AcaUjzSUvTEyQOf2ReyXqKuPnkIuJwYGjHEAAAFMJFAAnWQIUA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
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
Hi, Rainer, Interop is a compelling reason for protocol design, so I tend to agree with you that it is a feature nice to have. I am wondering whether we should define procedures for frame delineating processing in syslog-tls draft because we have both octect-counter and LF in a record. Miao > -----Original Message----- > From: Rainer Gerhards [mailto:rgerhards@hq.adiscon.com] > Sent: Friday, July 21, 2006 6:16 PM > To: Miao Fuyou; Tom Petch; syslog@ietf.org > Subject: RE: [Syslog] delineated > datagramswasdraft-ietf-syslog-transport-tls-01.txt > > Miao, > > I agree with your comments. However, using the LF as a record > delimited would still allow us to interop with existing > syslog/tls implementations. This is my major point. I think > it is worth it. > > Rainer > > > -----Original Message----- > > From: Miao Fuyou [mailto:miaofy@huawei.com] > > Sent: Friday, July 21, 2006 12:00 PM > > To: 'Tom Petch'; syslog@ietf.org > > Subject: RE: [Syslog] delineated > > datagramswasdraft-ietf-syslog-transport-tls-01.txt > > > > > > TLS uses SHA-1 or MD5 in ciphersuite for message integrity > > verification. If bytes lost happens during transferring, > the message > > will be dropped by TLS. > > That is also the cause that we need a security mechanism > for Syslog. > > > > As for error of encoding/decoding, I believe if an application does > > encoding/decoding in a wrong way, you must not expect it do > it right > > with other mechanism, such as LF. > > > > Redundancy to improve robustness is good idea, but I don't > think it > > applies to this case. > > > > > -----Original Message----- > > > From: Tom Petch [mailto:nwnetworks@dial.pipex.com] > > > Sent: Tuesday, June 20, 2006 8:43 PM > > > To: syslog@ietf.org > > > Subject: Re: [Syslog] delineated datagrams > > > wasdraft-ietf-syslog-transport-tls-01.txt > > > > > > I wonder if others share my concern about the lack of > robustness in > > > the way in which datagrams are delineated in the stream > protocol (a > > > TCP rather than a TLS issue). > > > > > > The system works as long as > > > - the frame length is encoded perfectly > > > - the frame length is decoded perfectly > > > - no bytes are inserted or removed in error which is > doubtless true > > > in some networks, but I would prefer not to > > rely on it. > > > > > > So, when an error occurs, can the Collector/Relay detect it? > > > Can the Collector/Relay recover synch? If not, what does the > > > Collector/Relay do? > > > > > > There is very little redundancy in the definition of > frame length, > > > and syslog messages have very little structure to help the > > > application, so I think that this is an issue we should address. > > > > > > Tom Petch > > > > > > ----- Original Message ----- > > > From: "David B Harrington" <dbharrington@comcast.net> > > > To: <syslog@ietf.org> > > > Sent: Tuesday, May 09, 2006 4:26 PM > > > Subject: [Syslog] draft-ietf-syslog-transport-tls-01.txt > > > > > > > > > Hi, > > > > > > A new revision of the syslog/TLS draft is available. > > > > > > http://www.ietf.org/internet-drafts/draft-ietf-syslog-transport-tls-01 > > > .txt > > > > > > We need reviewers. > > > Can we get > > > 1) a person to check the grammar? > > > 2) a person to check the syslog technical parts? > > > 3) a person to check compatibility with the other WG documents? > > > 4) a person to check the TLS technical parts? > > > > > > We also need general reviews of the document by multiple people. > > > > > > Thanks, > > > David Harrington > > > co-chair, Syslog WG > > > ietfdbh@comcast.net > > > > > > > > > _______________________________________________ > > > Syslog mailing list > > > Syslog@lists.ietf.org > > > https://www1.ietf.org/mailman/listinfo/syslog > > > > > > > > > _______________________________________________ > > > Syslog mailing list > > > Syslog@lists.ietf.org > > > https://www1.ietf.org/mailman/listinfo/syslog > > > > > > > > > > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > > > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
- [Syslog] draft-ietf-syslog-transport-tls-01.txt David B Harrington
- RE: [Syslog] draft-ietf-syslog-transport-tls-01.t… Rainer Gerhards
- Re: [Syslog] stream transport was draft-ietf-sysl… Tom Petch
- Re: [Syslog] ciphersuites was draft-ietf-syslog-t… Tom Petch
- RE: [Syslog] ciphersuites was draft-ietf-syslog-t… Miao Fuyou
- RE: [Syslog] stream transport wasdraft-ietf-syslo… Miao Fuyou
- Re: [Syslog] stream transport wasdraft-ietf-syslo… Darren J Moffat
- RE: [Syslog] stream transportwasdraft-ietf-syslog… Rainer Gerhards
- Re: [Syslog] delineated datagrams was draft-ietf-… Tom Petch
- [Syslog] stream transport David Harrington
- RE: [Syslog] delineated datagrams wasdraft-ietf-s… Miao Fuyou
- RE: [Syslog] delineated datagramswasdraft-ietf-sy… Rainer Gerhards
- RE: [Syslog] delineated datagrams Miao Fuyou
- RE: [Syslog] delineated datagrams Chris Lonvick
- RE: [Syslog] delineated datagrams Rainer Gerhards
- RE: [Syslog] delineated datagrams David Harrington
- RE: [Syslog] delineated datagrams Balazs Scheidler
- RE: [Syslog] delineated datagrams John Calcote
- RE: [Syslog] delineated datagrams Balazs Scheidler
- RE: [Syslog] delineated datagrams John Calcote
- RE: [Syslog] delineated datagrams Rainer Gerhards
- RE: [Syslog] delineated datagrams Balazs Scheidler
- RE: [Syslog] delineated datagrams Rainer Gerhards
- Re: [Syslog] delineated datagrams Chris Lonvick
- RE: [Syslog] delineated datagrams Rainer Gerhards
- RE: [Syslog] delineated datagrams David Harrington