This topic contains 6 replies, has 1 voice, and was last updated by 
Josh Stern November 14, 2022 at 9:00 pm.
-
Posts
-
Josh Stern
ModeratorStrategies from my POV:
GT should plan long term to be a major/dominant player in routing of various types, hardware & software
Short term, it looks like the easiest strategy is to commission some of our I-affiliates to run modified router nodes (our mods), viewing them as colleagues/partners in that long term agenda.
For multi-path routing over IP6 payloads with novel GT stuff inside, the front of the GT payload needs to understand it’s part of multi-path strategy & how to read/pop some stack of instructions about what is to be done at the front of the data stream. The last car of the data stream can contain the info/instructions it needs about extra health check/acks/diagnostics beyond IP6 for it’s path component. And then the same is true for the post-assembled payload from multi-paths.
Take that framework & see what needs to be done to bring legs to more primitive data packet relay forms.
-
Josh Stern
ModeratorAlso about IP6 loading. It will be helpful to make sure coding has special forms for “Here I removed N zeros for compression” & “Here I added N zeros for packet padding.” That way, forexample, multi-path which has a lot of uncertainty about speed can use redundant routes & then work with what finishes first. The remaining,promised IP6 packets can be filled with padding while the content message is away to it’s next destination.
-
Josh Stern
ModeratorKey application example is some rural fields of plentiful but slow & not completely reliable paths. We want redundant parallel tries. The receiver coordinator can easily check when a complete set has been received and begin next stage processing. For IP6 or similar protocols we might be finishing up our freight commitments with side cargo or there might be no other message running, so padding happens.
-
Josh Stern
ModeratorMy thoughts about the form & options for receipts
a) Receipts confirming intact msg to receiver should be crypto based
b) Receipts are not accomodated within IP6 level. They are a return msg with a special bit indicating a receipt confirmation
c) Options from the sender are
Generate a receipt msg? Yes or No?Delay time of sending in some random delay window [delay1,delay2]
Send to this other node N which may implement some sort of mailbox storage for receipts or tryforward a summary to the sender
Should the receipt msg. demand a receipt of receipt msg? Yes or No? If yes, then a failure will result in a failure msg to the original sender and a log that can be queried.
-
-
-
-
Josh Stern
ModeratorAnother form of transport that is hard to turn off is the WhoIsIT Foundation network node running email/smtp as a transport service for payload routing/briding.
-
Josh Stern
ModeratorHacking “fax lines” is another possible format for encrypted data tunnels to use.
You must be logged in to reply to this topic.