Category: Standards Track                           Apple Computer, Inc.
and no new operation codes, response codes, or resource record types.
other search domain that might appear in the DNS search list.
to have a mechanism in place to handle them when they happen.
machines by copying it onto a floppy disk or similar removable media.
forced to rename their machines have never been an issue.
silently discard any response packets where the IP TTL is not 255.
APIs to not provide any indication of the IP TTL on received packets.
Likewise, any DNS query for a name ending with "0.8.e.f.ip6.arpa."
MUST be sent to the IPv6 mDNS link-local multicast address FF02::FB.
even being aware what a multicast address is.
protocol has met the user's needs in this case.
Question Section of a Multicast DNS Query.
cached record expires and has to be removed from the list.
the Known Answer records have been sent.
also waiting to receive the same answer record.
are deployed (see Section 16. "Multicast DNS and Power Management").
only that the information in the response is true and accurate.
a simple client that does not fully implement all of Multicast DNS.
packet's source IP address and port.
MUST be randomly delayed in the range 20-120ms, as described above.
move to the second step.
analogous to the Update section of a DNS Update packet [RFC 2136].
to its query, and concludes that it may not use the desired name.
data first is deemed lexicographically earlier).
records to fit in a single packet, multiple packets may be used.
the answer section of the DNS Response.
The most significant bit of the rrclass is the mDNS "cache flush"
loser, and the loser must cease using the name, and reconfigure.
"Probing and Announcing on Startup".
private ".local.", "254.169.in-addr.arpa." and "0.8.e.f.ip6.arpa."
Abstract Services using DNS" [DNS-SD].
avoids taking external dependencies on other protocols.
the impact of such stale data.
cache entry to be promptly deleted.
Whenever a host has a resource record with potentially new data (e.g.
immediately flushed from the cache.
packets. Only cache records more than one second old will be flushed.
records in a response packet sent via unicast to any host.
interface should immediately be flushed.
record cache should be flushed.
rdata can inform the cache and have that data flushed.
specific "magic packet" required to wake the device up.
its deleted resource records, and re-announces them to the network.
device, and proceeds to connect to it.
is described in another document [not yet published].
letters, digits and hyphens, with no spaces or other punctuation.
to accommodate old buggy legacy implementations.
from UTF-8 (US-ASCII being considered a compatible subset of UTF-8).
to canonical UTF-8 before being placed in any Multicast DNS packet.
it means that the querying host has no additional Known Answers.
port numbers is important to allow this flexibility.
a different UDP port eliminates this particular problem.
numbered UDP port eliminates this particular problem.
Copyright (C) The Internet Society 20th December 2002.