5 ms·
... For many of these systems, I don't control the user's router. I don't know how you imagine I'm supposed to create DNS records for each device when they're
by mort96 1y ago
...
For many of these systems, I don't control the user's router. I don't know how you imagine I'm supposed to create DNS records for each device when they're assigned some random IP address at some random network I don't control.
- stavros 1y agoHave the device ping a central server and create randomword.centralserver.com, for example. However, if the problem is the DNS record, why has this thread been exclusively about globally routable IP addresses until now?
- mort96 1y agoIn https://news.ycombinator.com/item?id=45957048 https://news.ycombinator.com/item?id=45957048, addisonj suggested that the problem stems from the distinction from "local" and "global", and that with IPv6, you don't need that distinction. That quite naturally flows into the question: okay, how are these devices supposed to get global IPv6 addresses then?
- stavros 1y agoYes, with IPv6, there are are enough addresses that you don't need to use NAT. All IPv6 devices that are connected to the internet have global IPv6 addresses. I don't quite understand the question here, it seems to me that we're asking "but how could we possibly do this entirely mundane everyday thing?".
- mort96 1y agoNot all devices connected to the Internet have globally unique IPv6 addresses, SLAAC and often DHCPv6 makes local v6 addresses. Where's the globally unique IPv6 address supposed to be coming from?
- stavros 1y agoThis explains it fairly well, I think: https://thisbridgeistheroot.com/blog/dhcpv6-prefix-delegation https://thisbridgeistheroot.com/blog/dhcpv6-prefix-delegatio...
- mort96 1y agoSo you're talking about being assigned temporary globally unique addresses, if the network the device happens to be on at any given time happens to be set up in a certain way? I still don't understand how this is supposed to help.
- stavros 1y agoIn https://news.ycombinator.com/item?id=45957048 https://news.ycombinator.com/item?id=45957048, addisonj suggested that the problem stems from the distinction from "local" and "global", and that with IPv6, you don't need that distinction. This helps because you don't have a NAT distinguishing between "local" and "global", all devices are in the global namespace. All the comments after that have been about solving an arbitrary and ill-defined problem with goalposts that keep shifting from globally unique addresses to DNS hostnames to permanent addresses.
- mort96 1y agoHow does getting a temporary globally unique IPv6 address from DHCPv6 solve any of the issues surrounding how new web technologies aren't available in "insecure contexts"? I assumed that the suggestion was that you could assign a device a permanent IPv6 address, because I can easily imagine that as a part of a solution to the HTTPS issue. When every device has a permanent IPv6 address, and if every device is reachable through said IPv6 address, you could, in principle, also automate assigning each device a DNS record and set up SSL that way. It would be a pretty terrible solution that's way more complicated than just using a local address over HTTP, but it makes sense. I have no idea how to even begin translating maybe getting temporary unique addresses through DHCPv6 into a solution to the HTTPS issue.