Re: [MMUSIC] SCTP-SDP: Virtual Connection impact

[Roman Shpount <[e-mail]>]

Christer,

The note tells what does not trigger setup of the new DTLS connection in
case of ICE. It does not specify what does. I also think it is ambiguous.
Current language implies that all candidate pairs associated with
SCTP association are the same transport.  Does this mean that if SCTP
connection is not re-established and ICE is used, new DTLS session is not
started? Or does it mean that a new DTLS connection is setup for each new
ICE session? What about ICE restart (i.e. ufrag change between the same end
points when the same candidate sets are reused on both sides)?

I believe more precise definition of behavior and additional text
clarification is needed here.
_____________
Roman Shpount

On Mon, Mar 30, 2015 at 12:46 PM, Christer Holmberg <
[e-mail]> wrote:

>  Hi Roman,
>
> The new note is intended to cover ICE.
>
> Regards,
>
> Christer
>
> Sent from my Windows Phone
>  ------------------------------
> From: Roman Shpount <[e-mail]>
> Sent: ‎30/‎03/‎2015 17:21
> To: Christer Holmberg <[e-mail]>
> Cc: mmusic <[e-mail]>
> Subject: Re: [MMUSIC] SCTP-SDP: Virtual Connection impact
>
>   On Sat, Mar 28, 2015 at 5:52 AM, Christer Holmberg <
> [e-mail]> wrote:
>
>>     Once the DTLS connection has been established, the endpoints MUST NOT
>>
>>    modify (as result of an offer/answer exchange) the TLS roles, or the
>>
>>    'active/passive' status, of the endpoints, unless the underlying
>>
>>    transport protocol is also modified (e.g. if an IP address- or port
>>
>>    value associated with the transport protocol is modified).
>>
>>
>>
>  In case of ICE, how do you define modification of the underlying
> transport protocol? IP address and port can obviously change to IP and port
> of another candidate pair.
>  _____________
> Roman Shpount
>
>