Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-07 ends 4 June

[Paul Kyzivat <[e-mail]>]

Roni,

I've trimmed this to the ones I wanted to follow up on.
All else is fine.

On 6/10/16 2:27 AM, Roni Even wrote:

>> I'll also note that "[I-D.ietf-mmusic-sdp-bundle-negotiation]" is rather
>> unwieldy to read. It would be helpful to change the references to
> something
>> more concise, such as [BUNDLE]. (xml2rfc supports this.)
> [Roni Even] This will change to the RFC number.

OK, that didn't dawn on me.

>> * Section 4.5:
>>
>>     The recommendation is that CLUE endpoints using SSRC multiplexing
>>     MUST support [I-D.ietf-mmusic-sdp-bundle-negotiation] and use the SDP
>>     mid attribute for mapping.
>>
>> I read this as being a bit stronger than I think is intended. I think the
> intent is
>> that all CLUE endpoints support BUNDLE (for interoperability), but that
> they
>> need not offer it. And they only need to use mid when they are using
>> BUNDLE. If they are not using BUNDLE then use of mid is optional.
> [Roni Even] I am not sure, what it says is that if when using SSRC
> multiplexing it must be done using bundle

OK, I take it back. I haven't thought about this for awhile and was a 
little muddled.

>> * Section 9:
>>
>> Shouldn't there be two things registered here? Both the RTP header
>> extension and the RTCP SDES item.
> [Roni Even] both are there.

Sorry, I didn't look close enough and thought all that text was about 
the captureid.

I think it would be helpful to break these into two subsections so that 
it is very clear that there are two actions called for.

	Thanks,
	Paul