Caitlin> It's basically the same as with TCP and UDP. It's a 16
Caitlin> bit number, and most people do not use the same port
Caitlin> number to mean *different* things over the different IP
Caitlin> transports.
But, just to be clear, the port number spaces are disjoint. It's
possible and valid to have one TCP socket bound to a given IP/port
number, and another UDP socket bound to the same IP/port number.
I do agree that assigned port numbers generally have the same meaning
across all transports. For example, both TCP port 111 and UDP port
111 are the sunrpc portmapper.
- R.
_______________________________________________
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
