[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [patch #9523] MDNS responder should reply after a random ti

From: Erik Ekman
Subject: [lwip-devel] [patch #9523] MDNS responder should reply after a random timeout
Date: Mon, 8 Jan 2018 16:13:50 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36

Follow-up Comment #14, patch #9523 (project lwip):

As I understand it, there is no concept of order in MDNS.
The responder is free to merge multiple different multicast (and non-legacy
unicast) into a single response packet sent as multicast.

This reduces the load on the network, as well as makes multiple packet known
address suppression easy. When a service is removed, all outgoing queued
replies for it should be cleared. The legacy question would have to be
temporarily copied (just the RR info: domain, class and type)

My suggestion is to have a 50ms or so tick and wait one or two ticks for
instance before sending a certain reply. That should be random enough since
different devices will not have a synchronized periodic timer. We could also
use this tick to make sure to not send an answer again if we sent it multicast
during the last second. (RFC 6762, section 6) as well as for driving the
collision probing logic.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]