RE: [Syslog] RE: byte-counting vs special character

Chris Lonvick <clonvick@cisco.com> Thu, 17 August 2006 14:38 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDj0U-00080Q-9z; Thu, 17 Aug 2006 10:38:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDj0T-00080B-5O for syslog@ietf.org; Thu, 17 Aug 2006 10:38:01 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDj0T-0006uH-3f for syslog@ietf.org; Thu, 17 Aug 2006 10:38:01 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GDilZ-0007Hu-Dg for syslog@ietf.org; Thu, 17 Aug 2006 10:22:40 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-5.cisco.com with ESMTP; 17 Aug 2006 07:22:36 -0700
X-IronPort-AV: i="4.08,137,1154934000"; d="scan'208"; a="312069298:sNHT32560368"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-6.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k7HEMaX7009821; Thu, 17 Aug 2006 07:22:36 -0700
Received: from sjc-cde-003.cisco.com (sjc-cde-003.cisco.com [171.71.162.27]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k7HEMZ6X021067; Thu, 17 Aug 2006 07:22:35 -0700 (PDT)
Date: Thu, 17 Aug 2006 07:22:35 -0700
From: Chris Lonvick <clonvick@cisco.com>
To: David Harrington <ietfdbh@comcast.net>
Subject: RE: [Syslog] RE: byte-counting vs special character
In-Reply-To: <0bfb01c6c199$01c71860$0400a8c0@china.huawei.com>
Message-ID: <Pine.GSO.4.63.0608170721250.8687@sjc-cde-003.cisco.com>
References: <0bfb01c6c199$01c71860$0400a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
DKIM-Signature: a=rsa-sha1; q=dns; l=2431; t=1155824556; x=1156688556; c=relaxed/simple; s=sjdkim6002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=clonvick@cisco.com; z=From:Chris=20Lonvick=20<clonvick@cisco.com> |Subject:RE=3A=20[Syslog]=20RE=3A=20byte-counting=20vs=20special=20character; X=v=3Dcisco.com=3B=20h=3DRBXSe64fi0EdrHj8Tz0GuQtbh4g=3D; b=KGxRcUxzw4d6NrODmqacyZc/JMBQRZKBhb8kkzRFCTxRVc7r/Awny2LeBaWSagAZkq55en47 QF4Svr0q0RlUhB9HpkOxmG5490Hz/NFuqNl2TxLXvFxzezfvepTC1/WS;
Authentication-Results: sj-dkim-6.cisco.com; header.From=clonvick@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: -2.6 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
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

Hi,

I agree; we don't want a vote here.  We want strong technical reasons for 
making a decision.

Thanks,
Chris

On Wed, 16 Aug 2006, David Harrington wrote:

> Hi Rainer,
>
> The IETF doesn't vote.
> The chairs will determine consensus on or after the Aug 18 deadline
> for this decision.
>
> David Harrington
> dharrington@huawei.com
> dbharrington@comcast.net
> ietfdbh@comcast.net
> co-chair, Syslog WG
>
>
>> -----Original Message-----
>> From: Rainer Gerhards [mailto:rgerhards@hq.adiscon.com]
>> Sent: Wednesday, August 16, 2006 8:08 PM
>> To: Carson Gaspar
>> Cc: syslog@ietf.org
>> Subject: RE: [Syslog] RE: byte-counting vs special character
>>
>> Carson,
>>
>> Legacy code does not contain LF in messages. It is advised that
>> new-style syslog also does not contain control characters
>> (though it now
>> is allowed).
>>
>> Thus the argument is valid. Again, I do not object octet-couting (I
>> actually introduced the idea ;)) but find it the second
> best-solution.
>> Maybe we should do a simple poll - some have already voiced their
>> choices...
>>
>> Rainer
>>
>>> -----Original Message-----
>>> From: Carson Gaspar [mailto:carson@taltos.org]
>>> Sent: Wednesday, August 16, 2006 1:33 PM
>>> To: syslog@ietf.org
>>> Subject: Re: [Syslog] RE: byte-counting vs special character
>>>
>>> Escaping precludes no-configuration backwards compatibility,
>>> as no legacy
>>> syslog-over-tcp code does escaping. So if you want to
>>> interoperate with
>>> existing code, you must have a "don't escape or expect
>>> escapes" switch in
>>> your code. If you're going to do that, just have a "LF mode
>>> vs byte-count
>>> mode" switch. This whole backwards compat argument is bogus,
>>> iff we decide
>>> to escape embedded LF instead of forbidding it. And I have
>> yet to see
>>> anyone argue for LF on any grounds except backwards compatibility.
>>>
>>> --
>>> Carson
>>>
>>> _______________________________________________
>>> 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