On 10/22/2012 07:26 AM, Tim Chown wrote:
On 19 Oct 2012, at 17:55, Michael Thomas <[email protected]> wrote:
If you get an ISP's name couldn't you always with or without their cooperation
generate names of the form host.<uniquestring>.isp.net? Where <uniquestring>
is either statistically unique (cf ULA's), or is human-significant and unique
(eg,
host.casasanchez.customers.isp.net).
I would assume here that the name the ISP delegates includes such a unique
string, e.g. cust1234.someisp.net. Maybe for an extra fee they'll let you pick
a unique string to replace 'cust1234'. Personally (and I note at IETF85 we
found that half the homenet attendees had 110+ domains each!)
That's assuming that the ISP knows anything about me camping on
their namespace at all. If I run a DNS locally -- say in my home router --
I could use their name space regardless of whether they sanction it
or not. It might only work in my home, of course (ie, users of my
DNS server that is camping on somebody else's namespace).
I believe it's important to allow the homenet to use an ISP-independent domain
name as simply as possible.
Right, and is the reason that the DHCP linkage of the Orange draft
is problematic.
Mike
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
