Re: [auth48] AUTH48: RFC-to-be 9325 <draft-ietf-uta-rfc7525bis-11> for your review

[Thomas Fossati <[e-mail]>]

Hi all,

After a full read, some further (very minor) comments.
Feel free to disregard the one marked as "missing comma", that’s how I’d do in Italian.

(BTW, I agree with Yaron’s previous batch.)

Cheers, t

---

(decrease word count)

OLD
was published when the industry was in the midst of its transition to TLS 1.2.

NEW
was published when the industry was amid its transition to TLS 1.2.

---

(missing comma)

OLD
Years later, this transition is largely complete and TLS 1.3 is widely available

NEW
Years later, this transition is largely complete, and TLS 1.3 is widely available

---

(avoiding repeating "particular")

OLD
based on their particular circumstances (e.g., for use with a particular application protocol);

NEW
based on their particular circumstances (e.g., for use with a specific application protocol);

---

(decrease word count)

OLD
Certificate chains often take up the majority of the bytes transmitted during the handshake.

NEW
Certificate chains often take up most of the bytes transmitted during the handshake.

---

(harmonise bullet-lists style)
(unless there is a stringent reason for making this an exception?)

OLD
* limit the number of names or extensions;
* use keys with small public key representations, like the Elliptic Curve Digital Signature Algorithm (ECDSA); and
* use certificate compression.

NEW
* Limit the number of names or extensions.
* Use keys with small public key representations, like the Elliptic Curve Digital Signature Algorithm (ECDSA).
* Use certificate compression.

---

(decrease word count)

OLD
shared secrets for all of its AEAD cipher suites

NEW
shared secrets for all its AEAD cipher suites

---

(harmonise RFC-quoting style in §3.8 with §3.7)

OLD
"In the event that the server supports no protocols that the client advertises, then the server SHALL respond with a fatal 'no_application_protocol' alert."

NEW
| In the event that the server supports no protocols that the client
| advertises, then the server SHALL respond with a fatal
| 'no_application_protocol' alert."

---
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.