Geek Answers Handbook

Are there any protocol specifications that allow the use of TCP or UDP?

Are there any network protocols that are not strictly TCP or UDP, but can be used with one of them?

For example, HTTP, FTP, STMP, RTMP are always TCP.

DNS, SNMP, DHCP, RIP are always UDP.

Is there anything that could be TCP or UDP? Or am I mistaken in the above statements?

RTSP is one of the strangest I know that uses both: TCP for the control port, but UDP for audio / video / quality, but it has strict requirements for what is sent from each.

I ask about standard, published, or at least commonly used protocols, not user-defined ones.

+4
source share
5 answers

If you look at the Windows services file, you will see several protocols registered for both TCP and UDP. Path: C:\Windows\System32\drivers\etc In fact, most of the lists in the services file use the TCP and UDP protocols.

As well-known applications that use both, I think most chat applications use both. sms-chat definitely does, but probably most others do.

Edit:

From this file, there are several protocols that can be sent via TCP or UDP (there are exactly 100 of the listed protocols that use both the file and many internal MS protocols):

  • echo
  • dropping
  • day
  • qotd (Quote of the day)
  • charger (character generator)
  • Time
+2
source

DNS can use UDP or TCP; TCP is required when response data exceeds 512 bytes.

+4
source

SIP can use UDP, TCP or SCTP. Using reliable transport becomes important in SIP if your messages become generally large (i.e. significantly larger than the smallest MTU between user agents). Good examples are views with shared or bridge lines that use a presence form with XML bodies. The larger the number of SIP clients in the shared line group, the more packets there will be, which can lead to fragmentation and retransmission.

+2
source

SIP can be either UDP or TCP. However, the reality is that UDP is mainly used for this protocol.

+1
source

SNMP almost always works on top of UDP, but it can and does work over TCP. The theory says that it is a bad idea to do SNMP with regard to error correction transport, because some of the errors that SNMP intends to detect are masked.

+1
source

More articles:


All Articles