RFC Errata
Found 2 records.
Status: Held for Document Update (1)
RFC 6062, "Traversal Using Relays around NAT (TURN) Extensions for TCP Allocations", November 2010
Source of RFC: behave (tsv)
Errata ID: 3469
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Nazmus Shakeeb
Date Reported: 2013-01-23
Held for Document Update by: Martin Stiemerling
Date Held: 2013-09-30
Section 5.2. says:
The server MUST buffer any data received from the client.
It should say:
The server MUST buffer any data received from the peer.
Notes:
It is solely a typo, i.e., client is replaced by peer.
Status: Rejected (1)
RFC 6062, "Traversal Using Relays around NAT (TURN) Extensions for TCP Allocations", November 2010
Source of RFC: behave (tsv)
Errata ID: 3467
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Nazmus Shakeeb
Date Reported: 2013-01-22
Rejected by: Magnus Westerlund
Date Rejected: 2021-01-13
Section 5.2. says:
Otherwise, the server MUST initiate an outgoing TCP connection. The local endpoint is the relayed transport address associated with the allocation.
It should say:
Otherwise, the server MUST initiate an outgoing TCP connection. This connection MUST NOT be made using the relayed transport address associated with the allocation.
Notes:
if you send connect request using the allocated port then port the will not be in listen mode and this will prevent incoming tcp connection on this port.
this will cause major problem while doing ice check. The effect is so bad that
it may cause 97% call failure while using turn tcp behind nat.
--VERIFIER NOTES--
To my understanding this errata is due to implementation limitation or error. One those systems I have knowledge of you can create a TCP connection outgoing from the same TCP port that you have a listener.