From whiz100 at hotmail.com  Fri Oct 21 22:38:46 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Fri, 21 Oct 2005 16:38:46 -0400
Subject: [rfc3195] FW: Sasl
In-Reply-To: <BAY102-DAV5E0541F64DF8FB45ADDA0F2720@phx.gbl>
Message-ID: <BAY102-DAV994A2251EDD90F0B1E4F8F2720@phx.gbl>


I've got sasl working now.

I've attached my debug log so you can see what's going on.

I've not completed it yet, but it works as long as everything happens in an
expected order, and the authentication is a success. If not then it will
probably crash.
So I'm going to clean up the problems over the next week so it behaves
correctly including the error handling.

One of the problems I've found now is the server piece really needs a
configuration file which deviates from the problem I'm trying to solve.

I'm using the cyrus sasl library which was very easy to use. But getting it
installed and running was a pain. The documentation on cyrus is lacking in
some parts.
Also if you notice in my greeting from the server there are repeating
profile announcements. This is coming from cyrus. It's not caused a problem
but I wonder if other implementation would have an issue with it.


Peter



From whiz100 at hotmail.com  Fri Oct 21 23:06:56 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Fri, 21 Oct 2005 17:06:56 -0400
Subject: [rfc3195] FW: Sasl
In-Reply-To: <BAY102-DAV994A2251EDD90F0B1E4F8F2720@phx.gbl>
Message-ID: <BAY102-DAV69192F8250C5DD8AE8BE3F2720@phx.gbl>



Here's the debug log from the last post. The listserv stripped of the
attachment.

Peter

-------- start from here -----
I:RPY 0 0 . 0 50
Content-Type: application/beep+xml
 
<greeting/>
END
L:RPY 0 0 . 0 963
Content-Type: application/beep+xml
 
<greeting>
  <profile uri="http://xml.resource.org/profiles/syslog/RAW"/>
  <profile uri="http://iana.org/beep/TLS"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
</greeting>
END
I:MSG 0 1 . 50 155
Content-Type: application/beep+xml
 
<start number="1" serverName='testing'><profile
uri="http://iana.org/beep/TLS"><![CDATA[<ready/>]]></profile></start>END
L:RPY 0 1 . 963 82
Content-Type: application/beep+xml
 
<profile uri="http://iana.org/beep/TLS" />
END
*:About to start TLS
*:Now using TLS cipher=DES-CBC3-SHA
I:RPY 0 2 . 205 50
Content-Type: application/beep+xml
 
<greeting/>
END
L:RPY 0 2 . 1045 919
Content-Type: application/beep+xml
 
<greeting>
  <profile uri="http://xml.resource.org/profiles/syslog/RAW"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
</greeting>
END
I:MSG 0 3 . 255 169
Content-Type: application/beep+xml
 
<start number="3" ><profile
uri="http://iana.org/beep/SASL/OTP"><![CDATA[<blob>dGVzdHVzZXIAdGVzdHVzZXI=<
/blob>]]></profile></start>END
L:RPY 0 3 . 1964 152
Content-Type: application/beep+xml
 
<profile 
uri="http://iana.org/beep/SASL/OTP"><![CDATA[<blob>b3RwLW1kNSA0OTggcGEwMjY2I
GV4dA==</blob>]]></profile>
END
I:MSG 3 0 . 0 79
Content-Type: application/xml+beep
 
<blob>aGV4OjVjMDE5OTAzZWFkZDk0MWY=</blob>END
L:MSG 3 0 . 0 63
Content-Type: application/beep+xml
 
<blob status='complete'/>END
I:MSG 0 4 . 424 125
Content-Type: application/beep+xml
 
<start number="5" ><profile
uri="http://xml.resource.org/profiles/syslog/RAW"/></start>END
L:RPY 0 4 . 2116 101
Content-Type: application/beep+xml
 
<profile uri="http://xml.resource.org/profiles/syslog/RAW" />
END
L:MSG 5 0 . 0 19
 
Hello from syslogEND
I:ANS 5 0 . 0 6 0
 
plopEND
I:ANS 5 0 . 6 56 1
 
<4>Oct 12 09:14:00 plop pp[23]: this is a test messageEND
I:NUL 5 0 . 62 0
END
I:MSG 0 5 . 549 69
Content-Type: application/beep+xml
 
