Hi all,
draft-ietf-uta-email-deep-05 defines "Implicit TLS" in Section 4: 'a
mechanism where TLS is negotiated immediately at connection start on a
separate port (referred to in this document as "Implicit TLS")'
whereas published RFC 7525 uses the terminology "strict TLS". It is the
title of Section 3.2, which mentions 'a choice between strict TLS
configuration and dynamic upgrade from unencrypted to TLS-protected
traffic (such as STARTTLS)'.
I don't think any published RFC speak of implicit TLS, and I believe
there should be consistent naming of the same notion between RFCs. So,
wouldn't it be better to use in draft-ietf-uta-email-deep the wording
"strict TLS" instead of "implicit TLS"?
FWIW, I also use the "strict TLS" terminology in
draft-elie-nntp-tls-recommendations-01 that is currently in IETF Last Call:
https://www.ietf.org/id/draft-elie-nntp-tls-recommendations-01.txt
I hope that's fine, but of course it is still time to change it if
"implicit TLS" is in fact the right wording to use.
--
Julien ÉLIE
« Il y a des gens qui parlent jusqu'à ce qu'ils arrivent à trouver
quelque chose à dire. » (Sacha Guitry)
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
