Re: [AAA-WG]: Wrapping up Diameter EAP...

[Jari Arkko <[e-mail]>]

Yes. How about making the same statement as in RFC 3579,
but add Session-Id AVP in there as well?

--Jari

Bernard Aboba wrote:
> A question:
> 
> RFC 3579 requires that a RADIUS client be able to differentiate one EAP
> session from another.  As we've been discussing in EAP WG, this may be
> tricky in the case where an EAP authentication is restarted via an
> EAPOL-Start message.
> 
> I don't see any text in this draft equivalent to RFC 3579, Section 2.6.1
> that describe how Diameter handles this problem.  I suspect that Diameter
> should be able to do better than RADIUS, but guidance on how the server
> should behave would be helpful.
> 
> On Wed, 12 May 2004 [e-mail] wrote:
> 
> 
>>Hi,
>>
>>I've posted an intermediate version of draft-ietf-aaa-eap-06.a
>>at http://www.cs.hut.fi/~peronen/eap/diameter_eap.html
>>together with a HTML diff from version -05.
>>
>>This is supposed to resolve all remaining open issues, but
>>I would encourage everyone to check if they are OK with
>>the changes.
>>
>>If I don't get any complaints, I'll post this as -06 some time
>>next week and ask the WG chairs to send it to the IESG.
>>
>>Best regards,
>>Pasi
>>
> 
>