<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
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...<br>
<br>
<div class="moz-cite-prefix">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.<br>
<br>
<small><b><big><big><big><font face="DejaVu Serif">msgSpec: 7
bytes binary encoded</font></big></big></big></b></small><br>
</div>
<ul>
<li><big>HeaderSpecification: 3 bytes</big></li>
<ul>
<li>multicastSymbol: 6 bits</li>
<li>sanguinity: 6 bits</li>
</ul>
<ul>
<li>msgVersion: 6 bits</li>
<li>hdrType: 6 bits</li>
</ul>
<li><big>msgSize: 2nd word, 4 bytes</big></li>
<ul>
<li>4 bytes (total size with msgSpec, header, payload sizes)</li>
</ul>
</ul>
<br>
<br>
<div class="moz-signature">-- <br>
<div align="left">. .. .. ^,^ robert
</div>
</div>
</body>
</html>