RFC 793:TRANSMISSION CONTROL PROTOCOL
RFC-Ref

destination


Click on the red underlined text to get to the source

... datagram provides a means for addressing source and destination TCPs in different networks. The internet protocol ...


... network, and from the communication network's point of view, are the sources and destinations of packets. Processes are viewed as the active elements ...
... internet module to transmit each segment to the destination TCP. The receiving TCP ...
... internet datagrams and routes these datagrams to a destination internet module or intermediate gateway ...
... other operations to achieve the delivery of the local packet to the destination internet module. ...
... network and routed to the next gateway, or to the final destination. ...
... internet datagram fragment format is designed so that the destination internet module can reassemble fragments ...
... A destination internet module unwraps the segment from the datagram ...
... (after reassembling the datagram, if necessary) and passes it to the destination TCP. ...
... stream of data sent on a TCP connection is delivered reliably and in order at the destination. ...


... header carries several information fields, including the source and destination host addresses [2]. A TCP header ...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source Port | Destination Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sequence Number ...
... port number. Destination Port: 16 bits ...
... 16 bits The destination port number. Sequence Number ...
... pseudo header contains the Source Address, the Destination Address, the Protocol, and TCP length. This gives the TCP ...
... Source Address | +--------+--------+--------+--------+ | Destination Address | +--------+--------+--------+--------+ | zero | PTCL | TCP ...
... Hosts which prefer to avoid waiting are willing to risk possible confusion of old and new packets at a given destination may choose not to wait for the "quite time". Implementors may provide TCP users ...
... no data in return need only wait to hear the connection was CLOSED successfully to know that all his data was received at the destination TCP. Users must keep reading connections ...
... octet. If the sending user also indicates a push, timely delivery of the urgent information to the destination process is enhanced. ...
... for all data submitted to TCP. If data is not successfully delivered to the destination within the timeout period, the TCP will abort the connection ...
... If the URGENT flag is set, segments sent to the destination TCP will have the urgent pointer set. The receiving ...
... SEND calls, followed by a CLOSE, and expect all the data to be sent to the destination. It should also be clear that users should continue to RECEIVE on CLOSING connections, since the other side ...
... TCP (e.g., remote close executed, transmission timeout exceeded, destination inaccessible). ...
... 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 ...
... so that the source and destination addresses used in the TCP checksum be the originating source and ultimate destination. It is also important to preserve the return route to answer connection ...
... 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. ...
... A computer. In particular a source or destination of messages from the point of view of the communication network. ...
... A source or destination address specific to the host level. ...
... A program in execution. A source or destination of data from the point of view of the TCP or other host-to-host ...



Google
Web
RFC-Ref