Section 4.4 DNS Issues
This sections appears to be a real cop out.
It is perfectly natural for clients to want to make queries and
have these addresses returned from the DNS.
The problem is that there is no co-ordinating authority for
D.F.IP6.ARPA and if we let queries be made the servers for
F.IP6.ARPA (or IP6.ARPA) will be swapped. Similarly we can
force public servers for zones under C.F.IP6.ARPA. I propose
that we actually allow these addresses to be returned but
that (caching) nameservers be automatically configured to
return Name Error for queries under D.F.IP6.ARPA and (maybe)
C.F.IP6.ARPA and that *explicit* configuration be required
to get a different response.
e.g.
that the server behaves as if the following zones are loaded.
C.F.IP6.ARPA. 3600 IN SOA C.F.IP6.ARPA. RFCXXXX.C.F.IP6.ARPA. (
1 7200 3600 604800 3600 )
C.F.IP6.ARPA. 3600 IN NS C.F.IP6.ARPA.
C.F.IP6.ARPA. 3600 IN TXT Automatically generated as per RFCXXXX
D.F.IP6.ARPA. 3600 IN SOA D.F.IP6.ARPA. RFCXXXX.D.F.IP6.ARPA. (
1 7200 3600 604800 3600 )
D.F.IP6.ARPA. 3600 IN NS D.F.IP6.ARPA.
D.F.IP6.ARPA. 3600 IN TXT Automatically generated as per RFCXXXX
Note 1: the above zones can be used by existing for servers to
achieve the same behaviour.
Note 2: There are no addresses associated with the nameservers,
sites may want to assign a address (e.g. ::1).
Note 3: RFCXXXX.[CD].F.IP6.ARPA above could be replace by
a local contact address.
Co-operating sites are would secondary the relevent local reverse
zones (X.X.X.X.X.X.X.X.X.X.[CD].F.IP6.ARPA.) or manage their own
[CD].F.IP6.ARPA zones.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
