Re: [Syslog] Tls-01

"Tom Petch" <nwnetworks@dial.pipex.com> Fri, 16 June 2006 09:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrAZn-0005VD-GA; Fri, 16 Jun 2006 05:25:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrAZk-0005Ul-0k for syslog@ietf.org; Fri, 16 Jun 2006 05:25:12 -0400
Received: from galaxy.systems.pipex.net ([62.241.162.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrAZi-0006cx-NY for syslog@ietf.org; Fri, 16 Jun 2006 05:25:12 -0400
Received: from pc6 (1Cust160.tnt30.lnd3.gbr.da.uu.net [62.188.122.160]) by galaxy.systems.pipex.net (Postfix) with SMTP id 9BDFEE0006D8; Fri, 16 Jun 2006 10:25:09 +0100 (BST)
Message-ID: <002e01c6911d$d9a6bc60$0601a8c0@pc6>
From: Tom Petch <nwnetworks@dial.pipex.com>
To: David B Harrington <dbharrington@comcast.net>, syslog@ietf.org
References: <072001c679f6$3a0ffd80$0400a8c0@china.huawei.com>
Subject: Re: [Syslog] Tls-01
Date: Fri, 16 Jun 2006 10:16:41 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc:
X-BeenThere: syslog@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
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

We have chosen and used a consistent terminology up until the tls document, so I
think that tls should come in line.  I think I see its problem, of not wanting
to use the phrase 'sender or relay' repeatedly, but in that case, it should
generate a new term, not redefine a well-established one.  For myself, I am
comfortable with reusing 'sender or relay' in each case.

Tom Petch


----- Original Message -----
From: "David B Harrington" <dbharrington@comcast.net>
To: <syslog@ietf.org>
Sent: Wednesday, May 17, 2006 11:09 PM
Subject: [Syslog] Tls-01


Hi,

The definition of sender in syslog-tls-01 differs from that in
syslog-protocol.
In -protocol, the "sender" is the message generator.
In -tls, the sender is the message sender, whether that entity
generated the message or not, and "originator" is the generator of the
message.
The distinction is important for discussing transport isues common to
both senders and relays.

Can the WG please take a look at the differences in terminology, so we
can settle on terms that can be used consistently in all our
documents?

Thanks,
David Harrington
dharrington@huawei.com
dbharrington@comcast.net
ietfdbh@comcast.net
co-chair, Syslog WG


_______________________________________________
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