[OPSAWG]Re: TACACS+ w/ TLS 1.3 implementations

Hi, On 27.06.2024 17:01, Joe Clarke (jclarke) wrote: Who has implemented this draft or are planning to do so? https://github.com/MarcJHuber/event-driven-servers/tree/master/tac_plus-ng is a TACACS+ server implementation supporting TLS1.3 and is quite likely to match the draft requirements, bu

[OPSAWG]Re: TACACS+ w/ TLS 1.3 implementations

On Jun 27, 2024, at 11:01 AM, Joe Clarke (jclarke) wrote: > > Recently, there have been a couple of questions as to existing or planned > implementations of > https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs-tls13/ . While > this document is a propose standard and implementations ar

[OPSAWG]TACACS+ w/ TLS 1.3 implementations

Recently, there have been a couple of questions as to existing or planned implementations of https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs-tls13/ . While this document is a propose standard and implementations are not re

[OPSAWG]WG LC: draft-ietf-opsawg-tacacs-tls13

Hi Rod, Many thanks for your kind words and previous feedback which helped significantly. Regarding your comment, It is a good proposal, but just to clarify, the paras are intended to convey from the flow perspective: para 4 covers the client start, para 5 then deals with server behaviour i.e.

[OPSAWG]Re: WG LC: draft-ietf-opsawg-tacacs-tls13

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 co

[OPSAWG]Re: 🔔 WG Adoption Call for draft-gfz-opsawg-ipfix-alt-mark-01

Hi Henk, All, I support the adoption of this document as coauthor. Regards, Giuseppe -Original Message- From: Henk Birkholz Sent: Wednesday, June 26, 2024 11:59 AM To: OPSAWG Subject: [OPSAWG]🔔 WG Adoption Call for draft-gfz-opsawg-ipfix-alt-mark-01 Dear OPSAWG members, this email s