Re: [radext] I-D Action: draft-ietf-radext-tls-psk-03.txt

[Peter Deacon <[e-mail]>]

On Mon, 18 Sep 2023, Alan DeKok wrote:

> On Sep 18, 2023, at 11:25 AM, Bernard Aboba <[e-mail]> wrote:

>> [BA] Yes, but most likely it's TLS 1.2 or earlier.  The time between 
>> 1.2 and 1.3 was so long that a lot of equipment end-of-life'd before 
>> 1.3 came out, but is still operating.  That equipment will never get a 
>> TLS 1.3 upgrade, which means that when TLS 1.2 is deprecated it will 
>> need to be retired. As an example, for enterprise WiFi, there are 
>> probably many 802.11AC deployments out there from the mid to late 2010s 
>> that are now at or nearing end-of-life and therefore may not get a TLS 
>> 1.3 upgrade. Will be interesting to see if those devices will be 
>> offered an upgrade to secure RADIUS with TLS 1.2.  Often vendors limit 
>> those upgrades to newer equipment.

>  I think then mandating TLS 1.3 is best then.  If it takes a while for
>  people to add TLS-PSK, there are few reasons to allow TLS 1.2.

I don't think TLS 1.3 should be required.

We are also supporting PAKEs and until OPAQUE is ready the only usable 
PAKE only works with TLS 1.2.  Limiting TLS-PSK to 1.3 means people using 
older TLS stacks won't be able to use TLS-PSK and if there are any version 
specific problems with TLS found they won't be able to switch versions.

regards,
Peter