Hello Chris,
Thank you (to all authors) for bringing this forward. That effort is very much
appreciated, specifically as we rely on it in work done in IEC on power system
automation security.
I reviewed the latest version of the draft. I also reviewed earlier versions
and the updated version d
Hi Sean,
Yes, that seems already to fit.
Best regards
Steffen
> -Original Message-
> From: Sean Turner
> Sent: Dienstag, 31. Januar 2023 15:37
> To: Fries, Steffen (T CST)
> Cc: Uta@ietf.org
> Subject: Re: [Uta] I-D Action:
> draft-ietf-uta-ciphersuites-in-sec-s
Hi Sean,
I was just wondering how the progress of
draft-ietf-uta-ciphersuites-in-sec-syslog is seen. We are in the next step of
the IEC specification and it would be good to have a RFC, which can be
normatively referenced. Anything I can provide support?
Best regards
Steffen
> -Original
Hi Chris,
Based on the implementations in industry that I'm aware of, I would see TLS 1.2
as mandatory and TLS 1.3 as optional. The take up of TLS 1.3 is not as fast and
will take a while.
Best regards
Steffen
From: Uta On Behalf Of Chris Lonvick
Sent: Montag, 12. September 2022 00:25
To: Uta
Hi Hannes,
Just saw your review. Should have pointed to yours as we found similar nits.
Regarding to your last point. The text stated in Section 7 was used to show how
the draft is referenced in the IEC documents. It was incorporated in the draft
IEC document to make the reader aware that there
Hi,
During the UTA WG meeting I volunteered to review the latest draft
draft-ietf-uta-ciphersuites-in-sec-syslog-01. Thank you again to the Chris,
Sean, and Jo for the update to syslog security as it is directly used /
referenced in IEC TC57 WG15 documents.
I just found some nits in the draft
Hi all,
Thank you for taking up this issue. We started the discussion based on work we
are currently doing in IEC TC57 WG15, in the context of security event logging.
As we rely on syslog and are using TLS to secure it, there was a request to be
able to support it with current cipher suites as
