> At the time of the synchronization, the EB frame can neither be authenticated
> nor its freshness verified.
I suggest:
> At the time of the synchronization, the EB frame can neither be authenticated
> nor its freshness verified. An attacker could have fabricated the EB, or
> may have simply
the receive time attached to
> the frame as a meta of sorts to enable the delayed validation?
> >
> > All the best,
> >
> > Pascal
> >
> >> -Original Message-
> >> From: 6tisch <6tisch-boun...@ietf.org> On Behalf Of Thomas Watt
ation?
>
> All the best,
>
> Pascal
>
>> -Original Message-
>> From: 6tisch <6tisch-boun...@ietf.org> On Behalf Of Thomas Watteyne
>> Sent: vendredi 26 juillet 2019 17:08
>> To: Mališa Vučinić
>> Cc: 6tisch <6tisch@ietf.org>
>&
Pascal Thubert (pthubert) writes:
> I'm wondering about the delayed security processing. That processing
> may be delayed beyond the current ASN. Is the ASN of the receive
> time attached to the frame as a meta of sorts to enable the delayed
> validation?
There is TimeStamp parameter to the
Mališa Vučinić writes:
> I worked on the initial version of the text describing the ASN
> replay attack and its resolution discussed during the Montreal
> meeting.
>
> The text can be found at:
>
>
6tisch <6tisch-boun...@ietf.org> On Behalf Of Thomas Watteyne
> Sent: vendredi 26 juillet 2019 17:08
> To: Mališa Vučinić
> Cc: 6tisch <6tisch@ietf.org>
> Subject: Re: [6tisch] ASN replay attack -- proposed text
>
> Malisa,
> The text IMO explains both the probl
Malisa,
The text IMO explains both the problem and the solution very well, congrats.
Thomas
> On 26 Jul 2019, at 20:23, Mališa Vučinić wrote:
>
> Dear all,
>
> I worked on the initial version of the text describing the ASN replay attack
> and its resolution discussed during the Montreal
Dear all,
I worked on the initial version of the text describing the ASN replay attack
and its resolution discussed during the Montreal meeting.
The text can be found at:
https://bitbucket.org/6tisch/draft-ietf-6tisch-minimal-security/commits/4ea5f58b1a3245a1e2a2b46f95f0fd48b2f4bb31
Please
