Bonjour Conformance Test WARNING i… | Apple Developer Forums
Bonjour Conformance Test WARNING in Multicast DNS SHARED REPLY TIMING resolution App & System Services Networking Network AirPrint Bonjour You’re now watching this thread. If you’ve opted in to email or web notifications, you’ll be notified when there’s activity. Click again to stop watching or visit your profile to manage watched threads and notifications. You’ve stopped watching this thread and will no longer receive emails or web notifications when there’s activity.
Click again to start watching. danibj OP Created Mar ’26 Replies 9 Boosts 0 Views 1.3k Participants 2 Hello and Good day! We are conducting Bonjour Conformance Test (BCT) for Printer device. BCT result is PASSED but with warning in Multicast DNS, specifically, WARNING: SHARED REPLY TIMING - UNIFORM RANDOM REPLY TIME DISTRIBUTION Other Shared Reply Timing is passed: PASSED: MULTIPLE QUESTIONS - SHARED REPLY TIMING - UNIFORM RANDOM REPLY TIME DISTRIBUTION Environment: BCT Tool Version: 1.5.4 (15400) MacOS Sequioa 15.5 DUT Firmware : Linux Debian 9 Apple mDNSResponder 1790.80.10 Service types: _ipps._tcp, _uscans._tcp, _ipp._tcp, _uscan._tcp Router : NEC AtermWR8370N Setup: 1-to-1 [Mac->Router<-DUT connection] Based on debug.log, this is where WARNING occurs: NOTICE 2026-03-04 10:51:06.870187+0900 _shared_reply_timing 04103: Shared reply response times: min = 26ms, max = 114ms, avg = 65.50ms WARNING 2026-03-04 10:51:06.870361+0900 _shared_reply_timing 04136: 50 percent of the replies within the correct range fell in the interval 20ms and 46ms (should be close to 25%).
PASSED (SHARED REPLY TIMING) In the same debug.log for MULTIPLE QUESTIONS - SHARED REPLY TIMING is PASSED: NOTICE 2026-03-04 10:52:29.912334+0900 _shared_reply_timing 04103: Shared reply response times: min = 22ms, max = 112ms, avg = 78.00ms DEBUG_2 2026-03-04 10:52:29.912849+0900 recv_packet 01997: received packet (558 bytes) PASSED (MULTIPLE QUESTIONS - SHARED REPLY TIMING) [Details] Looking at Bonjour_Conformance_Guideline.pdf https://download.developer.apple.com/Documentation/Bonjour_Conformance_Test_Guideline/Bonjour_Conformance_Guideline.pdf there were some differences: In 1.6.2 Expected Result: Test Result File of Test that All Tests Passed, this is not displayed: PASSED: SHARED REPLY TIMING - UNIFORM RANDOM REPLY TIME DISTRIBUTION And in II.8 Shared Reply Timing: (Ideally, 25% of the answers should fall in each 21ms quadrant of the range 20ms - 125ms.) and comparing to the debug.log, there was a discrepancy of the interval, because 20ms and 46ms is 26ms interval.
From RFC6762 6. Responding, Ideal range is from 20ms-120ms Because of this, please advise on the questions below: I would like to know on the possible cause and resolution for these WARNINGS. And since in current BCT result, (Test result integrity signature is generated), I would like to know if this is acceptable for BCT certification. Thank you. Answered by DTS Engineer in 880360022 Thank you for providing the code.
I modify a bit to be able to build in our DUT FYI, my original code has some logic flaws that I eventually sorted out with a bit more testing and experimentation. The underlying math here is that the BCT binning test is equivalent to the combined probability of rolling 10 3-sided dice and having either or both of these occur: The same number appear on 4 or more dice -> ~31% At least one number not appearing at all ->21% ...and the combined probability of those two events works out to about ~40%.
I suspect/assume that you're having test runs that OCCASIONALLY succeed, but the inherent failure rate might also be being skewed by other details of your implementation. I've filed a bug on this already (r.172771068), but I'd appreciate your filing your own bug and posting the bug number back here. I would like to confirm if the result of SHARED REPLY TIMING with Warning is not an issue and can still result to BCT certification to Pass.
This warning is not an issue and should not prevent certification. __ Kevin Elliott DTS Engineer, CoreOS/Hardware Replies 9 Boosts 0 Views 1.3k Participants 2 DTS Engineer OP Apple Mar ’26 [Details] Looking at Bonjour_Conformance_Guideline.pdf ... there were some differences: So, for future reference, the Bonjour Conformance Guideline document is primarily focused on details of how the test needs to be run, NOT what the test actual "does" or how to interpret it's results.
The details of the test process itself are found in: Documentation/Conformance Test Outline.txt ...inside the disk image of the conformance test itself. For the share reply timing test, that document says: II.8 Shared Reply Timing The test tool issues a query for a shared (service PTR) record, and records how quickly the device answers. This test is repeated 10 times. The response times must form a uniform random distribution in the range 20ms - 125ms.
Any results in the range 10ms - 20ms, or 125ms - 750ms are warnings. Any results less than 10ms or more than 750ms are failures. For purposes of determining a uniform random distribution, only the answers that fall into the correct time range (20ms - 125ms) are considered. It is a warning if less than 5% or more than 45% of these answers fall in any one quadrant of the range. (Ideally, 25% of the answers should fall in each 21ms quadrant of the range 20ms - 125ms.) If all 100 replies lie within one tenth of the correct range, this is a failure. (To accommodate low-cost devices with low clock precision, warning-generating replies outside of the 20ms - 125ms range automatically prevent random distribution failures). ...
For the details, please refer to "RFC6762 6. Responding". Note the RFC reference at the end. All of the test in the BCT correspond to requirements defined by the underlying RFC specs, so the test outline also refers back to the controlling RFC. In term of this particular test section 6 of RFC6762 has the full rational, but the short summary is that spec expects a small random delay between response to reduce the probability of ethernet collision.
Your particular failure was caused by exactly what the warning described: "50 percent of the replies within the correct range fell in the interval 20ms and 46ms" That leads to here: (Ideally, 25% of the answers should fall in each 21ms quadrant of the range 20ms - 125ms.) and comparing to the debug.log, there was a discrepancy of the interval, because 20ms and 46ms is 26ms interval. The "21ms quadrant" is a typo (r.172415434), as the correct interval for "20ms - 125ms" is "26ms": (125ms - 20ms) -> 105ms 105/4 -> 26.25 -> 26ms In terms of the RFC: From RFC6762 6.
Responding, Ideal range is from 20ms-120ms I believe the BCT is intentionally setting it's ideal range slightly above the RFC ideal so that issues like network latency and other "noise" don't generate invalid failures. Putting that in more concrete terms, it's very difficult (basically impossible) for a device to delay for 119ms (a valid delay) while GUARANTEEING that the reply will be received by 120ms. A packet received at 123ms has no meaningful impact on the large bonjour protocol (since the valid range is obviously MUCH larger) so adding a small "pad" to the range reduce testing issues without creating any other impact.
I would like to know on the possible cause See above. and resolution for these WARNINGS. I'd start by looking at the actual reply times, as the real concern here is fixed or consistent delays, not the distribution, as fixed or consistently repeating intervals could actually INCREASE the collision rate. At that point, it's then a matter of investigating and correcting whatever is causing your replay delay to be so short.
And since in current BCT result, (Test result integrity signature is generated), I would like to know if this is acceptable for BCT certification. That's not a decision I'm directly involved with but, no, I wouldn't expect this to be an issue, assuming there isn't any obvious issue (like repeating patterns) in your reply delay. __ Kevin
The rest of this page is on the live site.