Ummm think about it. Sure you'll want to control the nanites remotely but that doesn't mean you need to communicate with each one of them directly.
Communicate with a few controller nanites, that manage the others, and have them establish a private network between themselves. You can tell controller nanite #5/10 to have nanite #324235236523 to do some junk.
Besides, think of the routing chaos if the global routers had to manage separate connections going to each one of the nanites. Hierarchy is your friend.
Hrmph. Anyone ever hear of a private network? IPv6 just like IPv4 provides for private networks that dont exactly need to have a public address.
Nanothingies can easily go on the super large private networks provided for by IPv6. If anything needs to be public, have the controller on a public IP address. I can't really think of a situation I might want to telnet to specific nanothingie #233523523 from halfway across the globe.
Same thing with toasters btw. If i actually did have my toaster network-enabled, i would probably have it on my PRIVATE network in my house. I could then toast some bread at home from my car by connecting to some external controller that interfaced with my toaster through the private network. My toaster doesn't necessarily need to serve web pages directly now does it?
Just a thought...
Slashdot Mirror
http://www.iana.org
Of course, you still need a way to get to your DNS server. :) Perhaps DHCP can help...
Looks like DNS is gonna become just that more important.
Ummm think about it. Sure you'll want to control the nanites remotely but that doesn't mean you need to communicate with each one of them directly.
Communicate with a few controller nanites, that manage the others, and have them establish a private network between themselves. You can tell controller nanite #5/10 to have nanite #324235236523 to do some junk.
Besides, think of the routing chaos if the global routers had to manage separate connections going to each one of the nanites. Hierarchy is your friend.
Hrmph. Anyone ever hear of a private network? IPv6 just like IPv4 provides for private networks that dont exactly need to have a public address. Nanothingies can easily go on the super large private networks provided for by IPv6. If anything needs to be public, have the controller on a public IP address. I can't really think of a situation I might want to telnet to specific nanothingie #233523523 from halfway across the globe. Same thing with toasters btw. If i actually did have my toaster network-enabled, i would probably have it on my PRIVATE network in my house. I could then toast some bread at home from my car by connecting to some external controller that interfaced with my toaster through the private network. My toaster doesn't necessarily need to serve web pages directly now does it? Just a thought...