[pkgsrc/trunk]: pkgsrc/net/py-zeroconf py-zeroconf: updated to 0.36.2

[adam <adam%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/914cca60e419
branches:  trunk
changeset: 458002:914cca60e419
user:      adam <adam%pkgsrc.org@localhost>
date:      Mon Sep 06 11:25:22 2021 +0000

description:
py-zeroconf: updated to 0.36.2

0.36.2

Include NSEC records for non-existent types when responding with addresses
0.36.1

Skip goodbye packets for addresses when there is another service registered with the same name

If a ServiceInfo that used the same server name as another ServiceInfo was unregistered, goodbye packets would be sent for the addresses and would cause the other service to be seen as offline.

Fixed equality and hash for dns records with the unique bit

These records should have the same hash and equality since the unique bit (cache flush bit) is not considered when adding or removing the records from the cache.

0.36.0

Technically backwards incompatible:

Fill incomplete IPv6 tuples to avoid WinError on windows

0.35.1

Only reschedule types if the send next time changes

When the PTR response was seen again, the timer was being canceled and rescheduled even if the timer was for the same time. While this did not cause any breakage, it is quite inefficient.

Cache DNS record and question hashes

The hash was being recalculated every time the object was being used in a set or dict. Since the hashes are effectively immutable, we only calculate them once now.

0.35.0

Reduced chance of accidental synchronization of ServiceInfo requests
Sort aggregated responses to increase chance of name compression
Technically backwards incompatible:

Send unicast replies on the same socket the query was received

When replying to a QU question, we do not know if the sending host is reachable from all of the sending sockets. We now avoid this problem by replying via the receiving socket. This was the existing 
behavior when InterfaceChoice.Default is set.

This change extends the unicast relay behavior to used with InterfaceChoice.Default to apply when InterfaceChoice.All or interfaces are explicitly passed when instantiating a Zeroconf instance.

0.34.3

Fix sending immediate multicast responses
0.34.2

Coalesce aggregated multicast answers

When the random delay is shorter than the last scheduled response, answers are now added to the same outgoing time group.

This reduces traffic when we already know we will be sending a group of answers inside the random delay window described in datatracker.ietf.org/doc/html/rfc6762#section-6.3

Ensure ServiceInfo requests can be answered inside the default timeout with network protection

Adjust the time windows to ensure responses that have triggered the protection against against excessive packet flooding due to software bugs or malicious attack described in RFC6762 section 6 can 
respond in under 1350ms to ensure ServiceInfo can ask two questions within the default timeout of 3000ms

0.34.1

Ensure multicast aggregation sends responses within 620ms

Responses that trigger the protection against against excessive packet flooding due to software bugs or malicious attack described in RFC6762 section 6 could cause the multicast aggregation response 
to be delayed longer than 620ms (The maximum random delay of 120ms and 500ms additional for aggregation).

Only responses that trigger the protection are delayed longer than 620ms

0.34.0

Implemented Multicast Response Aggregation

Responses are now aggregated when possible per rules in RFC6762 section 6.4

Responses that trigger the protection against against excessive packet flooding due to software bugs or malicious attack described in RFC6762 section 6 are delayed instead of discarding as it was 
causing responders that implement Passive Observation Of Failures (POOF) to evict the records.

Probe responses are now always sent immediately as there were cases where they would fail to be answered in time to defend a name.

0.33.4

Ensure zeroconf can be loaded when the system disables IPv6

diffstat:

 net/py-zeroconf/Makefile |   4 ++--
 net/py-zeroconf/distinfo |  10 +++++-----
 2 files changed, 7 insertions(+), 7 deletions(-)

diffs (27 lines):

diff -r 58684daac81d -r 914cca60e419 net/py-zeroconf/Makefile
--- a/net/py-zeroconf/Makefile  Mon Sep 06 10:25:40 2021 +0000
+++ b/net/py-zeroconf/Makefile  Mon Sep 06 11:25:22 2021 +0000
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.22 2021/08/06 12:42:34 adam Exp $
+# $NetBSD: Makefile,v 1.23 2021/09/06 11:25:22 adam Exp $
 
-DISTNAME=      zeroconf-0.33.3
+DISTNAME=      zeroconf-0.36.2
 PKGNAME=       ${PYPKGPREFIX}-${DISTNAME}
 CATEGORIES=    net python
 MASTER_SITES=  ${MASTER_SITE_PYPI:=z/zeroconf/}
diff -r 58684daac81d -r 914cca60e419 net/py-zeroconf/distinfo
--- a/net/py-zeroconf/distinfo  Mon Sep 06 10:25:40 2021 +0000
+++ b/net/py-zeroconf/distinfo  Mon Sep 06 11:25:22 2021 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.22 2021/08/06 12:42:34 adam Exp $
+$NetBSD: distinfo,v 1.23 2021/09/06 11:25:22 adam Exp $
 
-SHA1 (zeroconf-0.33.3.tar.gz) = 1453e37ce56aaca6761258c50e92c1f04b1172f9
-RMD160 (zeroconf-0.33.3.tar.gz) = b2aa27ed8ecf9a345cfb83f359649f33c1b3a7e9
-SHA512 (zeroconf-0.33.3.tar.gz) = b3ba9324c66e3af1dc8765a6f3809ee35119ac7abcb73018ac05a55189dd560b03d7d13f020d1d9f54533598c7b179fea1c5e921dfd331a964162a5ca5b5c710
-Size (zeroconf-0.33.3.tar.gz) = 95953 bytes
+SHA1 (zeroconf-0.36.2.tar.gz) = 617fdf4de55d27b93f0138b4f4aac6b43f5b872b
+RMD160 (zeroconf-0.36.2.tar.gz) = 56b89e8e28f3aca53f5e6c16e496b5ed3e25f602
+SHA512 (zeroconf-0.36.2.tar.gz) = a2aef5942f61652bde7299a373fe69b935ac734719e592dd024d839a3a5770e6271933971e55317d07e82012ac85ecb18b1d92f64244373be8e240341bafe77f
+Size (zeroconf-0.36.2.tar.gz) = 102578 bytes