Re: accept-types [was Re: Fwd: Re: Adrian Farrel's Discuss on draft-ietf-simple-chat-16: (with DISCUSS and COMMENT)]

On Sep 6, 2012, at 7:28 AM, Miguel A. Garcia <[email protected]> wrote:

> Hi Ben,
> 
> Inline comments.
> 
> On 05/09/2012 21:05, Ben Campbell wrote:
>> 
>> On Sep 5, 2012, at 9:35 AM, Miguel A. Garcia <[email protected]> wrote:
>> 
>>> I am now addressing the issue with accept-types and accept-wrapped-types.
>>> 
>>> There are two affected sections:
>>> 
>>> Section 5.2 discusses the SDP offer/answer when joining a chat room. The text now reads:
>>> 
>>>          The conference focus of a chat room MUST include support for
>>>          a <xref target="RFC3862">Message/CPIM</xref> top-level
>>>          wrapper for the MSRP messages by setting the 'accept-types'
>>>          MSRP media line attribute in the <xref target="RFC3264">SDP
>>>          offer or answer </xref> to include 'Message/CPIM'.
>> 
>> _only_ Message/CPIM, right? Or can other media types be included at the root?
> 
> Well, I expect the UA to be common to chat (through chat server) and point-to-point instant messaging. If this is the case, the UA will add the accept-types including types that are supported and useful for both chat and point-to-point IM. Then the MSRP switch will response with only Message/CPIM.

But the text talks about the what the conference focus sends, not UAs in _general_. If the focus includes anything _other_ than Message/CPIM in accept-types, it better be prepared to receive it. Is that the intent?

> 
> So, to summarize, the UA populatse the accept-types with all the formats that it supports, including Message/CPIM; the server will reply with Message/CPIM. The text to support this reads:
> 
>   The conference focus of a chat room MUST include support for a
>   Message/CPIM [RFC3862] top-level wrapper for the MSRP messages by
>   setting the 'accept-types' MSRP media line attribute in the SDP offer
>   or answer [RFC3264] to include 'Message/CPIM'.