On Fri, Oct 05, 2001 at 09:14:48AM -0500, Chris M. Lonvick wrote: > Hi, > > I'm going to split up the discussion a bit so we can tackle it > in pieces. We need to do a holistic review but I think that we > need to first get some consensus on some specifics. I'm going > to start with the address of the device in the payload block. > (I'll keep going till the flight lands. ;-) > > Section 4.2 states: > ============== > 4.2. Building the Payload Block > > The payload block is built when a new reboot session is started. > There is a one-to-one correspondence of reboot sessions to payload > blocks. That is, each reboot session has only one payload block, > regardless of how many signature groups it may support. > > The payload block consists of the following > > a. Unique identifier of sender; by default, the sender's 128-bit IP > address encoded in base-64. > ============== > > Why not just leave this as the "decimal-dot" (IPv4) or "decimal-colon" > (IPv6) representation? For example, if the sender's address is 10.1.1.1 > then it will be 0x0a010101 in the IP header but will be "10.1.1.1 " in > the payload. This may drive the total number of signatures down to 6 in > the payload block but I think that I might rather see the address in > cleartext rather than in base-64. If that makes sense, the representations > are defined in STD-13 (IPv4) and RFC-2373 (IPv6).
Am I wrong that this payload block is used only when certificates are distributed, and not in signature groups. So the size of the field doesn't affect the number of signatures one can put into a single log message. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
