Re: [rtcweb] RFC 5763 Section 6.7.1 (was DTLS, DTLS-SRTP, and 5-tuples)

[Jonathan Lennox <[e-mail]>]

On Mar 26, 2015, at 6:41 PM, Bernard Aboba <[e-mail]<mailto:[e-mail]>> wrote:

RFC 5763 Section 6.7.1 explains much of what we've been talking about on this thread.
6.7.1<http://tools.ietf.org/html/rfc5763#section-6.7.1>. ICE Interaction

   Interactive Connectivity Establishment (ICE), as specified in
   [RFC5245<http://tools.ietf.org/html/rfc5245>] provides a methodology of allowing participants in
   multimedia sessions to verify mutual connectivity.  When ICE is being
   used, the ICE connectivity checks are performed before the DTLS
   handshake begins.  Note that if aggressive nomination mode is used,
   multiple candidate pairs may be marked valid before ICE finally
   converges on a single candidate pair.  Implementations MUST treat all
   ICE candidate pairs associated with a single component as part of the
   same DTLS association.  Thus, there will be only one DTLS handshake
   even if there are multiple valid candidate pairs.  Note that this may
   mean adjusting the endpoint IP addresses if the selected candidate
   pair shifts, just as if the DTLS packets were an ordinary media
   stream
(Adding MMUSIC.)

The one recommendation I’d make for this problem is that one of the DTLS-SCTP drafts (probably ietf-mmusic-sctp-sdp, I guess?) should repeat this text from 5763.