Brian E Carpenter

BTW that was Python 3. If you prefer Python 2 see below. And it's the same on Windows or Linux. import cbor import binascii raw1=binascii.a2b_hex('d81858e95900e686782650545220202a205a65726f636f6e662e5f687474702e5f7463702e646e732d73642e6f72672e82781853525620302030203830207a65726f636f6e662e6f72672e70412035302e3139372e3133382e31303178185458542022747874766572733d31222022706174683d2f22782b50545220202a204d756c74696361737420444e532e5f687474702e5f7463702e646e732d73642e6f72672e82781c53525620302030203830206d756c746963617374646e732e6f72672e70412035302e3139372e3133382e31303178185458542022747874766572733d31222022706174683d2f22') print cbor.loads(raw1) raw2=binascii.a2b_hex('d81858e95900e686782650545220202a205a65726f636f6e662e5f687474702e5f7463702e646e732d73642e6f72672e82781853525620302030203830207a65726f636f6e662e6f72672e70412035302e3139372e3133382e31303178185458542022747874766572733d31222022706174683d2f22782b50545220202a204d756c74696361737420444e532e5f687474702e5f7463702e646e732d73642e6f72672e82781c53525620302030203830206d756c746963617374646e732e6f72672e70412035302e3139372e3133382e31303178185458542022747874766572733d312220') print cbor.loads(raw2)...

Very likely this is caused by issue #1

There's a new draft at [https://www.ietf.org/archive/id/draft-carpenter-6man-rfc6874bis-03.html](https://www.ietf.org/archive/id/draft-carpenter-6man-rfc6874bis-03.html).

The IETF 6MAN WG has just formally adopted our document [draft-ietf-6man-rfc6874bis-00](https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-00.html). All we need is a developer who understands all the places where URLs are parsed (there are several) and...

New version of the draft published: [https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-01.html](https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-01.html). Among other things it adds a juicy Microsoft Windows use case,

The relevant URI syntax update is now in IETF Last Call, i.e. the last opportunity for public comments: https://mailarchive.ietf.org/arch/msg/ietf-announce/BqBF9qvZ8qZR4ZPlawPvQSe0WbU/

As far as I understand things (and I'm a newcomer to avahi), avahi-publish-address fails, and could not possibly work as coded, for complete link-local addresses such as `fe80::1%eth0`. That's because...

@pwithnall, you said "Do non-Linux platforms use a different way of identifying scope IDs? IIRC they all do something similar, but this should be checked." On Windows, you see things...

I've done some more hacking at this, reported at https://github.com/becarpenter/misc/tree/main/zelect#linux-a-tale-of-woe

And there's this microtool for your amusement: https://github.com/becarpenter/misc/blob/main/dedup.py