Re: [MMUSIC] WGLC on draft-ietf-mmusic-msrp-usage-data-channel-16

[Paul Kyzivat <[e-mail]>]

On 5/10/20 3:29 PM, Christer Holmberg wrote:

>>> "This document RFC 4975, by allowing the usage of the "msrps" scheme 
>>> when the underlying connection is protected with DTLS."
>>
>> The key is ensuring that the required usage is clear and unambiguous. 
>> Specifically, ISTM that a "msrps" URI together with a "dc" parameter 
>> implies that connecting to this requires use of a data channel over a 
>> DTLS association established using the address in the URI.
>>
>>> Following up on that, a question about the example in 4.8:
>>>
>>> The path attribute includes:
>>>
>>>    msrps://bob.example.com:54111/si438dsaodes;dc
>>
>> but the corresponding c= is:
>>
>>    c=IN IP4 198.51.100.79
>>
>> Am I to infer that =IN IP4 198.51.100.79 is the resolution of 
>> bob.example.com:54111? If so, why doesn't the c= reference 
>> bob.example.com:54111?
> 
> I think we should remove the port number for the path attribute.
> 
> As you know, we have tried to make it clear that the msrp URI is not 
> used for routing, and that the path can be set to anything.
> 
> Do you want the address and port of the path URI to match the c= line?

My thought is: what do I start with in order to establish communication 
with you? In this case I'm thinking it is the msrps URI. Starting with 
only that as my knowledge about you, how do I set up a connection?

I hope it isn't necessary to know anything else. If not, then I suggest 
that the example proceed on that basis.

	Thanks,
	Paul