Hi Everyone,
Great work here! I'm really looking forward to having the TACACS+ with TLS (TACACSS) protocol progressed, I've been reading the drafts and am glad for the work everyone has put into progressing this. Revision 8 brought clarity for SS 3.3. TLS Identification which I had most concerns about, the document now has a great description for the TLS identification methods. I wonder however if there were to be any more revisions if Section 4. Obsolescence of TACACS+ Obfuscation could be made a bit simpler with paragraphs 4 and 6, both related to how the client handles session packets, being combined. Kind Regards, Rod Persky From: Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org> Sent: Monday, June 24, 2024 10:35 PM To: opsawg@ietf.org Cc: u...@ietf.org Subject: [EXTERNAL] [OPSAWG]WG LC: draft-ietf-opsawg-tacacs-tls13 With shepherd in hand (thanks, Med), we are kicking off a two-week working group last call for the TACACS+ secured with TLS 1.3 draft. This draft has received several reviews, and the authors have addressed all outstanding comments. That said, I have re-requested reviews from SEC DIR and OPS DIR to confirm it has resolved previously-raised issues. The question about port seems to have been addressed with a custom port being an appropriate proposal. The chairs would like all comments and feedback by July 8, 2024. We will be re-running the IPR poll in parallel. (Copying TLS in Applications [uta] list for more TLS application-layer visibility.) Thanks. Joe
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
