[governance] Uni.X to Uni.X .NETworking - Where Do 32-bit Address Blocks Fit ?

[Jim Fleming]

Given the 160 bit Uni.X to Uni.X .NETworking message format:

SSDD.SSDD.SSSSDDDD.SSSDDD.LLLLLLLLLL
SSSSSSSDDDDDDD.SD.DDSS.SSSSSSDDDDDD
SDSDGTTT.PPSSSDDD.CCCCCCCCCCCCCCCC
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

Assuming: 20+32+12

2 - Fixed 01  <<<<< From half of the First 4 Bits
2 - Fixed 01
4 - Now
3 - Fixed 000
7 - Now
2 - Fixed 11
<<<< 32-bits >>>>
1 - Fixed 0
6 - Fixed 000000
1 - Fixed 0
1 - Fixed 1
3 - Now

Where do 32-bit address blocks fit ?

0101.DDDD.000.DDDDDDD.11.<<<<32 bits>>>>.0.000000.0.1.DDD

Foot Soldiers:
01 - .CORPS
01 - .MOBILE

20 bits on the left and a 5 bit per letter symbol set implies 4 letters
(like .COM or .NET) on the left
12 bits on the right and a 4 bit per letter symbol set implies 3 letters
(like .3D including the dot)

With the string 0.000000.0.1.DDD and the fixed bits the 12 bit package with
character boundaries
looks like the following:

0000.0000.1DDD

Given the 4-letter symbol set: .CDEIMNOPRTUV389
that implies that common extensions would be dot-dot (0000.000) and a letter
from
the second half of the set because the 1 is fixed.

      1000 8 P
      1001 9 R
      1010 A T
      1011 B U
      1100 C V
      1101 D 3
      1110 E 8
      1111 F 9

If you were to write a numeric address, it can end in [DOT DOT Symbol]

Prefix:192.168.1.1..P

The Prefix comes from one of the 2,048 address space regimes. DDDD.DDDDDDD

What are the top 2,048 top level domains ?

Who was it that lied about the root-servers not being able to handle 2,048
TLDs ?

Is it fair to give each of them their own block of address space to manage ?
Note: Manage does not imply route or a geographic region, these are foot
soldiers, they move around.


_______________________________________________
governance mailing list
governance at lists.cpsr.org
https://ssl.cpsr.org/mailman/listinfo/governance