On 07/29/2012 10:54 PM, Daniel Migault wrote:
Hi Stéphane,
Thank you for reading the drafts. My responses are added in the text.
On Mon, Jul 16, 2012 at 4:09 PM, Stephane Bortzmeyer <[email protected]
<mailto:[email protected]>> wrote:
On Tue, Jul 03, 2012 at 12:11:54PM +0200,
Daniel Migault <[email protected] <mailto:[email protected]>> wrote
a message of 155 lines which said:
> Please find two Naming Architectures we would like to discuss at
Vancouver:
I won't be in sunny British Columbia but I've read the drafts and I
have a philosophical question. You did not say clearly if the
delegated domain must be under an ISP's domain. If yes, it ties the
user to the ISP ("I've switched ISPs, use
<http://fridge.migault.free.fr/> and no longer
<http://fridge.migault.orange.fr/>"). If no, the ISP won't be able to
update the DNS delegation. IMHO, it would be a good idea to have a
high-level discussion of the service provided to the user, before
getting into protocol details.
The delegated domain name is under the ISP domain. If that is not clear, we
will clarify it in the next version.
Shouldn't we consider the case of over the top providers too? That is, suppose
that, oh say, google wanted to get into the DNS naming business. There's nothing
really stopping them or anybody else, nor do I think we should limit them.
I'm a little confused by the section of why DHCP is needed here between ISP
and CPE. With bind, for example, it's very easy to set up an authoritative
server
to be a slave for zone transfers. That is, you can set up CPE to be the master
of
zone information and do zone transfers to an authoritative server with lots of
bandwidth, etc. This has the property that it decouples the locality requirement
with DHCP, so yahoo-names works too in addition to $ISP. And of course, it need
not involve CPE at all because naming could all be done as a web UI to their
DNS servers.
Mike
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
