At 14:29 01-12-2009, Andrew Sullivan wrote:
The IANA Considerations section is a little coy in the way it notes
that the document reserves .local. Moreover, the action is not merely
to IANA, but strictly to ICANN, and I worry about the procedural rules
for such an action. If there is a strong reason to put this document
on the standards track, the use of .local is surely it.
Quoting Section 3.1:
"Note that this use of the ".local." suffix falls under IETF/IANA
jurisdiction, not ICANN jurisdiction."
This draft mentions that the IETF has the authority to instruct IANA
to reserve pseudo-TLDs as required for protocol design
purposes. There is no action requested from IANA for ".local" in the
IANA Considerations section.
"In contrast, private uses of the DNS protocol on isolated private
networks are not governed by ICANN. Since this change is a change
to the core DNS protocol rules, it affects everyone, not just those
machines using the ICANN-governed Internet."
Is any other use of the DNS protocol governed by ICANN?
Could the authors please drop the reference to the ICANN-governed
Internet? I suggest dropping Section 3.1 as it is not the type of
content generally discussed in an Informational document.
In Section 6.3:
"iTunes users are accustomed to seeing a list of shared network music
libraries in the sidebar of the iTunes window. There is no "refresh"
button for the user to click because the list is expected to be
always accurate, always reflecting the currently available libraries,
without the user having to take any manual action to keep it that
way. When a new library becomes available it promptly appears in the
list, and when a library becomes unavailable it promptly disappears.
It is vitally important that this responsive user interface be
achieved without naive polling that would place an unreasonable
burden on the network."
The above is superfluous.
In Section 15:
"A host SHOULD defend its host name (FQDN) on all active interfaces on
which it is answering Multicast DNS queries."
What does that mean?
In Section 17:
"Set-top boxes (e.g. Apple's "Apple TV") connected to a television
can play music, photographic slide shows, and movies stored on the
user's desktop computer (e.g. an iMac running iTunes) -- but only
if that desktop computer is not asleep."
"Services like Apple's "Back to My Mac" allow users to access data
on their home computers from remote locations, using screen
sharing or file sharing -- but only if their computer at home
is not asleep."
Could the authors please remove such references?
Regards,
-sm
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf