Hi Russ, all, While waiting for a follow-up from Russ, I'd like to recall that the reasoning for the CURRENT wording in 3.2.2 was described in an external review (https://mailarchive.ietf.org/arch/msg/opsawg/U3mPq3WlRF48blMmr2uCF80KLiI/; see points# 7 and 8). That reasoning was consistent with the intent described by Doug below.
Cheers, Med (Doc Shepherd) De : Douglas Gash (dcmgash) <dcmg...@cisco.com> Envoyé : mardi 2 juillet 2024 10:07 À : Russ Housley <hous...@vigilsec.com>; sec...@ietf.org Cc : draft-ietf-opsawg-tacacs-tls13....@ietf.org; last-c...@ietf.org; opsawg@ietf.org Objet : Re: Secdir last call review of draft-ietf-opsawg-tacacs-tls13-10 Hi Russ, Many thanks for taking the time to review. Before we dig into the issues raised, I'd like to check to see if your comments spring from the doc misleading due to bad wording, or if you have in mind a deeper issue. What the doc is trying to express (and we will refactor a little to make this clearer), is that: * Implementations MUST always support the core implementation of mutual Cert based authentication. There is always the core of "compatibility" * Implementations MAY support other options as these options mature and are widely accepted, such as PSK, RPK * Deployments do not have to use Cert based if implementations support these other options. I suspect that this may not actually address your real concerns though: please let us know if the issues you see are deeper than the implementation/deployment matrix of options. Many Thanks! From: Russ Housley via Datatracker <nore...@ietf.org<mailto:nore...@ietf.org>> Date: Monday, 1 July 2024 at 19:06 To: sec...@ietf.org<mailto:sec...@ietf.org> <sec...@ietf.org<mailto:sec...@ietf.org>> Cc: draft-ietf-opsawg-tacacs-tls13....@ietf.org<mailto:draft-ietf-opsawg-tacacs-tls13....@ietf.org> <draft-ietf-opsawg-tacacs-tls13....@ietf.org<mailto:draft-ietf-opsawg-tacacs-tls13....@ietf.org>>, last-c...@ietf.org<mailto:last-c...@ietf.org> <last-c...@ietf.org<mailto:last-c...@ietf.org>>, opsawg@ietf.org<mailto:opsawg@ietf.org> <opsawg@ietf.org<mailto:opsawg@ietf.org>> Subject: Secdir last call review of draft-ietf-opsawg-tacacs-tls13-10 Reviewer: Russ Housley Review result: Not Ready I reviewed this document as part of the Security Directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Security Area Directors. Document authors, document editors, and WG chairs should treat these comments just like any other IETF Last Call comments. Document: draft-ietf-opsawg-tacacs-tls13-10 Reviewer: Russ Housley Review Date: 2024-07-01 IETF LC End Date: Unknown IESG Telechat date: Unknown Summary: Not Ready Major Concerns: Section 3.2.2 says: "Certificate based mutual authentication MUST be supported." I assume that this means that it MUST be supported, but I does not have to be used. However, the next sentence seems to require certificates, Section 3.2.2: With the removal of the reference to [RFC8773], how is the requirement for certificates accomplished while also using external PSKs? I am unaware of any other way to do so. Section 3.2.2 says: "...[RFC7250] must be used in context of [RFC8446]". How is the requirement for certificates accomplished with raw public keys? I am unaware of any way to do so. Minor Concerns: None Nits: None ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
