On 08/08/12 20:48, Curtis Villamizar wrote:
One solution, the one you are describing is where the CPE runs DHCP
only and uses the dyndns protocol to make addresses available
globally.
Another solution is have the CPE run both DHCP and bind (or equiv) and
run dyndns. The provider could delegate and secondary a subdomain of
the provider with no need to contact a domain registry.
Yes, that is exactly the 13 months old solution, described in these drafts:
http://www.ietf.org/id/draft-mglt-homenet-naming-delegation-00.txt
http://www.ietf.org/id/draft-mglt-homenet-front-end-naming-delegation-00.txt
When a domain registrar is needed is only when the homenet needs or
wants (maybe for ego reasons) a domain residing in a TLD (such as .com
or .org) and would not accept a subdomain from the provider. For
example the homenet user wants foo.com and would not accept something
of the form foo.site.provider.com, which would be less permanet (the
delegation is lost if switching providers).
For security reasons documented in one of the drafts above, it should be
disabled by default. A user-defined configuration could open the DNS
port to the world, and allow additional domains.
bfn, Wouter
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
