Re: [Simple] MSRP chat: draft-niemi-simple-chat-04.txt

[smile <wangsmile at huawei.com>]

inline
----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat at cisco.com>
To: "Aki Niemi" <aki.niemi at nokia.com>
Cc: "Miguel Garcia" <Miguel.An.Garcia at nokia.com>; "ext Adam Roach" <adam at nostrum.com>; <simple at ietf.org>
Sent: Tuesday, March 21, 2006 12:10 AM
Subject: Re: [Simple] MSRP chat: draft-niemi-simple-chat-04.txt


> 
> 
> Aki Niemi wrote:
> 
>>>In other words, the nickname reservation protocol that you're defining
>>>with the NICKNAME mechanism in MSRP shouldn't be limited to MSRP. My
>>>suggestion, for what it's worth, is that you (1) split the nickname
>>>reservation mechanism out into a separate draft, and (2) use either SIP
>>>or the XCON Conference Control Protocol instead of MSRP.
>> 
>> 
>> I think these two are actually reasonable suggestions, as long as the
>> same disclaimer we have in the draft still holds (namely, scope it for a
>> particular room only, first-come-first-served policy, defining "sticky"
>> nicknames out-of-scope, etc.).
> 
> I think it is ok if the mechanism doesn't require more than FCFS policy 
> for assignment of names. But neither should it be restricted to such a 
> policy. IMO sticky nicknames are quite important. It would be upsetting 
> if each time I came to the simple chat room I had to wonder whether 
> "fluffy" was still Cullen.
> 
So, I suggest nickname should be register in chat room, then your nickname 
will not be stolen. If user come into chat room has not registered, server can 
assign default nickname to him.

Xiao

> Paul
> 
> _______________________________________________
> Simple mailing list
> Simple at ietf.org
> https://www1.ietf.org/mailman/listinfo/simple
>

_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple