Thanks for bringing this up, Jouni. I agree that this need to be specified
somehow.
(Another possible way to document this is to put it in the revision that we
were planning for EAP-AKA’.)
Jari
___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/m
Hi,
I’ve been thinking of what to do with the EAP work that got discussed both in
the SAAG meeting last time (my drafts), as well on the list. The latter was
more on the EAP-TLS side, and it seems that the discussion has converged to a
reasonable direction recently.
Wondering how we could get
On Dec 21, 2017, at 8:40 AM, Jari Arkko wrote:
>
> I’ve been thinking of what to do with the EAP work that got discussed both in
> the SAAG meeting last time (my drafts), as well on the list. The latter was
> more on the EAP-TLS side, and it seems that the discussion has converged to a
> reaso
> The Session ID also needs to be defined for SIM and AKA, as per Jouni's
> comments. That doesn't fit in with AKA' changes.
Yeah, I was thinking about that but didn’t go far enough. But you’re right.
Maybe this needs to be a separate item for EAP-SIM.
> It may also be worth re-examining EAP-
On Dec 21, 2017, at 9:07 AM, Jari Arkko wrote:
>
>> I've seen people run into this issue with large certificates and long
>> certificate chains. It would be good to find a way to allow this use-case.
>
> That’s interesting.
>
> Do you have any suggestions on what to do about this issue, or we
