Connected: An Internet Encyclopedia
RFC 1122 - 4.2.2.18 Passive OPEN Calls: RFC-793 Section 3.8

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.17 Probing Zero Windows: RFC-793 Section 3.7, page 42
Next: 4.2.2.19 Time to Live: RFC-793 Section 3.9, page 52

### 4.2.2.18 Passive OPEN Calls: RFC-793 Section 3.8

Every passive OPEN call either creates a new connection record in LISTEN state, or it returns an error; it MUST NOT affect any previously created connection record.

A TCP that supports multiple concurrent users MUST provide an OPEN call that will functionally allow an application to LISTEN on a port while a connection block with the same local port is in SYN-SENT or SYN-RECEIVED state.

DISCUSSION:

  Some applications (e.g., SMTP servers) may need to handle multiple connection attempts at about the same time. The probability of a connection attempt failing is reduced by giving the application some means of listening for a new connection at the same time that an earlier connection attempt is going through the three- way handshake.

IMPLEMENTATION:

  Acceptable implementations of concurrent opens may permit multiple passive OPEN calls, or they may allow "cloning" of LISTEN-state connections from a single passive OPEN call.

Next: 4.2.2.19 Time to Live: RFC-793 Section 3.9, page 52

Connected: An Internet Encyclopedia
RFC 1122 - 4.2.2.18 Passive OPEN Calls: RFC-793 Section 3.8