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

[Alexander Clouter <[e-mail]>]

On Fri, 18 Aug 2023, at 21:07, Alan DeKok wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories. This Internet-Draft is a work item of the RADIUS EXTensions
>> (RADEXT) WG of the IETF.
>> 
>>   Title           : RADIUS and TLS-PSK
>>   Author          : Alan DeKok
>>   Filename        : draft-ietf-radext-tls-psk-02.txt
>>   Pages           : 14
>>   Date            : 2023-08-18
>> 
>> Abstract:
>>   This document gives implementation and operational considerations for
>>   using TLS-PSK with RADIUS/TLS (RFC6614) and RADIUS/DTLS (RFC7360).

Looks fine to me, "ship it" (after touching up the paint job).

"Implementations MUST use ECDH cipher suites", is this not meant to be "Implementations MUST support ECDH cipher suites" or because pinning cipher suites tends to not age well?

s/labelled/labeled/g   <-- probably my fault, I think I nitted the US to GB in the last one
s/incorret/incorrect/g

Typo in: "We note that the PSK identity is a field created >>but<< the connecting client", should be "We note that the PSK identity is a field created >>by<< the connecting client".

I think someone here had a preference for non-compressed CIDRs: s~192.0.2/24~192.0.2.0/24~

Thanks