Re: [pcp] EAP-over-PCP

[Alper Yegin <[e-mail]>]

>> I don't understand how this works.
>> EAP authenticator performs rexmits. 
>> So, if it does not get a response, it'll keep rexmitting. So, how can you achieve "server will never generate an unsolicited request"?
> 
> A retransmission is not an unsolicited request...  I'm not sure what you mean by this.

If the EAP authenticator does not receive a response on time, it'd re-xmit the EAP request.
Which in turn will be transmitted by the PCP server to the PCP client.
That transmission is not "solicited by the PCP client".

> 
>> And, furthermore, there'd be EAP re-authentication which can be initiated by the client or server. This is another reason for having to support server-side requests.
> 
> Why do you think that we need to support EAP re-authentication? 
> 

EAP re-authentication is one of the EAP events, and any EAP lower-layer has to support that.
Otherwise, what? Your sessions have infinite lifetime? Authorization never changes? Never need to re-key? Never need to challenge the end-point again?
These are the things that call for "re-authenticaiton", and why EAP has that, and why EAP lower-layers need to support that.

Alper







> Margaret
> 
>