Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This protocol uses Simple Traversal of UDP through NAT (STUN) binding request and response messages for connectivity checks between the two endpoints. The protocol supports message formats specified in [IETFDRAFT-STUN-02] section 10 and [RFC5389] section 11<2>. The message format is negotiated according to section 3.1.5.2. STUN messages sent over Transmission Control Protocol (TCP) MUST follow the framing method specified in [RFC4571] section 2. This method is required to demultiplex the received application data and STUN packets. STUN messages MUST support the STUN extensions and attributes specified in [IETFDRAFT-ICENAT-19] section 19. The XOR-MAPPED-ADDRESS attribute MUST have a value of 0x0020.
This protocol defines two additional attributes: CANDIDATE-IDENTIFIER and IMPLEMENTATION-VERSION, which MUST be supported per the procedures in [IETFDRAFT-STUN-02] section 10.2 if the message format follows [IETFDRAFT-STUN-02], or in [RFC5389] section 15 if the message format follows [RFC5389]. The CANDIDATE-IDENTIFIER attribute MUST be sent only with STUN binding request messages. The IMPLEMENTATION-VERSION attribute MUST be added to all STUN binding request and response messages.