In message <[email protected]> Wouter Cloetens writes: > 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
Thank you for pointing these out. I will take a look at them. > > 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. I think you missed the point. This is not a security issue. The homenet user that wants foo.com needs to go to a domain registrar. The provider can only give out foo.site.provider.com but if this is for true home use and not business use, then that should be fine. The point is to be able to reach the home without typing in an IPv6 address. The same type of user happily accepts an email address of the form <namestring>@provider.com where namestring often has to contain numbers to keep it unique because all first names and most last names are already taken at the provider. It would be perfectly fine for the provider to offer <namestring>.site.provider.com as a domain delegation if namestring has already been assigned to the home as an account ID and email address. If the user want a domain name in a TLD, they need a domain name registrar. > bfn, Wouter > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
