On Aug 26, 2025, at 10:27 AM, Jeffrey Haas <[email protected]> wrote: >> s/secret key/shared key/ ? > > I'm going to leave this one for Alan and the security folk to answer. The > document mostly uses "secret key" throughout the text.
The terminology could be either way. RFC 5880 uses both "secret key" and "shared key". I don't think either term is a show-stoppew. >> >> The page size of 256 sequence number is not really justified, I would naively >> have expected a much larger "page". Rate of 100's of pps is rather low level. > > ISAAC wasn't crafted to solve BFD's problems, we're just conveniently using > it. :-) The page size is a limitation of ISAAC. The only thing I know about cryptography is that I'm not going to invent my own version. An alternative to ISAAC would be to use a CSRNG, and then to manually pre-cache blocks of data. But then we have to choose a secure generator, and define how much data to cache. In contrast, ISAAC came with exactly the functionality that we need. The optimized authentication draft makes it easy to add such a construct later, if we so desire. Alan DeKok.
