Connected: An Internet Encyclopedia
RFC 1122 - 4.2.2.1 Well-Known Ports: RFC-793 Section 2.7

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1122
Up: 4. TRANSPORT PROTOCOLS
Up: 4.2 TRANSMISSION CONTROL PROTOCOL -- TCP
Up: 4.2.2 PROTOCOL WALK-THROUGH
Prev: 4.2.2 PROTOCOL WALK-THROUGH
Next: 4.2.2.2 Use of Push: RFC-793 Section 2.8

### 4.2.2.1 Well-Known Ports: RFC-793 Section 2.7

DISCUSSION:

  TCP reserves port numbers in the range 0-255 for "well-known" ports, used to access services that are standardized across the Internet. The remainder of the port space can be freely allocated to application processes. Current well-known port definitions are listed in the RFC entitled "Assigned Numbers" [INTRO:6]. A prerequisite for defining a new well- known port is an RFC documenting the proposed service in enough detail to allow new implementations.

  Some systems extend this notion by adding a third subdivision of the TCP port space: reserved ports, which are generally used for operating-system-specific services. For example, reserved ports might fall between 256 and some system-dependent upper limit. Some systems further choose to protect well-known and reserved ports by permitting only privileged users to open TCP connections with those port values. This is perfectly reasonable as long as the host does not assume that all hosts protect their low-numbered ports in this manner.

Next: 4.2.2.2 Use of Push: RFC-793 Section 2.8

Connected: An Internet Encyclopedia
RFC 1122 - 4.2.2.1 Well-Known Ports: RFC-793 Section 2.7