RFC 793:TRANSMISSION CONTROL PROTOCOL
RFC-Ref

address


Click on the red underlined text to get to the source

... communication facilities simultaneously, the TCP provides a set of addresses or ports within each host. Concatenated with the network ...
... network and host addresses from the internet communication layer, this forms ...
... made known to the public. These services can then be accessed through the known addresses. Establishing and learning the port addresses ...
... addresses. Establishing and learning the port addresses of other processes may involve more dynamic mechanisms. ...


... hosts anywhere in the internet system. These calls have parameters for passing the address, type of service, precedence, security, and other control information. ...
... independently by each TCP they might not be unique. To provide for unique addresses within each TCP, we concatenate an internet address ...
... unique addresses within each TCP, we concatenate an internet address identifying the TCP with a port ...
... sockets are a convenient mechanism for a priori associating a socket address with a standard service. For instance, the "Telnet ...
... Entry, Text Generator, Echoer, and Sink processes (the last three being for test purposes). A socket address might be reserved for access to a "Look-Up" service which would return the specific socket ...


... header carries several information fields, including the source and destination host addresses [2]. A TCP header follows the internet ...
... TCP header. This pseudo header contains the Source Address, the Destination Address, the Protocol, and TCP length. ...
... pseudo header contains the Source Address, the Destination Address, the Protocol, and TCP length. This gives the TCP ...
... +--------+--------+--------+--------+ | Source Address | +--------+--------+--------+--------+ | Destination Address ...
... Source Address | +--------+--------+--------+--------+ | Destination Address | +--------+--------+--------+--------+ | zero | PTCL | TCP ...
... state diagram in figure 6 illustrates only state changes, together with the causing events and resulting actions, but addresses neither error conditions nor actions which are not connected with state changes ...
... sequence number, control flags, and ACK field. Other fields such as window, addresses, lengths, and text have been left out in the interest of clarity. ...
... TCP identifiers for the source address will either be supplied by the TCP or the lower level protocol (e.g., IP ...
... SEND (local connection name, buffer address, byte count, PUSH flag, URGENT flag [,timeout]) ...
... SEND without ever explicitly knowing the foreign socket address. ...
... indications for different SENDs, it might be appropriate for the buffer address to be returned along with the coded response to the SEND request. TCP ...
... Format: RECEIVE (local connection name, buffer address, byte count) -> byte count, urgent flag, push flag ...
... Response String Always Buffer Address Send & Receive Byte count (counts bytes received) Receive Push flag Receive ...
... route information to be communicated. This is especially important so that the source and destination addresses used in the TCP checksum be the originating source and ultimate destination. It is ...
... Any lower level protocol will have to provide the source address, destination address, and protocol fields ...
... Any lower level protocol will have to provide the source address, destination address, and protocol fields, and some way to determine the "TCP ...


... Destination Address ...
... The destination address, usually the network and host identifiers. ...
... internet address ...
... A source or destination address specific to the host level. ...
... An address which specifically includes a port identifier, that ...
... identifier, that is, the concatenation of an Internet Address with a TCP port. ...
... Source Address ...
... The source address, usually the network and host identifiers. ...



Google
Web
RFC-Ref