Er, by which I mean that dates can be relative to the time stamped by something and kept for the connection duration. That would reduce the number of bits needed by a fair margin, assuming that is desirable. -=R On Wed, Jan 16, 2013 at 3:48 PM, Roberto Peon <grmocg@gmail.com> wrote: > How about setting epoch as the first request in the connection? :) > -=R > > > On Wed, Jan 16, 2013 at 3:45 PM, Nico Williams <nico@cryptonector.com>wrote: > >> On Wed, Jan 16, 2013 at 5:39 PM, Mark Nottingham <mnot@mnot.net> wrote: >> > On 17/01/2013, at 10:35 AM, Nico Williams <nico@cryptonector.com> >> wrote: >> > Yep, but you either need to make the epoch start at least a few years >> ago (old Last-Modified times, is important for heuristic freshness), OR >> keep it signed (losing a bit). >> > >> > And I think you need more than 12 bits for seconds in a day... >> >> Oops, for some reason I thought of seconds in an hour. So 5 more >> bits, and we're about even with seconds since epoch. Either way >> getting from 24 bytes to 4 is pretty good, and no compression scheme >> will do better. >> >> >
Received on Wednesday, 16 January 2013 23:49:30 UTC