Re: [Stox] Review of -chat

Saúl Ibarra Corretgé <> Wed, 31 July 2013 15:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A38F821F9C78 for <>; Wed, 31 Jul 2013 08:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.828
X-Spam-Status: No, score=-0.828 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3, SARE_MLH_Stock1=0.87]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id B8CvdckZWi17 for <>; Wed, 31 Jul 2013 08:16:52 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2856B21F9C9B for <>; Wed, 31 Jul 2013 08:16:51 -0700 (PDT)
Received: by (Postfix, from userid 5001) id C7C17B019B; Wed, 31 Jul 2013 17:16:50 +0200 (CEST)
Received: from ( []) by (Postfix) with ESMTPSA id 0E06DB017A; Wed, 31 Jul 2013 17:16:49 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <>
In-Reply-To: <>
Date: Wed, 31 Jul 2013 17:16:51 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: "Olle E. Johansson" <>
X-Mailer: Apple Mail (2.1508)
Cc: "" <>, Peter Saint-Andre <>
Subject: Re: [Stox] Review of -chat
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 31 Jul 2013 15:16:58 -0000

>> SIP entities will implement text/html, can we use that?
> Or recommend multipart/alternative if it's a downgrade?

I have never seen multipart used in MSRP and I'd rather not open that door ;-)

> Which document says that SIP Uas will support text/html?

Well, nobody says UAs will support it, it's negotiated with a=accept-types in SDP, but an MSRP client is very likely to implement it, directly or wrapped in CPIM.

>> For one, both SIP and XMPP clients usually implement typing indications so translating the semantics between the two is useful to get that information through. Now, as for the 'gone' state case, it's used by XMPP clients when the conversation is closed, so the other party can know that the window was closed on the other side and conversation has ended. Ending a conversation in SIP would mean sending a BYE, and this is particularly useful, because otherwise the SIP / MSRP session would stay up forever since there is no ending condition.
> Is the closing window notification more than just closing window? Is the chat dead, really?

My understanding is that chat "sessions" in XMPP is a very loose thing, so you could actually resume it later, but as a concept, if you close the window and you signal that you are "gone" I wouldn't expect further conversation from him. XMPP clients usually say "Olle has left the conversation".

Saúl Ibarra Corretgé
AG Projects