Re: [Syslog] Please review draft-ietf-syslog-transport-tls

[robert.horn at agfa.com]

The syslog-transport-tls-13 looks OK.  I have the following 
comments/questions but they might not need any document changes.

1) In 4.2, is this the proper words for dealing with ongoing changes to 
other standards and RFCs? Someday the SHA1 use will be deprecated.  The 
people who do that probably are not syslog people and won't update this 
document.

2) In 5.2, name matching becomes much more complex when non-latin 
alphabets are included.  Even the meaning of case-insensitive can become 
unclear.  We deal with this routinely when doing person name matching and 
point to the Unicode TR-15 character matching rules and specify that the 
NFC rule set defines "equality".  This is also the W3C recommendation.  We 
then note that culture specific matching rules may be needed, e.g., the 
alternative encodings of "Strasser" in German, are not "equal" by the NFC 
rules.  Will this automatically flow through from the non-latin extensions 
for DNS and thus dnsName, or is something needed here?

I expect that there will still be implementer questions about some of the 
fingerprint and other rules, but these requirements are clear about the 
wire protocol.  It's not specific and should not be regarding user 
interface and configuration files.  So I agree with what is written.

Kind Regards,

Robert Horn | Agfa HealthCare
Research Scientist | HE/Technology Office
T  +1 978 897 4860

Agfa HealthCare Corporation, 100 Challenger Road, Ridgefield Park, NJ, 
07660-2199, United States
http://www.agfa.com/healthcare/
Click on link to read important disclaimer: 
http://www.agfa.com/healthcare/maildisclaimer
_______________________________________________
Syslog mailing list
Syslog at ietf.org
https://www.ietf.org/mailman/listinfo/syslog