I'm probably confused, or the example has been simplified.. but On Mon, May 7, 2012 at 2:58 PM, Brian Dickson <[email protected]> wrote: > Scenario 2: > perform basic pseudo-signature once, repeat for routing table of 400,000 in > size. > pseudo-signature operation: > use N distinct pseudo-random number generators (PNRG), seeded > separately with state preservation (N=8 corresponds to 256 bits of entropy) > call random() from each preserved state to generate a 32-bit random > number, concatenate the N x 32 bit values
how do I check 3 as-hops away that whatever is attached to the update means that the update was signed? you seem to be saying: "sign with some random bytes that you make up on the fly". -chris _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
