<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-syslog-rfc3195bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-syslog-rfc3195bis-00">
   <front>
      <title>Reliable Delivery for syslog</title>
      <author initials="D." surname="New" fullname="Darren New">
         </author>
      <author initials="M. T." surname="Rose" fullname="Dr. Marshall T. Rose">
         </author>
      <author initials="E." surname="Lear" fullname="Eliot Lear">
         <organization>Cisco Systems</organization>
      </author>
      <date month="November" day="8" year="2007" />
      <abstract>
	 <t>The syslog protocol describes a number of service options related to
propagating event messages.  This memo describes a mapping of the
syslog protocol to TCP connections, useful for reliable delivery of
event messages through the use of a BEEP profile.  The earlier RAW
and COOKED BEEP syslog profiles are deprecated.  The use of syslog
over BEEP provides robustness and security in message delivery that
is unavailable to the usual UDP-based syslog protocol, by providing
encryption and authentication over a connection-oriented protocol.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-syslog-rfc3195bis-00" />
   
</reference>