<close number="5" code="200" />END
L:RPY 0 5 . 2217 43
Content-Type: application/beep+xml
 
<ok/>END
I:MSG 0 6 . 618 69
Content-Type: application/beep+xml
 
<close number="0" code="200" />END
L:RPY 0 6 . 2260 43
Content-Type: application/beep+xml
 
<ok/>END
 



From rgerhards at hq.adiscon.com  Wed Oct 26 11:35:28 2005
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Wed, 26 Oct 2005 11:35:28 +0200
Subject: [rfc3195] RFC 3195 implementations
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E3CCB@grfint2.intern.adiscon.com>

Hello List,

I appreciate the many subscription requests  this new list got. With
this mail, I would like to both inform about the RFC 3195
implementations I know of as well as poll who else is doing some work.

I track implementations at

http://www.syslog.cc/ietf/rfcs/3195.html

This page includes everything I came across, but I guess it is
incomplete. If someone knows of any other implementations, I would
appreciate to know about that.

Other then already-available softwares, I would also like to know about
who is working towards an implementation. I know that for many
commercial projects such an announcement is probably impossible. But if
someone can talk about an effort, that would be very useful to know.

The main reasoning for my question is that I would like to see if
interest in RFC 3195 is actually growing. This is probably also very
useful information for further IETF standardization efforts.

Any response is deeply appreciated.

Rainer Gerhards


From whiz100 at hotmail.com  Thu Oct 27 20:34:38 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Thu, 27 Oct 2005 14:34:38 -0400
Subject: [rfc3195] Framing problems
Message-ID: <BAY102-DAV139A6BA5BD3637B3B71FD2F2680@phx.gbl>



Can someone tell me which of the below is correct. I'm questioning the msgno
on RPY and ERR. I believe example 1 is correct as is msgno RPY matches the
MSG msgno good message and the msgno ERR matches the MSG msgno from the bad
message.

BEEP FRAMING =
 HEADER SP common

Common = channel SP msgno SP more SP seqno SP size
HEADER = msg / rpy / ans /err etc...



------ example 1 -----


I:MSG 0 4 . 434 210
Content-Type: application/beep+xml
 
<start number="5" ><profile
uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<iam
fqdn='paul.debug.local' ip='127.0.0.1' type='device' />
]]></profile></start>END
L:RPY 0 4 . 875 130
Content-Type: application/beep+xml
 
<profile uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<ok
/>]]></profile>
END
I:MSG 5 0 . 0 44
Content-Type: application/beep+xml
 
plop23END
I:MSG 5 1 . 44 169
Content-Type: application/beep+xml
 
<entry facility='8' severity='6' hostname='paul.debug.local' timestamp='Oct
27 08:27:00'><![CDATA[<a>some large data</a>]]></entry>END
L:ERR 5 0 . 0 115
Content-Type: application/beep+xml
 
<error code='500'><![CDATA[Unreconized Tag expecting entry or
path]]></error>END
L:RPY 5 1 . 115 43
Content-Type: application/beep+xml
 
<ok/>END




------ example 2 ------


I:MSG 0 1 . 50 214
Content-Type: application/beep+xml
 
<start number="1" ><profile
uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<iam
fqdn='paul.debug.local' ip='192.168.0.103' type='device' />
]]></profile></start>END
L:RPY 0 1 . 198 104
Content-Type: application/beep+xml
 
<profile uri='http://xml.resource.org/profiles/syslog/COOKED' />
END
I:MSG 1 0 . 0 42
Content-Type: application/beep+xml
 
plopEND
I:MSG 1 1 . 42 169
Content-Type: application/beep+xml
 
<entry facility='8' severity='6' hostname='paul.debug.local' timestamp='Oct
27 08:27:00'><![CDATA[<a>some large data</a>]]></entry>END
L:ERR 1 0 . 0 93
Content-Type: application/beep+xml
 
<error code='500'><![CDATA[Unreconized Tag]]></error>
END
L:RPY 1 0 . 93 43
Content-Type: application/beep+xml
 
<ok/>END



