RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)
draft-aboba-radius-rfc2869bis-22

Date: Wed, 14 May 2003 10:24:16 -0700 (PDT)
From: Bernard Aboba
To: Randy Bush
Subject: Re: For mid-June agenda?

> they are on the agenda

We've just had an additional issue come up with respect to
RFC 2869bis-21.  Glen Zorn has found some issues with the suggested RADIUS
retransmission behavior.  We could put off the IESG review for a few weeks
in order to resolve his comments -- or the IESG can review his comments
along with RFC 2869bis-21.  The issue isn't terribly complex -- Glen
is suggesting that jitter be added and that the RTOinitial should be
larger than 3 seconds;  in addition he is asking that we separate
out the material on RADIUS retransmission behavior into a separate
document that would apply to all of RADIUS, not just RADIUS/EAP.

Overall, I agree with Glen's comments.  If we put off the IESG review a
few weeks, we can address them in a -22.

Date: Sun, 27 Apr 2003 09:48:34 -0700 (PDT)
From: Bernard Aboba
To: Randy Bush
cc: iesg@ietf.org
Subject: Re: Updated drafts addressing IESG comments

> > http://www.drizzle.com/~aboba/EAP/draft-aboba-radius-rfc2869bis-20.txt
>
> i thought this was already ballotted, but dt seems to disagree with me.
> i have tried to put it on next week's agenda, though it may be too late.

It is ok to wait on this. We are putting it through a "pseudo-WG last
call" in EAP WG along with RFC 2284bis. This ends May 12, 2003.

From: Randy Bush
Date: Sun, 9 Feb 2003 21:46:42 -0500
To: Bernard Aboba
Cc: iesg-secretary@ietf.org
Subject: Re: [iesg-secretary #5264] It's time...

> Actually, the most recent version is draft-aboba-radius-rfc2869bis-09.txt,
> submitted to the archive today (got a last minute comment in). Go ahead
> and do a 4 week IETF last call on it, which I'll announce to both AAA and
> EAP WGs as well.

secretariat, please issue a FOUR WEEK IETF last call for info on the
document draft-aboba-radius-rfc2869bis-09.txt when it appears in the
archive.

thanks.

randy

Four weeks would be good, both for this and draft-chiba. That way we can
go around to all the various constituencies and make sure they read it and
comment.

bernard sez:
Jari Arkko found some issues with -07 of RFC 2869bis so we are
holding that draft for -08, which should be available next week.

bernard sez

This draft is an update to RFC 2869 to resolve interoperability issues. It
is cited by IEEE 802.1aa, which has requested that it be published as an
RFC prior to completion of the IEEE 802.1X-2003 standard, currently
estimated to occur in Spring, 2003.

To get it ready, we've asked for comment from IEEE 802.1aa, and AAA WG.
draft-ietf-aaa-eap-00.txt is also dependent on RFC 2869bis, since it
incorporates much of the same text.

Given the timelines, we're expecting this draft to go to IETF last call
(along with draft-congdon-radius-8021x) sometime in January, 2003.
Assuming that IETF last call comments and IESG review is favorable, given
that publication is requested by an SDO, is there a way to get it through
the RFC editor more rapidly?