On 31/07/12 20:32, Curtis Villamizar wrote:
I'm thinking I'd much more like to see a specific recommendation that HOMENET 
gateways implement a site-managed reverse tree, optionally augmented with a 
zero-configuration method for generating content explicitly managed by a 
knowledgeable home network administrator.

For example, after I install a fresh HOMENET gateway in my new house, I expect 
the following things just to happen correctly without any forethought:

1. The integrated DNS content server should have authority for all of the 
ip6.arpa corresponding to the IPv6 prefixes delegated by its service provider;

2. The integrated DNS resolving server should answer [on the local network 
only] for the locally generated ULA prefixes required by RFC 6106.

3. Queries for PTR records in zones for which it's authoritative should always 
produce a synthesized answer if no explicitly configured records are stored in 
the content server.

[...]

I think you could add to the above that the provider should offer to
delegate a forward zone and a reverse zone via DHCP extension and
offer to provide DNS secondary for those zones.  Note that
draft-lemon-dhc-dns-pd doesn't go that far (offering a forward zone
name to use), but it would be a useful addition.

Covered in:
 http://www.ietf.org/id/draft-mglt-homenet-naming-delegation-00.txt

This also covers security considerations.

It would be nice if the customer router could request that the
provider secondary also pick up a zone allocated to the site by a
registrar.  The provider router can verify this by looking up the NS
records for that zone and determining that the A or AAAA for at least
one of the existing nameservers falls with the static address
allocation of the site.  This would be for advanced users and the
advanced user (or a sufficiently advanced DHCP/nameserver coupling)
could then update the list of NS records adding the provider
secondary.

Covered in a completely different way in:

http://www.ietf.org/id/draft-mglt-homenet-front-end-naming-delegation-00.txt
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to