Re: [radext] Control of RFC 3580. Transfer to RADIUS WG possible?

[Alan DeKok <[e-mail]>]

On Oct 7, 2015, at 10:16 AM, <[e-mail]> <[e-mail]> wrote:
> Obviously, it does not prevent RADEXT to work on a new version of this document. However, before rushing for publishing a bis-version of this document, it would be good to know what would be the purpose of this new document.

  To bring the standards up to date with current requirements, and with current use-cases.  To address ambiguities in the current specifications.  To clarify best practices.
 
> The initial aim was to have non-normative text describing how to use RADIUS with 802.1X, and this material was put in an information RFC as well as in a non-normative appendix in IEEE specification. 
> 
> I know that some cleanup/updates/clarifications are required for this document. But to be really useful,  it could be interesting to know whether IEEE would be happy to endorse/reference the new version of the RFC, especially if some proposed changes have impacts on existing RADIUS implementation. Just to ensure that the proposed modifications/clarifications put in a bis-version will be followed by IEEE community.

  I agree.

> And also, what should be the status of this document: Standard track/Informational?

  Probably the same as RFC 3580, informational.

> Now, if the work is agreed, the proposed changes straightforward and there is no contentious discussions, I don't see why a 3-year period would be required to publish a new version. It will depend on the amount and type of change.

  I agree.  I'll work with Nick to come up with an I-D.  I won't be in Yokohama, but I can do a remote presentation.

  Alan DeKok.