Lines Matching refs:multicast
130 start sending DNS queries to a multicast address, and how a
138 multicast traffic generated by hosts making conventional use of
228 to the mDNS multicast address (224.0.0.251 or its IPv6 equivalent
249 the mDNS multicast address, if no other conventional DNS server is
253 Internet. When resolving global names via local multicast, it is even
256 multicast is a contentious issue, and this document does not discuss
258 names using DNS packets sent to a multicast address.
443 address (including the 224.0.0.251 link-local multicast address)
454 * All responses sent to the link-local multicast address 224.0.0.251
482 addressed to the link-local multicast address 224.0.0.251, from a
486 responder SHOULD elect to respond by multicast anyway, since it can
497 be sent to the mDNS multicast address 224.0.0.251. Since names under
505 mDNS link-local multicast address FF02::FB.
531 accumulating multiple responses made by multicast-aware DNS clients,
545 multicast address is. This change can typically be implemented with
703 Sending Multicast DNS responses via multicast has the benefit that
720 multicast responses may impose an unreasonable burden on the network.
726 responses instead of the usual multicast responses. These questions
728 distinguish them from the more usual questions requesting multicast
740 Reverting to multicast responses as soon as possible is important
741 because of the benefits that multicast responses provide (see
751 to the querier. If the responder has not multicast that record
760 instead multicast the response so as to keep all the peer caches up
764 may also send a multicast announcement too if the time since the last
765 multicast announcement of that record is more than a quarter of its
770 as multicast replies, including the cache flush bit (see Section
808 via link-local multicast would not reach a Querier outside the local
1035 multicast address (or its IPv6 equivalent FF02::FB). Operating in a
1049 Sending all responses by multicast also facilitates opportunistic
1054 (except in the one special case of answering probe queries) multicast
1056 since the last time that record was multicast on that particular
1064 responding via multicast to a probe, a Multicast DNS Responder is
1067 multicast on that interface.
1131 record in any multicast response recently, it SHOULD schedule the
1132 record to be sent via multicast as well, to facilitate passive
1134 since the record was last sent via multicast is less than one quarter
1139 listening for multicast queries on 224.0.0.251:5353 MUST be prepared
1232 from more than one other host. Because of the mDNS multicast rate
1236 wait before replying via multicast. At the present time, this
1255 network with a continuous stream of multicast traffic. For very
1643 record to be announced via multicast. Clients receiving the record
1645 record sooner than A expects. By sending its own multicast response
1850 A host observes the multicast queries issued by the other hosts on
1852 using multicast is that it allows all hosts to see the responses (or
1862 expected to be given as an answer in a multicast response, but no
1866 After seeing two or more of these queries, and seeing no multicast
1872 cause a lot of unnecessary multicast traffic. If host A sends
1873 multicast queries that remain unanswered, then there is no reason
1921 multicast addresses; therefore they identify not a single host but a
2083 In most operating systems, incoming multicast packets can be
2095 able to bind to UDP port 5353 and receive incoming multicast packets
2330 appropriate. For link-local multicast packets on today's networks,
2340 fit in a single MTU-sized multicast response packet, a Multicast DNS
2406 In multicast query messages, the Query ID SHOULD be set to zero on
2409 In multicast responses, including gratuitous multicast responses, the
2414 particular (unicast or multicast) query, the Query ID MUST match the
2426 In both multicast query and multicast response messages, MUST be zero
2427 (only standard queries are currently supported over multicast, unless
2460 In multicast response messages, the TC bit MUST be zero on
2471 In both multicast query and multicast response messages, the
2478 In both multicast query and multicast response messages, the
2521 In both multicast query and multicast response messages, the Response
2590 common, and redirecting link-local multicast DNS packets to a
2626 * uses multicast
2674 Some people have argued that sending responses via multicast is
2675 inefficient on the network. In fact using multicast responses results
2676 in a net lowering of overall multicast traffic, for a variety of
2679 * One multicast response can update the cache on all machines on the
2682 transmit that multicast query on the network at all.
2690 * When a host sees a multicast query, but does not see the corres-
2691 ponding multicast response, it can use this information to promptly
2693 user-interface quality and responsiveness without multicast
2703 sent. The option of multicast responses allows clients with limited
2705 addresses, to choose to fail-over to a single multicast response in
2708 * In the case of overlayed subnets, multicast responses allow a
2713 * Link-local multicast transcends virtually every conceivable network
2717 addressed to a link-local multicast destination address will still
2753 Some discovery protocols use a range of multicast addresses, and
2755 sought. Queries are sent via multicast to the address as indicated by
2757 unicast. Particularly in IPv6, where multicast addresses are
2763 host may have to join a large number of multicast groups. This can
2765 supports a limited number of multicast addresses efficiently. When
2769 multicast address range in the first place.
2772 hash to the same multicast address.
2813 multicast address (during network outages which disrupt communication
2849 IANA has allocated the IPv4 link-local multicast address 224.0.0.251
2852 IANA has allocated the IPv6 multicast address set FF0X::FB for the