Re: [Stox] Nickname Usage Conflict Resolution
Peter Saint-Andre <stpeter@stpeter.im> Wed, 24 July 2013 02:57 UTC
Return-Path: <stpeter@stpeter.im>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6ED11E81C3 for <stox@ietfa.amsl.com>; Tue, 23 Jul 2013 19:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.014
X-Spam-Level:
X-Spam-Status: No, score=-102.014 tagged_above=-999 required=5 tests=[AWL=-0.585, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_MLH_Stock1=0.87, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMIU-Wnh4yyg for <stox@ietfa.amsl.com>; Tue, 23 Jul 2013 19:57:36 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 6283611E81C0 for <stox@ietf.org>; Tue, 23 Jul 2013 19:57:33 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id ABD03414B4; Tue, 23 Jul 2013 20:59:22 -0600 (MDT)
Message-ID: <51EF429A.3010506@stpeter.im>
Date: Tue, 23 Jul 2013 20:57:30 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Saúl Ibarra Corretgé <saul@ag-projects.com>
References: <D928759B0247C54198D70FCD4A07DD8E38E38B62@ASHBDAG1M2.resource.ds.bah.com> <31EA9B37-9F4C-4473-A1BC-2B18759B865D@ag-projects.com>
In-Reply-To: <31EA9B37-9F4C-4473-A1BC-2B18759B865D@ag-projects.com>
X-Enigmail-Version: 1.5.1
X-Enigmail-Draft-Status: 513
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: "stox@ietf.org" <stox@ietf.org>, "De Vries, Michael [USA]" <devries_michael@bah.com>
Subject: Re: [Stox] Nickname Usage Conflict Resolution
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: Wed, 24 Jul 2013 02:57:41 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/20/13 7:48 AM, Saúl Ibarra Corretgé wrote: > Hi Michael, > > On Jul 20, 2013, at 1:07 AM, De Vries, Michael [USA] wrote: > >> Hello everyone, >> >> I have a concern with the suggested possible resolutions for a >> Nickname Usage Conflict in the draft-ietf-stox-groupchat-00 >> document. In section 3.2, the document says >> >> | Alternatively [to translating the MSRP 425 message to a >> <conflict/> error], | the gateway might generate a new >> nickname request on | behalf of the XMPP user, thus shielding >> the XMPP client from handling | the conflict error. >> >> Additionally, section 5 says >> >> | If there is a conflict between the SIP nickname and the XMPP >> | nickname, the SIP-to-XMPP or XMPP-to-SIP gateway is >> responsible for | adjusting the nickname to avoid the conflict >> and for informing the | SIP or XMPP client of the unique >> nickname used to join the chatroom. >> >> First, section 3.2 suggests that the gateway may choose to >> generate a new nickname, but can instead merely forward on the >> translated MSRP 425 or <conflict/> error, whereas section 5 says >> that the gateway is responsible for (aka MUST) adjusting the >> nickname in the event of a conflict. Both of these sections >> suggest that in the case of a nickname conflict the gateway may >> act independently of the client to change the client-generated >> nickname to one which is unique within the context of the >> chatroom. I'm not certain this is the most appropriate approach. >> Nicknames are important in that they are needed to facilitate >> private messaging and other features, as well as being an >> important part of user identification. It seems risky to >> automatically generate a new nickname when a conflict is found, >> instead of merely presenting the error to the user (via MSRP 425 >> message or <conflict/> error) so that they can choose a new >> nickname via their client. Additionally, a cursory examinatio n >> of the XMPP, MSRP, and MUC RFCs/XEPs does not appear to show any >> recommendation that nicknames be automatically generated in the >> event of a conflict. >> >> I believe that it would be better to require that the gateway >> merely forward on the translated MSRP 425 or <conflict/> error >> instead of attempting to address the conflict automatically, but >> I may not sufficiently understand the reasoning behind the >> automated nickname resolution. >> > > I agree. This is how things are usually handled in MSRP. When > testing things in XMPP however, not every client is able to > properly deal with nickname conflicts though. Peter, maybe this was > the reason why that text was added? I doubt that was the reason, since I don't believe in designing protocols around buggy software. :-) Many XMPP clients will indeed shield the user from making a decision about the nickname (e.g., if "stpeter" is taken they will cycle through nicks like "stpeter1" or "stpeter_" or whatever). So pushing an error back to the originating client seems fine to me in all cases. Question: if the gateway were to choose a nick on behalf of the client, are we sure that the chosen nick would get communicated back to the originating client? In any case, I think that what Mike proposes is sensible. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR70KaAAoJEOoGpJErxa2p478P/RLyVu5bqCMkC6ZgsPg8d1+0 KLcn1lwfsY/ivbXnDfugo0jrqH/hIr323K2Fjrmghdsg5kQnZ64ZG5afKyzP38gT c2HRYVSPhiPzqxD3h3Sm4w3GOjlJUqmWe8qijkszhkkbOMWuZC9DhWg738G2Kpwc AraKbB0OXmChJmdSlhIeps5cWfxtSyPQ1Gf6KCNoyAsloVVRjoGJymOZkm2YKnCI yQJsDT/ugkCpdNghUE9IiOXXtJ5uS2JAVfqdxJ1wrelRLBo++b+fBsGTz+5R7szt eQ7VnOyYX2smPD4gYlkcYHZ1gfvCT7a/4lXX5vOKwqxP3QcBoZp55ahFIzEmfkub zecoBhQonKZ06uXiWH6X7rQR+RhMhnPd63MkjxfJ0N0LsWQBhk+5Zge1bSvfqWLa 1XegEZuuVgj1ylytBjkLdePZc4kkK8ESG5u5gm300F6AeKBG3pW4qvft3jZ3ITxM PbhMfOJK+Pxn5roxy0wljBbQC3GWrC2KZTkpSoQXK2Wgh4SAI6IMfqJMVq4GPvCH Vd/IY6Ap9OiRyoPvDfmBag0qu1BXHK4tQGTpnCRMj3fXbU55OJ6I0ZhkTsde858M gb5CsHmW7an6cvgMYoxx/d95C/mZ4nc40U3nnZBX03cN2L9elhbX5V+Co/02OBLl flUT0UI8+ETldks/3q8u =BOf5 -----END PGP SIGNATURE-----
- [Stox] Nickname Usage Conflict Resolution De Vries, Michael [USA]
- Re: [Stox] Nickname Usage Conflict Resolution Saúl Ibarra Corretgé
- Re: [Stox] Nickname Usage Conflict Resolution Peter Saint-Andre