Paul, Probably best to knock this one out now. We missed the transposed #s in the abstract.
spt > On Oct 9, 2024, at 09:45, RFC Errata System <rfc-edi...@rfc-editor.org> wrote: > > The following errata report has been submitted for RFC9662, > "Updates to the Cipher Suites in Secure Syslog". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid8135 > > -------------------------------------- > Type: Editorial > Reported by: Sean Turner <s...@sn3rd.com> > > Section: Abstract > > Original Text > ------------- > RFC 5245 (TLS Transport Mapping for Syslog) > > Corrected Text > -------------- > RFC 5425 (TLS Transport Mapping for Syslog) > > Notes > ----- > In other words s/RFC 5245/RFC 5425 in the 2nd sentence. > The correct reference for TLS Transport Mapping for Syslog is RFC 5425; like > it is in the header, the 1st sentence of the abstract, and the rest of the > document. > > Instructions: > ------------- > This erratum is currently posted as "Reported". (If it is spam, it > will be removed shortly by the RFC Production Center.) Please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > will log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC9662 (draft-ietf-uta-ciphersuites-in-sec-syslog-07) > -------------------------------------- > Title : Updates to the Cipher Suites in Secure Syslog > Publication Date : October 2024 > Author(s) : C. Lonvick, S. Turner, J. Salowey > Category : PROPOSED STANDARD > Source : Using TLS in Applications > Stream : IETF > Verifying Party : IESG _______________________________________________ Uta mailing list -- uta@ietf.org To unsubscribe send an email to uta-le...@ietf.org