From whiz100 at hotmail.com  Fri Oct 21 22:38:46 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Fri, 21 Oct 2005 16:38:46 -0400
Subject: [rfc3195] FW: Sasl
In-Reply-To: <BAY102-DAV5E0541F64DF8FB45ADDA0F2720@phx.gbl>
Message-ID: <BAY102-DAV994A2251EDD90F0B1E4F8F2720@phx.gbl>


I've got sasl working now.

I've attached my debug log so you can see what's going on.

I've not completed it yet, but it works as long as everything happens in an
expected order, and the authentication is a success. If not then it will
probably crash.
So I'm going to clean up the problems over the next week so it behaves
correctly including the error handling.

One of the problems I've found now is the server piece really needs a
configuration file which deviates from the problem I'm trying to solve.

I'm using the cyrus sasl library which was very easy to use. But getting it
installed and running was a pain. The documentation on cyrus is lacking in
some parts.
Also if you notice in my greeting from the server there are repeating
profile announcements. This is coming from cyrus. It's not caused a problem
but I wonder if other implementation would have an issue with it.


Peter



From whiz100 at hotmail.com  Fri Oct 21 23:06:56 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Fri, 21 Oct 2005 17:06:56 -0400
Subject: [rfc3195] FW: Sasl
In-Reply-To: <BAY102-DAV994A2251EDD90F0B1E4F8F2720@phx.gbl>
Message-ID: <BAY102-DAV69192F8250C5DD8AE8BE3F2720@phx.gbl>



Here's the debug log from the last post. The listserv stripped of the
attachment.

Peter

-------- start from here -----
I:RPY 0 0 . 0 50
Content-Type: application/beep+xml
 
<greeting/>
END
L:RPY 0 0 . 0 963
Content-Type: application/beep+xml
 
<greeting>
  <profile uri="http://xml.resource.org/profiles/syslog/RAW"/>
  <profile uri="http://iana.org/beep/TLS"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
</greeting>
END
I:MSG 0 1 . 50 155
Content-Type: application/beep+xml
 
<start number="1" serverName='testing'><profile
uri="http://iana.org/beep/TLS"><![CDATA[<ready/>]]></profile></start>END
L:RPY 0 1 . 963 82
Content-Type: application/beep+xml
 
<profile uri="http://iana.org/beep/TLS" />
END
*:About to start TLS
*:Now using TLS cipher=DES-CBC3-SHA
I:RPY 0 2 . 205 50
Content-Type: application/beep+xml
 
<greeting/>
END
L:RPY 0 2 . 1045 919
Content-Type: application/beep+xml
 
<greeting>
  <profile uri="http://xml.resource.org/profiles/syslog/RAW"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
</greeting>
END
I:MSG 0 3 . 255 169
Content-Type: application/beep+xml
 
<start number="3" ><profile
uri="http://iana.org/beep/SASL/OTP"><![CDATA[<blob>dGVzdHVzZXIAdGVzdHVzZXI=<
/blob>]]></profile></start>END
L:RPY 0 3 . 1964 152
Content-Type: application/beep+xml
 
<profile 
uri="http://iana.org/beep/SASL/OTP"><![CDATA[<blob>b3RwLW1kNSA0OTggcGEwMjY2I
GV4dA==</blob>]]></profile>
END
I:MSG 3 0 . 0 79
Content-Type: application/xml+beep
 
<blob>aGV4OjVjMDE5OTAzZWFkZDk0MWY=</blob>END
L:MSG 3 0 . 0 63
Content-Type: application/beep+xml
 
<blob status='complete'/>END
I:MSG 0 4 . 424 125
Content-Type: application/beep+xml
 
<start number="5" ><profile
uri="http://xml.resource.org/profiles/syslog/RAW"/></start>END
L:RPY 0 4 . 2116 101
Content-Type: application/beep+xml
 
<profile uri="http://xml.resource.org/profiles/syslog/RAW" />
END
L:MSG 5 0 . 0 19
 
Hello from syslogEND
I:ANS 5 0 . 0 6 0
 
plopEND
I:ANS 5 0 . 6 56 1
 
<4>Oct 12 09:14:00 plop pp[23]: this is a test messageEND
I:NUL 5 0 . 62 0
END
I:MSG 0 5 . 549 69
Content-Type: application/beep+xml
 
