Groovy. A generally clear and well organized document. A few nits:
There's a typo (missing 192) in the example in section 3.2:
$ORIGIN 192.IN-ADDR.ARPA.
...
2.0.192.IN-ADDR.ARPA. IN DNAME EMPTY.AS112.ARPA.
...
/|\
| missing!
In section 8.2, shouldn't the SOA MNAME for AS112.ARPA be something like
A.IANA-SERVERS.NET rather than BLACKHOLE.AS112.ARPA ? The latter makes
sense for the child zone EMPTY.AS112.ARPA.
Section A.1 is a bit confused about whether it is talking about the
future, present, or past. Should it say that the hostnames used in the
actual survey were not the ones listed in the description?
I think the appendix should note the caveat about glibc's logging, and
perhaps also the effect on mail servers, even though the latter isn't
relevant to AS112. I am worried that appendix A will be used as an
authoritative reference for DNAME support in contexts other than AS112, so
it should mention the known interop difficulties even though the general
conclusion is positive.
https://www.ietf.org/mail-archive/web/dnsop/current/msg10638.html
I imagine that there are sites which make much higher traffic use of RFC
1918 space than us, and glibc's logging could cause problems for them.
Tony.
--
f.anthony.n.finch <[email protected]> http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
