Re: [radext] draft-ietf-radext-radiusv11-00 minor fixes

[Matthew Newton <[e-mail]>]

On 23/05/2023 20:46, Alan DeKok wrote:
> On May 23, 2023, at 1:16 PM, Matthew Newton <[e-mail]> wrote:
>>
>> I've gone through the latest draft. Page numbers below are from draft-ietf-radext-radiusv11-00.pdf.
>>

Just a handful more having checked the rest of the references.


Page 14

"EAP-PWD" is actually referred to as "EAP-pwd" in RFC5931

Not sure it's worth changing, but it was new to me.


-

Page 15 5.1.2 CHAP-Challenge

"[RFC2865] Section 5.2" -> should be section 5.3 (twice in this
para)


-

Page 15 5.1.4 VSAs

Says VSAs must be encoded as their base data type, then goes on to
say MS-MPPE-Send-Key and MS-MPPE-Recv-Key MUST be encoded as
'text'. RFC2548 gives them as 'String' (albeit 'plaintext
String'). I think this should be type string here (RFC8044 s3.5)
for consistency with 5.1.1 and 5.1.3 above?


-

Page 16 6.1 Status-Server

"extension [RFC7360] suggest" add comma "extension [RFC7360]_,_
suggest"


-


Maybe add an "Implementation Status" section as per RFC7360 Section 9? 
Though I don't know if anything other than FreeRADIUS implements it yet?


-- 
Matthew