Yes, I totally agree this could make some things easier and it seems relevant for some use cases we have.
I do have to bend my brain a bit to interprete the fields right though. I have understood that the "to" field is used to impersonate another entity. When I am a privileged entity "special.myserver.com" and I send something on behalf of "[email protected]" to a entity called "someoneelse.montague.org", what do I do? I saw now that I send the stanza with the entity I am impersonating in the "to"-attribute. Then I would send it to capulet.org? how do I tell the server entity where the stanza should be addressed? In the light of this confusion I still have, could it be that there is something wrong in the examples 6 &7 in 4.2? The entity "sync.capulet.net" requests something on behalf of [email protected] (possibly capulet.net or somehow both the same). The answer in ex.7 is sent to a pubsub service without from. Now my naïve internal parser suggest that: a) either the ex.7 is from the pubsub service b) or/and it should be to sync.capulet.net As you see, I like the concept but am still struggling to understand the details. Best Regards, Johannes -----Ursprüngliche Nachricht----- Von: Standards [mailto:[email protected]] Im Auftrag von XMPP Extensions Editor Gesendet: Donnerstag, 18. September 2014 19:40 An: [email protected] Betreff: [Standards] Proposed XMPP Extension: Privileged Entity The XMPP Extensions Editor has received a proposal for a new XEP. Title: Privileged Entity Abstract: This specification provides a way for XMPP entities to have a privileged access to other entities data URL: http://xmpp.org/extensions/inbox/privilege-component.html The XMPP Council will decide in the next two weeks whether to accept this proposal as an official XEP.
