On Tue, 26 Sept 2023 at 15:01, <[email protected]> wrote: > Hi RADEXT, > > > > FWIW, the document specifies the following new RADIUS attribute: > > > https://boucadair.github.io/policy-based-network-acl/draft-ietf-opsawg-ucl-acl.html#name-user-access-control-group-i >
Hello Med, the example tables in the draft show that "Group ID" is an integer. Also, the YANG module shows that group-id has type uint32 with range "0..4294967294". If the value communicated with the new Radius attribute maps directly to a value with a uint32 type, why not use Radius type '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 [email protected]
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
