Hi,
You are right.
Anyway, Byzantine in Khronos was used to emphasize that even if an attacker identifies Khronos operation, it doesn't impact Khronos's security (since each time different servers are chosen at random).
I removed the Byzantine term and added this note in the security consideration section.
Best,
Neta
On Fri, Jul 7, 2023 at 2:40 PM Danny Mayer <mayer@xxxxxxxxxxxxxxxxx> wrote:
On 7/6/23 3:20 AM, Tim Chown wrote:
Nits:
The word ‘byzantine’ is used several times before it is explained, even with
forward references (except in the start of 4.1) to 4.3, and then in 4.3 I can't
find any use of the word. It would be nice to have it explained on first use.
>> Byzantine is just a term commonly used in distributed computing to represent a powerful generic attacker, for example the attacker is aware of the protocols run by others but is not limited to acting by them. I simplified the relevant sentence in the Introduction to show that Byzantine has no special meaning in this contest. I leave it there for the relation to the distributed computing literature.I’ve never heard of the term, and have a fair amount of experience in cyber, less so in classic distributed computing.
In the -18 version you’ve improved it but I’d suggest changing “(Byzantine)” in section 1 to “(which distributed computing literature often refer to as Byzantine attackers)” or something very similar. I think for an IETF doc you could just omit it.
Byzantine is used by Dave Mills in RFC5905 to describe the selection algorithm fault detection principles. See RFC 5905 Section 5. It's very specific to NTP.
Danny
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
