From 6eee70fb90409415252d9e6770d93757b5cdfa53 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 24 Jan 2007 04:06:57 +0000 Subject: [PATCH] 0.2 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@408 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0201.xml | 54 ++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 46 insertions(+), 8 deletions(-) diff --git a/xep-0201.xml b/xep-0201.xml index a8db4bec..069912a9 100644 --- a/xep-0201.xml +++ b/xep-0201.xml @@ -22,6 +22,13 @@ N/A &stpeter; &ianpaterson; + &ksmith; + + 0.2 + 2007-01-23 + psa +

Equalized treatment of different message types (chat and groupchat not preferred over normal); required the use of UUIDs; specified use of In-Reply-To header; added Kevin Smith as co-author.

 + 0.1 2006-12-20 @@ -42,14 +49,14 @@ - &RFC3921BISNOTE; -

Although message threads are re-used in XMPP extension protocols such as &xep0085; and &xep0155;, the semantics of message threads have never been well specified (e.g., in RFC 3921). This document attempts to clearly specify the meaning and handling of message threads for implementation by XMPP clients and possible incorporation into the successor to RFC 3921.

+

Although message threads are re-used in XMPP extension protocols such as &xep0085; and &xep0155;, the semantics of message threads have never been well specified (e.g., in &rfc3921;). This document attempts to clearly specify the meaning and handling of message threads for implementation by XMPP clients and for potential inclusion in &rfc3921bis;.

Threads matter because they enable XMPP clients to:

@@ -58,18 +65,20 @@

Section 2.1.2.3 of RFC 3920 currently states the following regarding the semantics of the ThreadID:

The <thread/> element contains non-human-readable XML character data specifying an identifier that is used for tracking a conversation thread (sometimes referred to as an "instant messaging session") between two entities.

The description in RFC 3921 is deemed to be too limiting, since it ignores the potential use of the ThreadID when exchanging message stanzas of types other than 'chat'. Therefore we proposal the following description:

-

The primary use of the XMPP <thread/> element is to uniquely identify a conversation thread or "chat session" between two entities instantiated by <message/> stanzas of type 'chat'. However, the XMPP <thread/> element may also be used to uniquely identify an analogous thread between two entities instantiated by <message/> stanzas of type 'headline' or 'normal', or among multiple entities in the context of a multi-user chat room instantiated by <message/> stanzas of type 'groupchat'.

+

The primary use of the XMPP <thread/> element is to uniquely identify a conversation thread or "chat session" between two entities instantiated by <message/> stanzas of type 'chat'. However, the XMPP <thread/> element may also be used to uniquely identify an analogous thread between two entities instantiated by <message/> stanzas of type 'headline' or 'normal', or among multiple entities in the context of a multi-user chat room instantiated by <message/> stanzas of type 'groupchat'. It may also be used for <message/> stanzas not related to a conversation, such as a game session or between plugins.

Section 2.1.2.3 of RFC 3920 currently states the following uniqueness requirement:

The value of the <thread/> element ... MUST be unique to that conversation thread within the stream and MUST be consistent throughout that conversation (a client that receives a message from the same full JID but with a different thread ID MUST assume that the message in question exists outside the context of the existing conversation thread).

The uniqueness requirement in RFC 3921 is not deemed strong enough since it is desirable that a ThreadID could be used to (for instance) restart a conversation at a later date. Therefore we propose the following uniqueness requirement:

-

For messages of type 'chat', 'headline', or 'normal', the value of the <thread/> element MUST be unique for the combination of the sender's bare JID and recipient's bare JID (i.e., the thread MUST NOT ever be repeated in communications between the sender and recipient). For messages of type 'groupchat', the value of the <thread/> element MUST be unique in the context of the multi-user chat room, as long as the room remains in existence.

+

The value of the <thread/> element MUST be a universally unique identifier (UUID) as described in &rfc4122;.

In the context of <message/> stanzas of type 'chat' exchanged between two entities, the value of the <thread/> element shall be considered equivalent to a unique identifier for the chat session or conversation thread. If an entity receives such a message with a new or unknown ThreadID, it SHOULD treat the message as part of a session with unnegotiated parameters (i.e., as equivalent to the first message in a chat session that has been negotiated via XEP-0155 with no parameters specified). An entity SHOULD destroy the thread when it sends or receives a XEP-0155 "terminate" action and MAY destroy the thread when it goes offline, but SHOULD NOT destroy the thread if a human user merely closes a window in a client interface.

+

When sending a <message/> stanza of type 'normal', the value of the <thread/> element is used to uniquely identify a conversation thread which may not be progressing in real-time. A <message/> stanza of type 'normal' SHOULD always use a new <thread/> element identifier unless it is written in direct reply to another <message/> stanza, in which case the <thread/> element of the original <message/> should be used. Determining what constitutes a <message/> stanza written in reply to another is a matter left to individual implementation, but it is envisaged that in most cases it would be the result of, e.g., the user clicking a 'reply' button when reading the contents of the previous stanza; alternatively, the entity that replies can include an "In-Reply-To" header as described in the Implementation Notes section of this document.

To ensure the uniqueness of ThreadIDs in the context of a multi-user chat room, the multi-use chat service MAY provide a way for room occupants to request a unique ThreadID; definition of such methods is out of scope for this specification.

-

There are no special handling requirements related to threads in the context of <message/> stanzas of type 'headline' or 'normal'.

+

There are no special handling requirements related to threads in the context of <message/> stanzas of type 'headline'.

+

When displaying historical conversations within a user interface, a client SHOULD provide a visual indication of thread membership of messages. Methods for such indications include (non-exhaustively) the grouping of all messages within a thread together, providing an index of threads, or formatting all messages within a thread in a cohesive manner, e.g. with a uniform coloring.

Depending on the type of the message (i.e., the value of the 'type' attribute), the <thread/> should be included as follows:

@@ -113,8 +122,37 @@ ]]> + +

An entity that needs to track replies to particular messages may do so by including an 'id' attribute with the &MESSAGE; stanza.

+ + Art thou not Romeo, and a Montague? + e0ffe42b28561960c6b12b944a092794b9683a38 + + ]]> +

The entity that replies then MAY include an "In-Reply-To" header:

+ + Neither, fair saint, if either thee dislike. + e0ffe42b28561960c6b12b944a092794b9683a38 + +
asiwe8289ljfdalk
+ + + ]]> + -

This document introduces no new security concerns or considerations above and beyond those specified in RFC 3920 and RFC 3921.

+

An entity that generates the UUID used as the ThreadID MUST ensure that the UUID does not reveal personally-identifying information about the entity.

This document requires no interaction with &IANA;.