[radext] SAAG Report for radext WG

[Margaret Cullen <[e-mail]>]

The radext WG met on Monday morning.  

We discussed the open issues with the RADIUS/(D)TLS update (draft-janfred-radext-radiusdtls-bis) in some detail. We confirmed that it has been adopted as a WG work item on the mailing list, and that it will be republished with a new name after the meeting. We also reached rough consensus on the resolutions to several open issues  (subject to mailing list confirmation).  The document needs additional work, including the addition of Security Considerations.

RADIUS/1.1 (draft-ietf-radext-radiusv11) is nearly complete, with minor issues still under discussion on the mailing list. It will go to WG Last Call when those issues are resolved.

The RADIUS/TLS-PSK draft (draft-dekok-radext-tls-psk) is ready for WG Last Call immediately after the IETF meeting. 

The Reverse COA draft  (draft-dekok-radext-revesre-coa) has expired and will be republished, after which we will make a call for adoption as a WG draft.  This document predated the WG re-charter, it has been stable for some time, and it will likely be ready for WG Last Call shortly after WG adoption.

The Deprecating Insecure Uses of RADIUS document (draft-dekok-radext-deprecating-radius) was adopted as a WG document at the March interim, but that was not confirmed on the list.  We will confirm WG adoption immediately after the IETF meeting, and send the document to WG Last Call once the few remaining issues are resolved on the mailing list.  This draft is dependent on the RADIUS/(D)TLS draft, though, so it will not be published as an RFC until that draft is also ready for publication.

We also received an informational presentation on RADIUS Attributes for 3GPP 5G AKA (draft-gundavelli-radext-5g-auth-01).  The chairs and authors will discuss how to proceed on this document with the AD.