diff --git a/xep-0189.xml b/xep-0189.xml index 56c08bcb..923667d6 100644 --- a/xep-0189.xml +++ b/xep-0189.xml @@ -25,9 +25,9 @@ &ianpaterson; 0.4 - 2006-11-23 + 2006-11-27 ip -

Changed namespace

+

Added jid attribute and send use case; changed namespace

0.3 @@ -115,7 +115,10 @@ julietDSAkey1 -

...

......... +

...

+ ... + ... + ...
@@ -236,8 +239,8 @@ -

If an entity wishes to request the public keys of another entity and it cannot access the keys via Personal Eventing via Pubsub, then the entity MAY send an IQ to the other entity:

- If an entity wishes to request the public keys of another entity and it cannot access the keys via Personal Eventing via Pubsub, then the entity MAY send an &IQ; of type 'get' to the other entity:

+ - - - julietRSAkey1 - ... - - - julietX509cert1 - ... - - + + + julietRSAkey1 + ... + + + julietX509cert1 + ... + + ]]>

If the receiving entity decides not to return the public keys, it MUST return an IQ error, which SHOULD be &unavailable; (to avoid divulging presence to unauthorized entities), but MAY be some other appropriate error, such as &forbidden; or ¬allowed;:

@@ -277,6 +280,69 @@ ]]>
+ +

An entity may request the public keys of another entity from a third party using the 'jid' attribute of the <pubkeys/> element to specify the JID that the keys belong to:

+ + + + ]]> + + + + benvolioRSAkey + ... + + + + ]]> + + + + + + + ]]> +
+ + +

If an entity wishes to send public keys to another entity then it MAY include them in a &MESSAGE; stanza. The entity MAY use the 'jid' attribute of the <pubkeys/> element to specify the JID that the keys belong to. If no 'jid' attribute is specified then the other entity SHOULD assume the keys belong to the sender of the stanza.

+ + + + + + ... + AQAB + + + + + + + ... + AQAB + + + + + + ]]> +
+

The reliable association between a user or entity and its public keys is beyond the scope of this document. However, each client SHOULD maintain its own secure library of the public keys (or the "fingerprints" of the keys) it associates with other users (not necessarily JIDs).

Whenever public keys are published an identity is typically associated with a JID. Although the public keys are public information, it may be critically important for the user of the JID to keep his identity secret from all but a few specified people. Implementors MUST take great care to ensure the identity of the user of a JID is never divulged to anyone except the entities who have been permitted by the user to access the public key.

@@ -305,6 +371,7 @@ +