Re: [Simple] I-D Action: draft-ietf-simple-chat-17.txt

[Paul Kyzivat <[e-mail]>]

On 11/19/12 4:12 PM, Ben Campbell wrote:
> Thanks Miguel. I think this version is much improved. But of course, here's a few questions and comments:
>
> Questions:
>
> 5.2 : There is new normative language in section 5.2 concerning the use of "accept-types" and "accept-wrapped-types" Do I read it correctly that and endpoint SHOULD (i.e. RECOMMENDED) include accept-wrapped-types, and a focus MAY do so? Do we allow either to include anything _other_ than message/cpim in accept-types?  If not, what does it mean to include only message/CPIM in "accept-types" and not include "accept-wrapped-types"?
>
> The last paragraph of 5.2 says that the focus must inform the switch of the chat room capabilities of each participant, and that it does this with the SDP "chatroom" attribute. Do we assume anything about how the focus and switch communicate? I thought the chatroom attribute was more about how the focus communicates this with _endpoints_.

This was in response to comments I made some time ago.
The point was to future-proof this, so that if in the future there is a 
new type (say message/cpim++) that something that implements that will 
be able to indicate support for both message/cpim and message/cpim++ and 
still be conforming to this spec.

(Of course, if both ends then support message/cpim++ and decide to use 
it, then they will cease to be operating in accord with this spec. 
Instead they will be following some new spec that calls for use of 
message/cpim++.)

	Thanks,
	Paul