I hope that <device>.example.com is not the way we're headed. Wasn't that what http://, etc... were going to solve? We already have a wap:// for mobile devices (yes, it's pathetic, but maybe that just means we need a new service type).