[Stox] On generating RFC4575 participants list out of a MUC

Saúl Ibarra Corretgé <saul@ag-projects.com> Fri, 25 October 2013 08:38 UTC

Return-Path: <saul@ag-projects.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 04C8F11E82E4 for <stox@ietfa.amsl.com>; Fri, 25 Oct 2013 01:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.243
X-Spam-Status: No, score=-1.243 tagged_above=-999 required=5 tests=[AWL=-0.155, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_22=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id DESuLisJfJg7 for <stox@ietfa.amsl.com>; Fri, 25 Oct 2013 01:38:18 -0700 (PDT)
Received: from mail3.sipthor.net (node16.dns-hosting.info []) by ietfa.amsl.com (Postfix) with ESMTP id 03D3011E815A for <stox@ietf.org>; Fri, 25 Oct 2013 01:38:17 -0700 (PDT)
Received: from imac.saghul.lan (ip3e830637.speed.planet.nl []) by mail3.sipthor.net (Postfix) with ESMTPSA id E1A9B16DC722; Fri, 25 Oct 2013 10:42:33 +0200 (CEST)
From: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Oct 2013 10:38:14 +0200
Message-Id: <1B5D6CBE-2151-4749-8A7C-8122B04BB071@ag-projects.com>
To: stox@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: Peter Saint-Andre <stpeter@stpeter.im>
Subject: [Stox] On generating RFC4575 participants list out of a MUC
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 08:38:24 -0000

Hi all,

This is regarding the issue I mentioned at the meeting in Berlin to which Peter referred recently.

In 4575 there are 2 types of entities which kind of relate to participants: users and endpoints. Each user contains a list of endpoints. As per the RFC:

- "The <users> element is a container of <user> child elements, each
   describing a single participant in the conference."

- "By including one or more <endpoint> elements under a parent <user>
   element, the server can provide the desired level of detail
   (including the state, media streams, and access information) about
   the user's devices and signaling sessions taking part in the

In SIP a user would be an AoR and an endpoint would be the contact or GRUU.

In XMPP tough, things are a bit more complicated. In the beginning I thought we could use the user bare JID as the <user> element and the occupant JID as the <endpoint>, but in practice this is not going to work, because the real JID is not always available in a MUC.

So, considering that, here is how I propose we proceed:

- <user> element entity is the occupant JID
- if the real JID is available, it MAY be added as a <associated-aors> child element of <user> (4575, sec 5.6.2) (based on local policy)
- <endpoint> entity is also the occupant JID

Neither user entity or endpoint entity is an xs:ID, so using it in both places doesn't invalidate the document :-)


Saúl Ibarra Corretgé
AG Projects