[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [dhcwg] A new draft of draft-jiang-dhc-secure-dhcpv6 is submitted. Comments are welcome!
Date: Mon, 14 Jul 2008 08:52:44 -0400
From: "Bernie Volz (volz)" <volz at cisco.com>
Message-ID: <8E296595B6471A4689555D5D725EBB21080C9F6F at xmb-rtp-20a.amer.cisco.com>
| it will add the AUTH option and then any options
| requested by the client. The server adds the option and then, just
| before sending the packet, does a callback to a function that is
| responsible for calculating the hash and storing it into the buffer to
| be transmitted.
[...]
| Sure, you have to know the key to figure out the signature size.
So you're saying that this implementation, if it was to add support
for CGA authentication (assuming that's decided to be worthwhile)
then it would get the key, figure out the length of the signature,
allocate space, then go do other stuff, then come back later, get the
key again, calculate the signature, and store it.
Why?
That's nothing like the way I'd write it.
kre
_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg