Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    IPV6    |    The convoluted hot-mess that is IPV6    |    4,612 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,576 of 4,612    |
|    Victor Sudakov to Dmitry Protasoff    |
|    Two ISPs and backup for a home network (    |
|    01 Jul 21 20:31:04    |
      REPLY: 2:5001/100.1 60dcd6e7       MSGID: 2:5005/49 60ddc5c0       CHRS: CP866 2       TZUTC: 0700       TID: hpt/fbsd 1.9.0-cur 2019-12-05       Dear Dmitry,              30 Jun 21 23:17, you wrote to me:               DP>>> NAT66 is what NAT for ipv6 is called.               VS>> What was the incentive to create such an abomination?               DP> "There are more things in heaven and earth, Horatio,        DP> Than are dreamt of in your philosophy."(c)Shakespeare               DP> And original ipv6 was just a miserable philosophy, created by people        DP> with limited knowledge about real life.              The original IPv4 was also miserable with its classful networks, RIPv1 etc. I       still cannot imagine however what "real life" problem they are solving by       creating NAT for ipv6.               DP>>> NPTv6 is not a NAT, it's        DP>>> stateless solution.               VS>> Even if NPT is called "prefix translation" and is stateless, it        VS>> is still a NAT (in IPv4 terms, a type of a one-to-one NAT).               DP> NPTv6 is for prefix translation only, not for address translation.        DP> It's much more lightweight and easy to implement.              Either you translate only the higher 64 bits of the address, or the whole 128       bits of the address, you still rewrite the packet. True, you don't do PAT,       that's why I said that it looks like a one-to-one IPv4 NAT (much like in AWS       VPC "public" subnets).               VS>> However, the creators of IPv6 had better invent something like        VS>> "dead gateway detection" or some other way for end devices to        VS>> select a working outgoing address when they have several global        VS>> prefixes (and gateways) available. I thought my knowledge was        VS>> lacking, but it turns out the new and flashy protocol stack is        VS>> lacking.               DP> Do you have a time machine to send some ideas to ipv6 creators? :)              Nope, but I think $subj can be implemented today, e.g. via some field in RAs       etc. In FreeBSD (and I'm sure in other IPv6 implementations) you can select       the prerred source address, you only have to add some way to change it       automatically when a "dead gateway" is detected.              Victor Sudakov, VAS4-RIPE, VAS47-RIPN       --- GoldED+/BSD 1.1.5-b20170303-b20170303        * Origin: Ulthar (2:5005/49)       SEEN-BY: 1/123 30/0 50/109 80/1 90/1 105/81 120/340 123/131 154/10       SEEN-BY: 221/1 6 226/30 227/702 229/424 426 550 700 1016 240/1120       SEEN-BY: 240/5832 249/206 317 400 261/38 280/464 5555 282/464 1038       SEEN-BY: 301/0 1 101 113 812 317/3 322/757 342/200 460/58 463/68 467/239       SEEN-BY: 467/888 633/280 712/848 920/1 5000/111 5001/100 5005/49 53       SEEN-BY: 5015/46 5020/715 830 846 1042 2047 2140 4441 5053/54 5058/104       SEEN-BY: 5064/56 5083/1 444       PATH: 5005/49 5020/1042 301/1 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca