[squeak-dev] Re: [Vm-dev] Re: SecureSession frame types
Robert Withers
robert.w.withers at gmail.com
Sun Dec 20 14:33:55 UTC 2015
Ok, let me make one last change to this 7 byte alternate proposal for
the message specification. In the first 3 bytes with 4 fields, use
supersymmetry to specify 6bits per field. SO the alternate would look
like below...
The whole point of the multicast symbol is to provide for low-level
routers to not even have to decode the asn.1 header and distinguish all
our message and header types. Just grab the first byte and mask the
upper 6bits and shift, there is a destination specifier, at least in the
large, as an alternate tunneling capability and would support reuse of
4byte IP addresses for NAT. If we loose that and knock sanguinity back
to 2bits, then we are down to a 6 byte spec + payload. I'm mulling iot
over, obviously.
*msgSpec: 7 bytes binary encoded*
* HeaderSpecification: 3 bytes
o multicastSymbol: 6 bits
o sanguinity: 6 bits
o msgVersion: 6 bits
o hdrType: 6 bits
* msgSize: 2nd word, 4 bytes
o 4 bytes (total size with msgSpec, header, payload sizes)
--
. .. .. ^,^ robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20151220/27dfc57d/attachment.htm
More information about the Squeak-dev
mailing list
|