A couple things that stand out to me from having basically read the whole
thread in one go (this is not intended to be an exhaustive list of open
questions):
It was implied but not fully clear to me, that Ryan thinks that someone so
inclined could, right now, go around trying to connect to wifi us
There has been a lot of discussion on this thread, but I do not see
anything actionable for the EAP-TLS 1.3 specification.
Joe
On Wed, Jan 8, 2020 at 12:48 PM Alan DeKok
wrote:
> On Jan 8, 2020, at 3:00 PM, Michael Richardson
> wrote:
> >
> >
> > Alan DeKok wrote:
> >alan> Many people use
On Wed, Jan 15, 2020 at 2:24 PM Roman Danyliw wrote:
> Hello!
>
> I conducted an AD review of draft-ietf-emu-rfc5448bis-06 and this document
> is in good shape. Thanks for all of the work on it. I have minor
> questions and editorial nits which can be addressed with the IETF Last Call
> feedbac
The IESG has received a request from the EAP Method Update WG (emu) to
consider the following document: - 'Improved Extensible Authentication
Protocol Method for 3GPP Mobile
Network Authentication and Key Agreement (EAP-AKA')'
as Informational RFC
The IESG plans to make a decision in the n
Hello!
I conducted an AD review of draft-ietf-emu-rfc5448bis-06 and this document is
in good shape. Thanks for all of the work on it. I have minor questions and
editorial nits which can be addressed with the IETF Last Call feedback.
Minor:
-- Can you revisit the history -- why was RFC4187 inf
> On 15 Jan 2020, at 16:10, Michael Richardson wrote:
>
>
> Eliot Lear (elear) wrote:
>>> Owen, do we have a need to recognize that a device needs to perform
>>> onboarding again after a movement?
>>>
>>> i.e. device A enrolls on network 1, gets an LDevID usable on network
>>> 1, uses that w
Eliot Lear (elear) wrote:
>> Owen, do we have a need to recognize that a device needs to perform
>> onboarding again after a movement?
>>
>> i.e. device A enrolls on network 1, gets an LDevID usable on network
>> 1, uses that with EAP-FOOBAR.
>>
>> device A then is mov
Hi Michael,
>
> Owen, do we have a need to recognize that a device needs to perform
> onboarding again after a movement?
>
> i.e. device A enrolls on network 1, gets an LDevID usable on network 1,
> uses that with EAP-FOOBAR.
>
> device A then is moved to network 2, it tries to use same LDevID
