… Please note that the demultiplexing Session Traversal Utilities for NAT (STUN) RFC5389 vs. SRTP vs. DTLS is done as described in Section 5.1.2 of [ RFC5764 , and SCTP is the only payload of DTLS. Since DTLS is typically implemented in user application space, the SCTP stack also …

…d, and if not, can respond with an 401 (Unauthorized) error, as described in [[!RFC5389]] Section 10.1.2. For incoming connectivity checks that pass validation, the RTCIceGatherer MUST buffer the incoming connectivity checks so as to be able to provide them to associated RTCIceTr…

…d, and if not, can respond with an 401 (Unauthorized) error, as described in [[!RFC5389]] Section 10.1.2. For incoming connectivity checks that pass validation, the RTCIceGatherer MUST buffer the incoming connectivity checks so as to be able to provide them to associated RTCIceTr…

… The key length facilitates the hash agility plan discussed in Section 16.3 of [RFC5389]. It should say: key_length: Length of the session key in octets. Notes: RFC2104 section 2 states: The authentication key K can be of any length up to B, the block length of the hash function.…

… The key length facilitates the hash agility plan discussed in Section 16.3 of [RFC5389]. It should say: key_length: Length of the session key in octets. Notes: RFC2104 section 2 states: The authentication key K can be of any length up to B, the block length of the hash function.…