[Syslog] Review of draft-petch-gerhards-syslog-transport-dtls-01.txt"

[fenghongyan <[e-mail]>]

Hi,

I read this proposal "draft-petch-gerhards-syslog-transport-dtls-01", 
I have some comments on it:

Those changes I made in my new version this draft is also need to make, I think. 


section 1.3
   The security discussion is similar as stated in syslog/tls,  Pasi
   recommended simply pointer to syslog/tls would be better.   

section 1.4
   This is covered in syslog/tls; a pointer to that document would work.

section 2.1
  I don't see if there's a necessary for a syslog server should be a DTLS client. 
  In my understanding, a dtls request is alway initiate by a dtls client, if syslog server being dtls client,
  how does a server know which client want to connect to it?
  I think RFC5425 has state authentication in very detail and come up the corresponding security policy.
  Also, fingerprint is aim to cover the case you discussed in your draft having a certificate url authentication. 
  A pointer to that document would work.

section 2.2
  I think a  udp "registered port number" is required to assign for udp mapping and 
 a sctp "registered port number" is required to assign for sctp mapping respectively.

section 2.3
 I claimed in my proposal to minimize the operation and security where 
 both syslog/tls and syslog/dtls are supported, why do you need write 
 the commands in your proposal?

section 2.6, section 2.8
  It is covered in syslog/tls security policy; a pointer to that document would work.







Thanks
Linda