On Tue, Oct 26, 2010 at 07:58:25AM -0700,
The IESG <iesg-secretary(_at_)ietf(_dot_)org> wrote
a message of 31 lines which said:
The IESG has received a request from an individual submitter to consider
the following document:
- 'Multicast DNS'
<draft-cheshire-dnsext-multicastdns-12.txt> as a Proposed Standard
There are several issues at stake:
1) Proposed Standard is certainly not the appropriate status. There
was never an IETF consensus about a solution for "link-local"
DNS. There were two competing proposals (the first one, RFC 4795, is
not even mentioned in draft-cheshire-dnsext-multicastdns, which I find
extremely petty). There is zero reason to give a special treatment to
"multicast DNS" (a bad name, since it is not the DNS at all). A
reasonable status would be Experimental since it was the one used for
SPF (now RFC 4408) which, like "multicast DNS", was widely implemented
when published as a RFC (as of today, 20 % of domains in .FR have a
SPF record).
2) I let ICANN state if they agree or not about the hijacking of a TLD
in appendix G. But the mention of RFC 2026 is dangerous. RFC 2026 says
"IANA has agreed to the four top level domain name reservations" while
nothing indicate such an agreement here.
3) The advice in Appendix H is extremely bad and must be removed:
suggesting people to use dummy TLD is quite dangerous since these TLD
are not reserved in any way and could be delegated by ICANN at any
moment. The proper solution for local domains is to use a subdomain of
a registered domain (local.example.org, for instance).
signature.asc
Description: Digital signature
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf