[Standards-JIG] RE: Standards-JIG Digest, Vol 24, Issue 4
jean-louis.seguineau at laposte.net
Wed Jan 4 18:05:40 UTC 2006
Looks good to me.
I don't know what much can be said on the SIP side. SIP message sessions are
not a standard in their current form. They are somewhat described in
draft-ietf-simple-im-session-00.txt and implemented in the Microsoft IM
clients. The next generation SIMPLE message (Message Relay) specs are really
in their infancy.
On the message content/envelope once you map the <thread/> and the Call-ID
you have all what's needed for a single resource chat session. You may want
to add that some chat state information may be carried in either a SIP
MESSAGE or INFO, and mapped to JEP 85 chat states notification. Anyway, the
content type for this information is just being made standard on the SIP
Date: Tue, 03 Jan 2006 14:49:43 -0700
From: Peter Saint-Andre <stpeter at jabber.org>
Subject: Re: [Standards-JIG] Chat Session Negotiation
To: Jabber protocol discussion list <standards-jig at jabber.org>
Message-ID: <43BAF177.3050503 at jabber.org>
Content-Type: text/plain; charset="iso-8859-1"
OK, I updated JEP-0155 accordingly.
The SIP mapping requires more text, but it's a start.
Jean-Louis Seguineau wrote:
> If by 'acked' you mean receive a response (200 OK) the answer is yes. If
> mean receive an ACK message as in the INVITE transaction, this is not
> The BYE is used in SIP to signal the end of a dialog that has been
> previously established by an INVITE transaction. It can be initiated by
> either end of the dialog. In our case, this fit well with the use of an
> message stanza, and as you said and either party could send it to end the
> I agree that the easiest and cleanest way to associate this termination
> the initial negotiation is by using a thread ID.
More information about the Standards