Hi Jared,
I suspect there is a disconnect here.
The guidance is not about random protocols, please check
https://richsalz.github.io/draft-use-tls13/draft-ietf-uta-require-tls13.html
which I think has the correct words.
Cheers,
Med
> -Message d'origine-
> De : Jared Mauch
> Envoyé :
Hi Toerless, all,
Please see inline one clarification comment as I think that is important.
Cheers,
Med
> -Message d'origine-
> De : Toerless Eckert
> Envoyé : mardi 8 avril 2025 18:05
> À : draft-ietf-uta-require-tls13@ietf.org; last-c...@ietf.org;
> uta@ietf.org; i...@ietf.org
> C
Mohamed Boucadair has entered the following ballot position for
draft-ietf-uta-require-tls13-09: Yes
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
Mohamed Boucadair has entered the following ballot position for
draft-ietf-uta-require-tls13-06: Yes
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
Hi all,
FWIW, we had an offline discussion with Alan and the authors to clarify the
concerns.
I'm reporting the main outcome of that discussion, fwiw:
(1) Alan agreed that:
* It is good practice to leverage existing standards
* Repeating details isn't useful
(2) Still, the key comment fro
Hi all,
This version adequately addresses my previous reviews.
The only remaining comments I have are triggered by the recent mgt exercise
https://mailarchive.ietf.org/arch/msg/opsawg/dRBbEoJ3Kgd8U9uvdcQbdFM3Sfo/ which
revealed the need to be explicit about the intended behavior on some few ite