<close number="5" code="200" />END
L:RPY 0 5 . 2217 43
Content-Type: application/beep+xml
 
<ok/>END
I:MSG 0 6 . 618 69
Content-Type: application/beep+xml
 
<close number="0" code="200" />END
L:RPY 0 6 . 2260 43
Content-Type: application/beep+xml
 
<ok/>END
 



From rgerhards at hq.adiscon.com  Wed Oct 26 11:35:28 2005
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Wed, 26 Oct 2005 11:35:28 +0200
Subject: [rfc3195] RFC 3195 implementations
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E3CCB@grfint2.intern.adiscon.com>

Hello List,

I appreciate the many subscription requests  this new list got. With
this mail, I would like to both inform about the RFC 3195
implementations I know of as well as poll who else is doing some work.

I track implementations at

http://www.syslog.cc/ietf/rfcs/3195.html

This page includes everything I came across, but I guess it is
incomplete. If someone knows of any other implementations, I would
appreciate to know about that.

Other then already-available softwares, I would also like to know about
who is working towards an implementation. I know that for many
commercial projects such an announcement is probably impossible. But if
someone can talk about an effort, that would be very useful to know.

The main reasoning for my question is that I would like to see if
interest in RFC 3195 is actually growing. This is probably also very
useful information for further IETF standardization efforts.

Any response is deeply appreciated.

Rainer Gerhards


From whiz100 at hotmail.com  Thu Oct 27 20:34:38 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Thu, 27 Oct 2005 14:34:38 -0400
Subject: [rfc3195] Framing problems
Message-ID: <BAY102-DAV139A6BA5BD3637B3B71FD2F2680@phx.gbl>



Can someone tell me which of the below is correct. I'm questioning the msgno
on RPY and ERR. I believe example 1 is correct as is msgno RPY matches the
MSG msgno good message and the msgno ERR matches the MSG msgno from the bad
message.

BEEP FRAMING =
 HEADER SP common

Common = channel SP msgno SP more SP seqno SP size
HEADER = msg / rpy / ans /err etc...



------ example 1 -----


I:MSG 0 4 . 434 210
Content-Type: application/beep+xml
 
<start number="5" ><profile
uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<iam
fqdn='paul.debug.local' ip='127.0.0.1' type='device' />
]]></profile></start>END
L:RPY 0 4 . 875 130
Content-Type: application/beep+xml
 
<profile uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<ok
/>]]></profile>
END
I:MSG 5 0 . 0 44
Content-Type: application/beep+xml
 
plop23END
I:MSG 5 1 . 44 169
Content-Type: application/beep+xml
 
<entry facility='8' severity='6' hostname='paul.debug.local' timestamp='Oct
27 08:27:00'><![CDATA[<a>some large data</a>]]></entry>END
L:ERR 5 0 . 0 115
Content-Type: application/beep+xml
 
<error code='500'><![CDATA[Unreconized Tag expecting entry or
path]]></error>END
L:RPY 5 1 . 115 43
Content-Type: application/beep+xml
 
<ok/>END




------ example 2 ------


I:MSG 0 1 . 50 214
Content-Type: application/beep+xml
 
<start number="1" ><profile
uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<iam
fqdn='paul.debug.local' ip='192.168.0.103' type='device' />
]]></profile></start>END
L:RPY 0 1 . 198 104
Content-Type: application/beep+xml
 
<profile uri='http://xml.resource.org/profiles/syslog/COOKED' />
END
I:MSG 1 0 . 0 42
Content-Type: application/beep+xml
 
plopEND
I:MSG 1 1 . 42 169
Content-Type: application/beep+xml
 
<entry facility='8' severity='6' hostname='paul.debug.local' timestamp='Oct
27 08:27:00'><![CDATA[<a>some large data</a>]]></entry>END
L:ERR 1 0 . 0 93
Content-Type: application/beep+xml
 
<error code='500'><![CDATA[Unreconized Tag]]></error>
END
L:RPY 1 0 . 93 43
Content-Type: application/beep+xml
 
<ok/>END



From whiz100 at hotmail.com  Fri Oct 21 22:38:46 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Fri, 21 Oct 2005 16:38:46 -0400
Subject: [rfc3195] FW: Sasl
In-Reply-To: <BAY102-DAV5E0541F64DF8FB45ADDA0F2720@phx.gbl>
Message-ID: <BAY102-DAV994A2251EDD90F0B1E4F8F2720@phx.gbl>


