-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Reverse DNS is often quite different in IPv6 compared to IPv4. In IPv6 end users likely get a /48, or perhaps a /64 rather than a small number of IPv4 addresses.
The reverse delegation either needs be a delegation to some device on the end user premise, or the end user needs to have some (presumably secure) way of updating the zone at their upstream (could be dynamic DNS, but doesn't need to be). I would recommend leaving IPv6 out of the document, or perhaps note that it is a different problem. Andrew Sullivan wrote: > ISSUE > ===== > > The document talks about IN-ADDR, which is IPv4 only, but is really > about reverse mapping. > > PROPOSAL > ======== > > The text makes explicit that any IN-ADDR references apply equally to > all relevant functionality in other IP versions. If this is not > clear in any part of the document, though, it will undermine the > effectiveness of the document, so additional objections of this kind > are solicited. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFPSiXMsfZxBO4kbQRAtQkAJ9wgW302u7UNI79vCz9rPQrcK9TGQCglSUh TniTKgqbO4XEZrC3G8+hQHg= =0wa/ -----END PGP SIGNATURE----- . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
