While I do maintain that "it's coming from the LAN" is not a good #security boundary, there are services where it is practical (eg. media center volume control), but also fault prone (oups my phone just switched to LTE for power saving – a generally justified thing).
Before I start formalizing how "a device can retain permissions it gets from being local for a few days" could work with EST / #TLS / #EDHOC: Does this model have a name, and/or have you ever seen it discussed or deployed anywhere?
Attached: 1 image Granted, it's not exactly out of the box, but with some more patches and band-aids this is capable of establishing an EDHOC connection even from the browser. Full source at <https://github.com/chrysn/aiocoap/blob/master/contrib/edhoc-demo-server.ipynb> Once more, thanks @[email protected] and @[email protected] for providing that great infrastructure.
The #IETF122 hackathon starts in a few hours. I will be joining remotely, work on #EDHOC on @ariel (let's see if its out-of-the-box support also interoperates out-of-the-box), and play with #embeddfriendly URIs expressed in #CBOR.
Ephemeral Diffie-Hellman Over COSE (EDHOC) described in the recently-published RFC 9528 and RFC 9529 is a very compact, lightweight authenticated key exchange protocol, providing state-of-the-art security including mutual authentication, forward secrecy and identity protection.