Hi Darren,
There is no need for Bazsi to write a different i-d.
draft-ietf-syslog-transport-tls is a Working Group document and the
final revision must reflect WG consensus.
If Bazsi (or anybody else) can propose changes to
draft-ietf-syslog-transport-tls and the WG reaches consensus on the
proposed changes, then the document will be revised to reflect that.
Please check me if I'm wrong on this, but I think that the only changes
between syslog-ng and what's in syslog-transport-tls are
- framing,
- changes to address the threat model (listed in our Charter).
Thanks,
Chris
On Tue, 4 Jul 2006, Darren Reed wrote:
Chris,
The approach I'd like to take is to see what Balazs Scheidler can
come up with, that is different to the proposed approach, to make
syslog function over a TLS transport in syslog-ng and look at turning
that into an i-d.
While it may not guarantee us any better situation with respect to
patents, etc, I have more faith working on documenting something
that is written to be open and free than involving people who have
a financial interest in the protocol going in certain diretions.
I suppose this is a get working code first and then refine/
document it.
Thoughts?
Darren
_______________________________________________
Syslog mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/syslog
