I'll get back to you on the generic certificates issue. For now, I
recommend you read RFC 4107. Also note that each device needs a
unique MAC address so the manufacturing process tends to have a step
for making a device unique.
So, it sounds like all forms of authentication are optional in
I failed to write this up yesterday.
Your protocol document uses ISO language identifiers rather than BCP
47. Please either use BCP 47 or explain for all the language sets
that BCP 47 can identify but your choice cannot why syslog
implementations will not care.
Sam,
I need to check the mailing list archives and my notes, but I think
there was no technical reason to use ISO instead of BCP 47. If I do not
find anything, I'll simply change the reference. In any case, I'll post
what I find out.
Rainer
-Original Message-
From: Sam Hartman
inline
Tom Petch
- Original Message -
From: Miao Fuyou [EMAIL PROTECTED]
To: 'Sam Hartman' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, January 31, 2007 5:50 AM
Subject: RE: [Syslog] AD Review for draft-ietf-syslog-transport-tls
Hi Sam,
Thanks for the review! My response is
- 'The syslog Protocol '
draft-ietf-syslog-protocol-19.txt as a Proposed Standard
draft-ietf-syslog-protocol-19.txt recommends using a reliable
protocol. Existing implementations of syslog do this and
deadlock with nameservers which are logging via syslog.
