On October 8, 2019 at 12:04 bill@herrin.us (William Herrin) wrote:
On Tue, Oct 8, 2019 at 12:01 PM <bzs@theworld.com> wrote:
My main point is, as I said, Bits is Bits, whether they're human readable (for some value of "human") like URLs or long hex strings which perhaps are less human readable.
Bits aren't just bits. Bits with useful properties (such as aggregability which coincides with the routing structure) are better bits.
Yet somehow we manage to start with URLs (for example.) My point is whatever is used it can be mapped to something perhaps more efficient given some design goals, such as the DNS does. And for that matter route lookup tables w/in routers. So at the end of the day all that is absolutely needed is (reasonable) unambiguity because in general ambiguity can't be fixed, the packet has to go somewhere. Different schemes might present different design opportunities but they all need to be unambiguous as routing endpoints. -- -Barry Shein Software Tool & Die | bzs@TheWorld.com | http://www.TheWorld.com Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD The World: Since 1989 | A Public Information Utility | *oo*