I've got sasl working now.

I've attached my debug log so you can see what's going on.

I've not completed it yet, but it works as long as everything happens in an
expected order, and the authentication is a success. If not then it will
probably crash.
So I'm going to clean up the problems over the next week so it behaves
correctly including the error handling.

One of the problems I've found now is the server piece really needs a
configuration file which deviates from the problem I'm trying to solve.

I'm using the cyrus sasl library which was very easy to use. But getting it
installed and running was a pain. The documentation on cyrus is lacking in
some parts.
Also if you notice in my greeting from the server there are repeating
profile announcements. This is coming from cyrus. It's not caused a problem
but I wonder if other implementation would have an issue with it.


Peter



From whiz100 at hotmail.com  Fri Oct 21 23:06:56 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Fri, 21 Oct 2005 17:06:56 -0400
Subject: [rfc3195] FW: Sasl
In-Reply-To: <BAY102-DAV994A2251EDD90F0B1E4F8F2720@phx.gbl>
Message-ID: <BAY102-DAV69192F8250C5DD8AE8BE3F2720@phx.gbl>



Here's the debug log from the last post. The listserv stripped of the
attachment.

Peter

-------- start from here -----
I:RPY 0 0 . 0 50
Content-Type: application/beep+xml
 
<greeting/>
END
L:RPY 0 0 . 0 963
Content-Type: application/beep+xml
 
<greeting>
  <profile uri="http://xml.resource.org/profiles/syslog/RAW"/>
  <profile uri="http://iana.org/beep/TLS"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
</greeting>
END
I:MSG 0 1 . 50 155
Content-Type: application/beep+xml
 
<start number="1" serverName='testing'><profile
uri="http://iana.org/beep/TLS"><![CDATA[<ready/>]]></profile></start>END
L:RPY 0 1 . 963 82
Content-Type: application/beep+xml
 
<profile uri="http://iana.org/beep/TLS" />
END
*:About to start TLS
*:Now using TLS cipher=DES-CBC3-SHA
I:RPY 0 2 . 205 50
Content-Type: application/beep+xml
 
<greeting/>
END
L:RPY 0 2 . 1045 919
Content-Type: application/beep+xml
 
<greeting>
  <profile uri="http://xml.resource.org/profiles/syslog/RAW"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/PLAIN"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/OTP"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/DIGEST-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/CRAM-MD5"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
  <profile uri="http://iana.org/beep/SASL/ANONYMOUS"/>
</greeting>
END
I:MSG 0 3 . 255 169
Content-Type: application/beep+xml
 
<start number="3" ><profile
uri="http://iana.org/beep/SASL/OTP"><![CDATA[<blob>dGVzdHVzZXIAdGVzdHVzZXI=<
/blob>]]></profile></start>END
L:RPY 0 3 . 1964 152
Content-Type: application/beep+xml
 
<profile 
uri="http://iana.org/beep/SASL/OTP"><![CDATA[<blob>b3RwLW1kNSA0OTggcGEwMjY2I
GV4dA==</blob>]]></profile>
END
I:MSG 3 0 . 0 79
Content-Type: application/xml+beep
 
<blob>aGV4OjVjMDE5OTAzZWFkZDk0MWY=</blob>END
L:MSG 3 0 . 0 63
Content-Type: application/beep+xml
 
<blob status='complete'/>END
I:MSG 0 4 . 424 125
Content-Type: application/beep+xml
 
<start number="5" ><profile
uri="http://xml.resource.org/profiles/syslog/RAW"/></start>END
L:RPY 0 4 . 2116 101
Content-Type: application/beep+xml
 
<profile uri="http://xml.resource.org/profiles/syslog/RAW" />
END
L:MSG 5 0 . 0 19
 
Hello from syslogEND
I:ANS 5 0 . 0 6 0
 
plopEND
I:ANS 5 0 . 6 56 1
 
<4>Oct 12 09:14:00 plop pp[23]: this is a test messageEND
I:NUL 5 0 . 62 0
END
I:MSG 0 5 . 549 69
Content-Type: application/beep+xml
 
