On Thu, 2006-09-07 at 17:17 +0800, Miao Fuyou wrote: > Starting from TCP and then upgrading to tls is quite different to current > tls transport mapping document. If we decide to do UPGRADING, we may first > need a TCP transport mapping for Syslog, and then define a specific string > to indicate the other side to upgrade to TLS. We currently assume Syslog has > a IANA allocated port for tls transport mapping, we may not need such > complexity on upgrading. > > FYI, HTTP has two tls mechansims: RFC2818(standards track) is similiar to > this draft, RFC2817(Informational) is on upgrading.
We clearly stated in our charter that we won't define a plain TCP version (although I personally disagree). A simple capability negotiation can be useful for reasons beyond TLS upgrade, like an optional support for Application Layer acknowledgements. -- Bazsi _______________________________________________ Syslog mailing list [email protected] https://www1.ietf.org/mailman/listinfo/syslog
