Eliot Lear (elear) wrote:
>> 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 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
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
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
On 2019-11-07 12:43 p.m., Alan DeKok wrote:
>> E.g. we have documented in
>> https://tools.ietf.org/html/draft-lear-eap-teap-brski-05#section-5 that:
>>
>> " A device that has not been bootstrapped at all SHOULD send an
>> identity of teap-bootstrap@TBD1. "
>>
>> If we register that
