From 15242bc9385108adef1ca5063d9281ae5c1af5e7 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 7 Dec 2007 02:44:02 +0000 Subject: [PATCH] reversion git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1462 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0100.xml | 157 +-------------------------------------------------- 1 file changed, 1 insertion(+), 156 deletions(-) diff --git a/xep-0100.xml b/xep-0100.xml index 723e9411..e9184952 100644 --- a/xep-0100.xml +++ b/xep-0100.xml @@ -28,12 +28,6 @@ &stpeter; &dizzyd; - - 1.1pre3 - 2007-11-19 - psa - Clarified that username used for registration is legacy user address; added optional support for specifying roster group name for contact list items sent via roster item exchange, either directly for legacy services that do not support groups or indirectly via a group name modifier and location (prefix or suffix) for legacy services that support groups. - 1.0 2005-10-05 @@ -960,156 +954,7 @@ - -

Some legacy services maintain server-side contact lists, which are sent to the gateway when it logs in to the legacy service on behalf of the user. The gateway MAY initiate adding of the legacy contact list items to the user's Jabber roster. Some existing gateways do this by sending a presence stanza of type "subscribed" from the legacy contact's JID (e.g., <LegacyUser@gateway.jabberserver.com>) to the Jabber user; unfortunately, this behavior violates the presence stanza handling rules specified in RFC 3921. Therefore, a gateway SHOULD instead send the legacy contact list items to the Jabber User via the &xep0144; protocol.

- - - - - - ]]> - - -

There are two scenarios for gateway handling of roster groups: either (1) the legacy service does not support groups or (2) the legacy service supports groups.

-

If the legacy service does not support categorization of contact list items into groups (equivalent to XMPP roster groups), then a gateway that handles communications with such a legacy service SHOULD enable the user to specify his or her desired roster group for those items by providing a field of "group" in the data form it provides to the user on registration.

- - - - Use the enclosed form to register. If your Jabber client does - not support Data Forms, visit http://www.shakespeare.lit/ - - - - Please provide the following information - to register with the AIM gatway. - - - jabber:iq:register - - - - - - - - - - - - ]]> - - - - - jabber:iq:register - - - RomeoMyRomeo - - - ILoveJuliet - - - AIM (Home) - - - - - ]]> -

When the gateway sends roster items to the user, it SHOULD then include the specified group.

- - - - AIM (Home) - - - - ]]> -

However, if the legacy service supports groups, then a gateway that handles communications with such a legacy service SHOULD enable the user to specify his or her desired roster group prefix or suffix for those items by providing fields of both "group" and "groupmodify" in the data form it provides to the user on registration.

- - - - Use the enclosed form to register. If your Jabber client does - not support Data Forms, visit http://www.shakespeare.lit/ - - - - Please provide the following information - to register with the MSN gateway. - - - jabber:iq:register - - - - - - - - - - - - - - - - ]]> - - - - - jabber:iq:register - - - RomeoMyRomeo - - - ILoveJuliet - - - (MSN Home) - - - suffix - - - - - ]]> -

When the gateway sends roster items to the user, it SHOULD then include the group name from the legacy service, prepended or appended with the groupmodify value.

- - - - Servants (MSN Home) - - - - ]]> - +

Some legacy services maintain server-side contact lists, which are sent to the gateway when it logs in to the legacy service on behalf of the user. The gateway MAY initiate adding of the legacy contact list items to the user's Jabber roster. Some existing gateways do this by sending a presence stanza of type "subscribed" from the legacy contact's JID (e.g., <LegacyUser@gateway.jabberserver.com>) to the Jabber user; unfortunately, this behavior violates the presence stanza handling rules specified in RFC 3921. Therefore, a gateway SHOULD instead send the legacy contact list items to the Jabber User via the &xep0144; protocol.

The following business rules apply: