Subject: [radext] Re: New I-D: draft-seralathan-radext-persistent-devid-00
From: "Alexander Clouter" <[email-masked]>
To: "Alan DeKok" <alan.dekok=[email-masked]>, "Premanand Seralathan (pseralat)" <pseralat=[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Date: Tue, 26 May 2026 12:20:16 +0100
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>

On Tue, 26 May 2026, at 11:50, Alan DeKok wrote:
>
> [snipped User-Name/CUI suggestion]
>
> And then the functionality works, without changing anything else in 
> RADIUS.  The main downside here is that there's no separate attribute 
> for persistent device ID.  But I think the main goals of the document 
> are met.

Multiple 'Class' attributes are allowed too.

Section 2.3 of the draft is wrong in stating Class is unsuitable as it is not stable, the value is determined by the RADIUS server so can be set to whatever you want.

This could be solved by using a prefix (for example 'devid:') to colour your device ID value and extract it from the accounting data.

Cheers

Alex