RFC 793:TRANSMISSION CONTROL PROTOCOL
RFC-Ref

network


Click on the red underlined text to get to the source

... host-to-host protocol between hosts in packet-switched computer communication networks, and in interconnected systems of such networks. ...
... between hosts in packet-switched computer communication networks, and in interconnected systems of such networks. ...
... As strategic and tactical computer communication networks are developed and deployed, it is essential to provide means of interconnecting them and to provide standard interprocess ...
... connection-oriented, end-to-end reliable protocol designed to fit into a layered hierarchy of protocols which support multi-network applications. The TCP provides for reliable inter-process ...
... communication between pairs of processes in host computers attached to distinct but interconnected computer communication networks. Very few assumptions are made as to the reliability of the communication ...
... wide spectrum of communication systems ranging from hard-wired connections to packet-switched or circuit-switched networks. ...
... addressing source and destination TCPs in different networks. The internet protocol also deals with any fragmentation ...
... transport and delivery through multiple networks and interconnecting gateways. The internet protocol ...
... segments, so this information can be communicated end-to-end across multiple networks. ...
... internet protocol | +---------------------+ |communication network| +---------------------+ ...
... which are co-resident with higher level protocols in the host computer. Some computer systems will be connected to networks via front-end computers which house the TCP ...
... TCP and internet protocol layers, as well as network specific software. The TCP specification describes an interface ...
... TCP is intended to be a host-to-host protocol in common use in multiple networks. ...
... interface. TCP is designed to work in a very general environment of interconnected networks. The lower level protocol which is assumed throughout this document is the Internet Protocol [2 ...
... addresses or ports within each host. Concatenated with the network and host addresses ...


... The internetwork environment consists of hosts connected to networks which are in turn interconnected via gateways. It is assumed here ...
... which are in turn interconnected via gateways. It is assumed here that the networks may be either local networks (e.g., the ETHERNET) or ...
... gateways. It is assumed here that the networks may be either local networks (e.g., the ETHERNET) or large networks ...
... networks (e.g., the ETHERNET) or large networks (e.g., the ARPANET), but in any case are based on packet switching technology. The active ...
... agents that produce and consume messages are processes. Various levels of protocols in the networks, the gateways, and the hosts support an interprocess ...
... transaction between a host and its network. The format of data blocks exchanged within the a network will generally not be of concern to us. ...
... host and its network. The format of data blocks exchanged within the a network will generally not be of concern to us. ...
... Hosts are computers attached to a network, and from the communication network's point of view, are the sources and destinations ...
... Hosts are computers attached to a network, and from the communication network's point of view, are the sources and destinations of packets. Processes are viewed as the active ...
... TCP which provides an interface to the local network. This internet module packages TCP segments ...
... gateway. To transmit the datagram through the local network, it is embedded in a local network packet. ...
... datagram through the local network, it is embedded in a local network packet. ...
... At a gateway between networks, the internet datagram is "unwrapped" ...
... internet datagram is "unwrapped" from its local packet and examined to determine through which network the internet datagram ...
... internet datagram is then "wrapped" in a local packet suitable to the next network and routed to the next gateway, or to the final destination ...
... datagram fragments if this is necessary for transmission through the next network. To do this, the gateway produces a set of internet ...
... internet module) to guide it in selecting the service parameters to be used in traversing the next network. Included in the type of service information is the precedence of the ...
... data structures. The actual interface to the network is assumed to be controlled by a device driver module. The TCP does not call on the ...
... controlled by a device driver module. The TCP does not call on the network device driver directly, but rather calls on the internet datagram ...
... | +---------------------------+ | Local Network Protocol | Network Level +---------------------------+ ...
... +---------------------------+ | Local Network Protocol | Network Level +---------------------------+ ...
... create a socket which will be unique throughout all networks connected together. ...


... Internet Protocol and is transferred across the TCP/Network interface in the arguments or results of calls by the TCP on the IP ...
... connection from being used while the same sequence numbers may still be present in the network from an earlier incarnation. We want to assure this, even if a TCP crashes and loses all knowledge of the ...
... microseconds. Thus, the ISN cycles approximately every 4.55 hours. Since we assume that segments will stay in the network no more than the Maximum Segment Lifetime ...
... handshake is necessary because sequence numbers are not tied to a global clock in the network, and TCPs may have different mechanisms for picking the ISN's. The receiver of the first SYN ...
... sequence number which may be duplicated by an old segment remaining in the network, the TCP must keep quiet for a maximum segment lifetime ...
... sequence number space each time a segment is formed and entered into the network output queue at a source host. The ...
... packets with sequence numbers identical to or overlapping with packets still in the network which were emitted on an earlier incarnation of the same connection. In the absence of knowledge ...
... segment at B from A. Left arrows (<--), indicate the reverse. Ellipsis (...) indicates a segment which is still in the network (delayed). An "XXX" indicates a segment which is lost or rejected. ...
... Case 2: TCP receives a FIN from the network ...
... If an unsolicited FIN arrives from the network, the receiving TCP ...
... segments may be lost due to errors (checksum test failure), or network congestion, TCP uses ...
... segment. Duplicate segments may arrive due to network or TCP retransmission. ...
... Because of the variability of the networks that compose an internetwork system and the wide range of uses of TCP connections ...
... in excessive retransmissions, adding unnecessarily to the load on the network and the TCPs. Indicating a small window may restrict the transmission of data to the point of introducing a round trip delay ...
... connection specified. Depending upon the implementation of the TCP, the local network and TCP identifiers ...
... performance, so it is not recommended. A more sophisticated implementation would return immediately to allow the process to run concurrently with network I/O, and, furthermore, to allow multiple SENDs to be in progress. Multiple SENDs are served in first come, first served order, so ...
... The TCP calls on a lower level protocol module to actually send and receive information over a network. One case is that of the ARPA internetwork system where the lower level module is the Internet Protocol ...


... A message sent in a packet switched computer communications network. ...
... 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. ...
... The unit of transmission within a local network. ...
... The source address, usually the network and host identifiers. ...


... Cerf, V., and R. Kahn, "A Protocol for Packet Network Intercommunication", IEEE Transactions on Communications, Vol. COM-22, No. 5, pp 637-648, May 1974. ...
... Connection Management in Transport Protocols", Computer Networks, Vol. 2, No. 6, pp. 454-473, December 1978. ...



Google
Web
RFC-Ref