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,871 of 4,612    |
|    Michiel van der Vlist to Alexey Vissarionov    |
|    List of IPv6 nodes    |
|    18 Jan 22 14:06:23    |
      TID: FMail-W32 2.1.3.7-B20170919       RFC-X-No-Archive: Yes       TZUTC: 0100       CHRS: CP850 2       MSGID: 2:280/5555 61e6bdf3       REPLY: 2:5020/545 61e49235       Hello Alexey,              On Monday January 17 2022 00:38, you wrote to Richard Menedetter:               RM>> Sure ... I agree. My reply was more from the ISP point of view.        RM>> With 1 v6 subnet it is easy, you just announce the subnet.               AV> No: when you need to provide the customer with IPv6, you assign one        AV> fixed address for a link, and route a /64 subnet through that address.               AV> Plastic routers (those sold for 20 EUR) deal with this setup just        AV> fine.              My provider issued "plastic box" already uses three subnets all by itself. The       first subnet is routed to the local LAN. (WiFi + wired). The second subnet is       rserverd for the private guest network. (WiFi only). The third subnet is for       the providers own guest network. (WiFi only).              The box supports pefix delegation, so I can connect another router and have       more subnets routed to that router.               RM>> If you allow more, you need a way to configure them. (eg. VLANs,        RM>> different subnet on different LAN port, etc.)               AV> Or simply route more /64 subnets through that address. Or /56 at once.              My provider gives me a /56 routed through that "plastic box".               RM>> That is added complexity for a low cost product, where most of        RM>> your residential customers will have no clue what this is all        RM>> about. So it makes more sense to offer that on higher tier (and        RM>> more expensive) services.               AV> That violates the KISS principle.              Indeed. It is easier to just give every customer a /56. And just route the       first /64 to the LAN, so that the user need not configure anything if he only       needs one /64. And the provider does not need to configure anything if the       customer needs more.                     Cheers, Michiel       --- GoldED+/W32-MSVC 1.1.5-b20170303        * Origin: he.net certified sage (2:280/5555)       SEEN-BY: 1/123 15/0 19/10 30/0 80/1 90/1 105/81 106/201 120/340 123/131       SEEN-BY: 153/7715 154/10 203/0 221/0 1 6 226/30 229/110 317 400 424       SEEN-BY: 229/426 428 550 664 700 240/1120 5832 249/206 250/1 266/512       SEEN-BY: 280/464 5003 5006 5555 282/464 1038 301/0 1 101 113 812 310/31       SEEN-BY: 317/3 320/219 322/757 342/200 396/45 460/58 633/280 640/1384       SEEN-BY: 712/848 920/1 2452/250 5019/40 5020/545 1042 12000 5053/58       SEEN-BY: 5058/104       PATH: 280/5555 301/1 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca