Re: [OPSAWG] [radext] draft-ietf-opsawg-ucl-acl: User Access Control Group ID RADIUS Attribute

2023-10-12 Thread Heikki Vatiainen
;integer' as defined by https://datatracker.ietf.org/doc/html/rfc8044#section-3.1 This would make things easier to implementations since they would always get a matching type from the Radius layer instead of having to parse a 'string' type. -- Heikki Vatiainen h...@radiatorsoftware

Re: [OPSAWG] [radext] draft-ietf-opsawg-ucl-acl: User Access Control Group ID RADIUS Attribute

2023-10-12 Thread Heikki Vatiainen
for example, what's the Radius attribute length restriction. It would also make it clear on how to encode/decode a group-id value for transporting it over the new Radius attribute. Radius also has type 'text' for carrying UTF-8 encoded strings. https://datatracker.ietf.org/doc/html/

[OPSAWG]draft-ietf-opsawg-tacacs-tls13: Debugging TACACS+ over TLS

2024-11-25 Thread Heikki Vatiainen
is! Please excuse me for being a bit late for the party. -- Heikki Vatiainen h...@radiatorsoftware.com ___ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org

[OPSAWG]Re: draft-ietf-opsawg-tacacs-tls13: Debugging TACACS+ over TLS

2024-11-26 Thread Heikki Vatiainen
stems where TLS only protects test data. While the access that > >this information provides to TLS connections can be useful for > >diagnosing problems while developing systems, this mechanism MUST NOT > >be used in a production system. > > > > I’m not quite sure