Why is the IEEE working on this? Surely it would be considerably more productive just to ask the XSF (or even the IETF, I can see arguments for both) about the problem?
On Mon, 1 Apr 2019 at 10:51, Peter Waher <peterwa...@hotmail.com> wrote: > Hello Paul, and those in the community interested in end-to-end encryption > of stanzas. > > > > Within the IEEE IoT Harmonization effort, there is a mechanism to > E2E-encrypt stanzas in XMPP: > > https://gitlab.com/IEEE-SA/XMPPI/IoT/blob/master/E2E.md > > > > Site for the IEEE IoT Harmonization project: > > https://gitlab.com/IEEE-SA/XMPPI/IoT > > > > Best regards, > > Peter Waher > > > > ------------------------------ > > > Hi everyone! > > > > The Sprint in Berlin was great and it was huge fun meeting so many > > developers (and users as well!) in person. There was a ton of > > interesting discussions around OMEMO and other stuff, as well as some > > productive coding (and Mate!). > > > > I took the opportunity to once again start a discussion around partial > > stanza encryption. The results have been collected in the XMPP wiki: > > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.xmpp.org%2Fweb%2FStanza_encryption&data=02%> > > 7C01%7C%7Cd32bc798ae25486bb0c008d6b681ae6f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897065421995310&sdata=YqVBLurjKA1xIqjIMqKweWXhm6hhk%2F7cdLfpwkiyOjg%3D&reserved=0 > <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.xmpp.org%2Fweb%2FStanza_encryption&data=02%7C01%7C%7Cd32bc798ae25486bb0c008d6b681ae6f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897065421995310&sdata=YqVBLurjKA1xIqjIMqKweWXhm6hhk%2F7cdLfpwkiyOjg%3D&reserved=0> > > > > The ultimate goal is to create a ProtoXEP along with some experimental > > implementations, so we can finally start to gather some experience on > > this unexplored topic. I know there be dragons and we should carefully > > think about rules to prevent evil things from happening, but we also > > have to get started, as I think this topic has been postponed for all > > too long. > > > > The specification is worked on on Github and a rendered version can be > > found below (this is all what I came up with while on my train home). > > The purpose of this mail is to get some first feedback and make people > > aware about the work, so they can get involved in the process :) > > > > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvanitasvitae%2Fflowdalic-xeps%2Ftree%2Fsce&data=02%7C01%7C%7Cd32bc798ae25486bb0c008d6b681ae6f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897065421995310&sdata=T61uPbN2631En4SqdiDMW2Gwk5pfgrCxZXFmFxHpt%2Bg%3D&reserved=0 > > https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgeekplace.eu%2Fxeps%2Fxep-sce%2Fxep-sce.html&data=02%7C01%7C%7Cd32bc798ae25486bb0c008d6b681ae6f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897065422005321&sdata=3BvePHpJPZICLrqxlfiRW7sCL0EwLRov%2FEc6l5i%2Bkic%3D&reserved=0 > > > > I also created a small MUC on the topic, although the address is not > > final, as I may move the conversation to a more stable server (mine is > > hosted behind dyndns, so Schroedingers Chat might kick in :/). > > > > xmpp:s...@conference.jabberhead.tk?join > > > > Happy Hacking! > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
