Re: Using nicknames in conference event packages (draft-ietf-simple-chat)

(as chair)

Hi, and sorry for the late response. 

The decision to use the xcon conference event package format is the result of an explicit SIMPLE consensus call back in December of 2010. That doesn't mean we can't readdress it, but we would need a really new and strong technical reason to do so at this late stage. (The draft is in IESG evaluation.) See the following email and the resulting thread:

http://www.ietf.org/mail-archive/web/simple/current/msg09093.html

(as individual)

The current text in the draft says use of that format is RECOMMENDED, i.e. it's at SHOULD strength. According to RFC 2119, that means the "... may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course" allows an implementation to choose another approach if there is good reason, and the implementer is aware of the consequences of the decision."

It seems to me that an implementation could choose to user other methods to express a nickname and not necessarily be non-compliant. But I would be concerned that doing so could cause interoperability problems between switches and clients.

Thanks!

Ben.

On Jun 14, 2012, at 9:37 AM, Saúl Ibarra Corretgé wrote:

> Hi,
> 
> The draft-ietf-simple-chat specification states that the 'nickname' extension defined by XCON (RFC 6501) should be used to convey the nickname in the conference event package. I think section 7.4 could clarify this a bit more, since the following may happen:
> 
> Alice joins the conference from multiple endpoints, but same AoR. The way the conference event payload is defined, there will be only one <user> element, because the 'entity' attribute needs to be unique and in the context of a SIP conference the entity most likely will be the user's AoR. There will be 2 <endpoint> elements, representing each of Alice's SIP clients, so putting the nickname there would IMHO make more sense.
> 
> Also, using XCON just for the nickname attribute may not be desired by some (that's me at least :-) ) so what about adding something along these lines to section 7.4? "A conference focus MAY choose to use the display-text element in the 'endpoint' or 'user' element to convey the user's nickname".
> 
> 
> Regards,
> 
> --
> Saúl Ibarra Corretgé
> AG Projects
> 
> 
> 
> _______________________________________________
> Simple mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/simple