<close number="5" code="200" />END
L:RPY 0 5 . 2217 43
Content-Type: application/beep+xml
 
<ok/>END
I:MSG 0 6 . 618 69
Content-Type: application/beep+xml
 
<close number="0" code="200" />END
L:RPY 0 6 . 2260 43
Content-Type: application/beep+xml
 
<ok/>END
 



From rgerhards at hq.adiscon.com  Wed Oct 26 11:35:28 2005
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Wed, 26 Oct 2005 11:35:28 +0200
Subject: [rfc3195] RFC 3195 implementations
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E3CCB@grfint2.intern.adiscon.com>

Hello List,

I appreciate the many subscription requests  this new list got. With
this mail, I would like to both inform about the RFC 3195
implementations I know of as well as poll who else is doing some work.

I track implementations at

http://www.syslog.cc/ietf/rfcs/3195.html

This page includes everything I came across, but I guess it is
incomplete. If someone knows of any other implementations, I would
appreciate to know about that.

Other then already-available softwares, I would also like to know about
who is working towards an implementation. I know that for many
commercial projects such an announcement is probably impossible. But if
someone can talk about an effort, that would be very useful to know.

The main reasoning for my question is that I would like to see if
interest in RFC 3195 is actually growing. This is probably also very
useful information for further IETF standardization efforts.

Any response is deeply appreciated.

Rainer Gerhards


From whiz100 at hotmail.com  Thu Oct 27 20:34:38 2005
From: whiz100 at hotmail.com (Peter Hall)
Date: Thu, 27 Oct 2005 14:34:38 -0400
Subject: [rfc3195] Framing problems
Message-ID: <BAY102-DAV139A6BA5BD3637B3B71FD2F2680@phx.gbl>



Can someone tell me which of the below is correct. I'm questioning the msgno
on RPY and ERR. I believe example 1 is correct as is msgno RPY matches the
MSG msgno good message and the msgno ERR matches the MSG msgno from the bad
message.

BEEP FRAMING =
 HEADER SP common

Common = channel SP msgno SP more SP seqno SP size
HEADER = msg / rpy / ans /err etc...



------ example 1 -----


I:MSG 0 4 . 434 210
Content-Type: application/beep+xml
 
<start number="5" ><profile
uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<iam
fqdn='paul.debug.local' ip='127.0.0.1' type='device' />
]]></profile></start>END
L:RPY 0 4 . 875 130
Content-Type: application/beep+xml
 
<profile uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<ok
/>]]></profile>
END
I:MSG 5 0 . 0 44
Content-Type: application/beep+xml
 
plop23END
I:MSG 5 1 . 44 169
Content-Type: application/beep+xml
 
<entry facility='8' severity='6' hostname='paul.debug.local' timestamp='Oct
27 08:27:00'><![CDATA[<a>some large data</a>]]></entry>END
L:ERR 5 0 . 0 115
Content-Type: application/beep+xml
 
<error code='500'><![CDATA[Unreconized Tag expecting entry or
path]]></error>END
L:RPY 5 1 . 115 43
Content-Type: application/beep+xml
 
<ok/>END




------ example 2 ------


I:MSG 0 1 . 50 214
Content-Type: application/beep+xml
 
<start number="1" ><profile
uri="http://xml.resource.org/profiles/syslog/COOKED"><![CDATA[<iam
fqdn='paul.debug.local' ip='192.168.0.103' type='device' />
]]></profile></start>END
L:RPY 0 1 . 198 104
Content-Type: application/beep+xml
 
<profile uri='http://xml.resource.org/profiles/syslog/COOKED' />
END
I:MSG 1 0 . 0 42
Content-Type: application/beep+xml
 
plopEND
I:MSG 1 1 . 42 169
Content-Type: application/beep+xml
 
<entry facility='8' severity='6' hostname='paul.debug.local' timestamp='Oct
27 08:27:00'><![CDATA[<a>some large data</a>]]></entry>END
L:ERR 1 0 . 0 93
Content-Type: application/beep+xml
 
<error code='500'><![CDATA[Unreconized Tag]]></error>
END
L:RPY 1 0 . 93 43
Content-Type: application/beep+xml
 
<ok/>END