Posted by: Anonymous Coward
on July 02, 2006 02:16 AM
A similar issue came up with VRRP (Virtual Router Redundancy Protocol, I believe). Right as the IETF was about to actually make it a formal standard, Cisco came in at the last minute and said, "oh, by the way, we claim patents on this, you have to pay us to use it." The OpenBSD team was working on their own VRRP implementation when they got a very threatening cease-and-desist letter from Cisco's chief legal counsel, Robert Barr.
The result was the Common Address Resolution Protocol, or CARP, which, I understand, is actually much better and more secure than VRRP. When the OpenBSD team tried to contact the IETF to get a protocol number assignment, the IETF ignored them, so they simply chose an unused one and went forward.
This problem is well detailed on the OpenBSD Web site, here:
I have no problem staying with the tried-and-true syslog functionality that we have today. If you need it secure, then that's what SSH tunnels are for.
Learn about Linux
Download Linux
Get Linux help
OpenBSD's CARP is a result of this lunacy
Posted by: Anonymous Coward on July 02, 2006 02:16 AMThe result was the Common Address Resolution Protocol, or CARP, which, I understand, is actually much better and more secure than VRRP. When the OpenBSD team tried to contact the IETF to get a protocol number assignment, the IETF ignored them, so they simply chose an unused one and went forward.
This problem is well detailed on the OpenBSD Web site, here:
<a href="http://www.openbsd.org/lyrics.html#35" title="openbsd.org">http://www.openbsd.org/lyrics.html#35</a openbsd.org>
I have no problem staying with the tried-and-true syslog functionality that we have today. If you need it secure, then that's what SSH tunnels are for.
#