They won't need to, there's plenty of space in the private range in IPv4 to put everything in my house on the net. IPv6 isn't going to make firewalls and private networks go away, people aren't going to just put everything directly on the Internet with a public IP just because they can just as no one gives every PC on their network now live IP's.
Are you brave enough to put your tea-making facilities in the DMZ? That's laying it on the line, man. Personally I think I would reverse proxy my teapot through nginx, I don't trust a TCP/IP stack embedded in a kitchen appliance.
I would like to take this opportunity to direct your attention towards the venerable http://nicecupofteaandasitdown.com which is both splendid and written by a hacker. I think you can tell when you get to the page with the venn diagram of biscuits.
The hypothetical Hot Beverages As A Service device that exists only in my head doesn't use NetBSD, it uses a custom standalone stack running on a PIC/AVR. So there.
Since we're talking about the Hyper Text Coffee Pot Control Protocol here, physical attributes of the teapot are irrelevant and thus outside of the scope of the RFC.
2.3.2 418 I'm a teapot
Any attempt to brew coffee with a teapot should result in the error
code "418 I'm a teapot". The resulting entity body MAY be short and
stout.
Because I'm apparently spending much of my day responding to HN stories, and because I wanted to see what happens when a page actually returns a 418 code:
Oh dear... Might have to build this now hmm? I'm not sure it counts if it's got a arduino in it and a cat 5 sticking out the back. The water is also an issue.
