From 23b76e82952bc81c6039daf93706a120e8ff6ce5 Mon Sep 17 00:00:00 2001 From: Ian Paterson Date: Fri, 20 Oct 2006 10:18:39 +0000 Subject: [PATCH] 0.10 RC1 added AMP note git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@117 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0155.xml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/xep-0155.xml b/xep-0155.xml index 8dbb0efb..a409dea8 100644 --- a/xep-0155.xml +++ b/xep-0155.xml @@ -29,7 +29,7 @@ 0.10 2006-10-20 ip -

Enhanced implementation notes.

 +

Enhanced implementation notes; added AMP note.

 0.9 @@ -105,6 +105,7 @@

In order to initiate a negotiated chat session, the initiating party ("user") sends a &MESSAGE; The &MESSAGE; stanza is used because the user does not necessarily know which of the contact's resources is most available (or indeed if the contact is online). stanza to the receiving party ("contact") containing a <feature/> child qualified by the 'http://jabber.org/protocol/feature-neg' namespace. The &MESSAGE; stanza MUST NOT contain a &BODY; child element (as specified in &rfc3921;). The &MESSAGE; stanza type SHOULD be "normal" (either explicitly or by non-inclusion of the 'type' attribute). The stanza MAY include an 'id' attribute and MUST contain a &THREAD; element for tracking purposes (where the newly-generated ThreadID is unique to the proposed session). The data form MUST contain a hidden FORM_TYPE field whose value is "http://jabber.org/protocol/chatneg" and MUST contain a boolean field named "accept". &BOOLEANNOTE; The inclusion of "otr" and "security" fields is also RECOMMENDED. Note: The options within any 'list-single' fields SHOULD appear in order of preference.

+

Note: If the user is interested only in an immediate chat session then the user SHOULD instruct the contact's server not to store the message for later delivery using the &xep0079; protocol.

In the following example of a negotiation request, Romeo requests a chat with Juliet and also queries her regarding whether she wants to enable all message logging (see &xep0136;) A client MUST NOT set the 'otr' field to 'true' unless it has confirmed that its server will allow it to switch off Automated Archiving (see Message Archiving). and support the &xep0071; and &xep0085; extensions during this chat session. He also requires that they are both connected securely to their servers, and asks which language she prefers amoungst those he can write. (Note: These fields are examples only; a full set of chat session negotiation parameters will be registered as described in the XMPP Registrar Considerations section of this document.)

+ + + ]]>

The contact's server delivers the request to the contact's most available resource (which in the examples below happens to be "balcony").