Michael Richardson wrote:
see inline
"Michael" == Michael Thomas <[email protected]> writes:
>> Homenet and code point of view, the important requirement would
>> actually be:
>> CER MUST be able to be authoritative name server for
>> at least one reverse (ip6.arpa) zone, and at least one
>> forward zone.
>> CER SHOULD support zone transfers to a secondary server,
>> which SHOULD be configurable manually, and SHOULD be
>> configurable by some TBD DHCPv6 option.
Michael> I'm confused, is the DHCPv6 part connected in any way to the zone
Michael> transfer part? I thought the DHCP part that Simon was
Michael> talking about
What prefix under ip6.arpa to populate depends upon the DHCPv6 PD
value(s). If we are a listed master, then we may need to do something
in DHCP to let the ISP know where our zone is (and if we have one).
The reverse map. Yes, obviously only the address space's parent owner
can delegate to us. But that is only completely true for the reverse zone.
If we are an unlisted master, then we may need to configure ACLs for the
listed masters to zone transfer from us, so we need DHCP to tell us.
If we are going to do DNS update, then we need in DHCP to find out where
to update to, and to establish keying material.
Just for the reverse zone. The forward zone(s) may have nothing to do with
an ISP, and we shouldn't expect any special relationship (this was my big
problem
with the Orange draft). I think it's just as likely if not more likely that
non-isp's
will perform this name service for homes -- think of the data mining
possibilities for
our naming being the "product".
Mike
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
