Re: draft-ietf-simple-chat-10

On Nov 24, 2011, at 7:39 AM, Ben Campbell wrote:

> 
> On Nov 24, 2011, at 3:45 AM, Miguel A. Garcia wrote:
> 
>> On 23/11/2011 19:42, Ben Campbell wrote:
>>>> - the nickname is bound only to a session, not to an AOR.
>>>> The nicknames for sessions must all be unique.
>>> 
>>> I think this is the right answer, but I think it's really "bound to an AoR in the scope of a session". It seems like any scoping of nicknames beyond a specific session should be a matter of local policy. Is there anything that stops an implementation from binding a nickname across multiple simultaneous sessions or even multiple sequential sessions if it wants to?
>>> 
>> 
>> I wouldn't like to see this option as the only one. I would like to join the conference with the same AOR from different devices and use the same nickname. Basically, I would like to hide the fact that I am using several devices to join the chat, and be known with a single nickname across all devices.
> 
> Sure, but isn't that still a  local policy choice on how an implementation handles the same nicknames across multiple MSRP sessions?

To elaborate: Would it make sense to say something the effect that a nick is bound to an AoR for the scope of the MSRP session. A conference server MAY, as a matter of local policy, bind the nick at a higher scope. For example… [list a few use cases]

Or do you think the other use cases need to be standardized? This is more of a user experience question than an interop question, as long as we have a way of telling a client it can't use a particular nickname.

> 
>> 
>> /Miguel
>> -- 
>> Miguel A. Garcia
>> +34-91-339-3608
>> Ericsson Spain
>