From ea1f6054a27c32938e65732c91586c1263877d6d Mon Sep 17 00:00:00 2001 From: stpeter Date: Tue, 5 Oct 2010 15:09:41 -0600 Subject: [PATCH] added RFC 5256 --- xep-0201.xml | 2 +- xep.ent | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/xep-0201.xml b/xep-0201.xml index 35643bb6..28ef7bc4 100644 --- a/xep-0201.xml +++ b/xep-0201.xml @@ -146,7 +146,7 @@ -

In general, the XMPP <thread/> element is handled in a manner similar to the "References:" header field from email (see &rfc5322;) and netnews (see &rfc5536;). Detailed guidelines for particular XMPP message types are provided in the following sections.

+

In general, the XMPP <thread/> element is handled in a manner similar to the "References:" header field from email (see &rfc5322;) and netnews (see &rfc5536;), as well as the THREAD extension to IMAP (see &rfc5256;). Detailed guidelines for particular XMPP message types are provided in the following sections.

For <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 new chat session. A client MAY destroy the thread when it goes offline, but SHOULD NOT destroy the thread if a human user merely disengages from the chat session (e.g., by closing a window in a client interface).

If an entity receives an XMPP presence stanza of type "unavailable" from the other entity during a chat session, it SHOULD NOT destroy the thread; instead, it SHOULD assume that the other entity will still be able to continue the session (perhaps the other entity was temporarily disconnected by a network error or is persisting the state of the session until it reconnects and receives "offline" messages).

diff --git a/xep.ent b/xep.ent index 67455a45..39f24c1c 100644 --- a/xep.ent +++ b/xep.ent @@ -579,6 +579,7 @@ THE SOFTWARE. RFC 5178 RFC 5178: Generic Security Service Application Program Interface (GSS-API) Internationalization and Domain-Based Service Names and Name Type <http://tools.ietf.org/html/rfc5178>." > RFC 5179 RFC 5179: Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism <http://tools.ietf.org/html/rfc5179>." > RFC 5246 RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 <http://tools.ietf.org/html/rfc5246>." > +RFC 5256 RFC 5256: Internet Message Access Protocol - SORT and THREAD Extensions <http://tools.ietf.org/html/rfc5256>." > RFC 5280 RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile <http://tools.ietf.org/html/rfc5280>." > RFC 5322 RFC 5322: Internet Message Format <http://tools.ietf.org/html/rfc5322>." > RFC 5359 RFC 5359: Session Initiation Protocol Service Examples <http://tools.ietf.org/html/rfc5359>." >