J. Postel. Transmission Control Protocol, RFC--761. USC Information Sciences Institute, January 1980. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
Why Use a Fishing Line When You Have a Net? - An Adaptive Multicast (Correct)
....over TCPbased programs such as rdist. For example, our system has been used to distribute a 133 Kbyte password file to 68 hosts in 20 seconds, whereas the equivalent rdist took 251 seconds. I Introduction Distributing data to multiple hosts using connection oriented protocols such as TCP [1] can be inefficient because the data must be transmit ted over the network multiple times, once to each target. Popular file distribution programs, including rcp, rdist, and track [2] are all based on this protocol. The time they require to distribute files to a group of machines is proportional ....
Jon Postel. Transmission Control Protocol. RFC 793, USC/Information Sciences Insti- tute, September 1981.
IEEE International Conference on Web Delivering of Music.. - The Recording Studio (Correct)
....very tightly bound to particular applications rather than appearing in reusable toolsets or kernel modules. As to control packets, we have shifted from the approach of our earlier protocol, which made limited use of TCP [4] for the handling of resend requests and retransmissions, to using raw UDP [5] for everything. Upon reflection, the use of TCP for retransmission handling was rather nave. Packet loss is usually a sign of network congestion, a condition that causes TCP to activate its congestion avoidance mechanism [3] Under conditions of mild congestion, this means a higher than usual ....
Postel, J. User datagram protocol. RFC 768, USC/Information Sciences Institute, Aug. 1980.
IEEE International Conference on Web Delivering of Music.. - The Recording Studio (Correct)
....benefitted much, given that RTP implementations, unlike TCP, are typically very tightly bound to particular applications rather than appearing in reusable toolsets or kernel modules. As to control packets, we have shifted from the approach of our earlier protocol, which made limited use of TCP [4] for the handling of resend requests and retransmissions, to using raw UDP [5] for everything. Upon reflection, the use of TCP for retransmission handling was rather nave. Packet loss is usually a sign of network congestion, a condition that causes TCP to activate its congestion avoidance ....
Postel, J. Transmission control protocol. RFC 793, USC/Information Sciences Institute, Sep. 1981.
Some Lessons From Using Static Analysis and Software Model.. - Musuvathi, Engler (2003) (6 citations) (Correct)
....the model checks if a packet generated by the implementation has a valid checksum. To check the implementation for protocol compliance, the model simultaneously runs a TCP reference model along with the implementation. The reference model performs the basic state machine transitions described in [34]. The model provides the same inputs to both the implementation and the reference model and checks if their states are consistent.CMC reports any inconsistency as a protocol violation error. 5.3 Measuring the Search Effectiveness Even after a working environment model is built, one problem still ....
....All are instances where the implementation fails to meet the TCP speci cation. These errors are fairly complex and require an intricate sequence of events to trigger the error. The following is a brief description of two of the bugs CMC found. While a detailed understanding of the TCP protocol [34] is required to completely understand these bugs, the purpose of the description below is to provide a general avor of errors CMC is able to nd. The rst bug involves the processing of RST (reset) packets. A RST packet is used to indicate an abnormal close of a connection. In response to a RST ....
J. Postel. Transmission control protocol. RFC 793, USC/Information Sciences Institute, September 1981.
Real Time Streaming of Multi-channel Audio Data over Internet .. - Aoxiang Xu And (2000) (1 citation) (Correct)
....an Internet. The fundamental difference between AFDP and our application is that the former is not bound by real time constraints. For a streaming audio application, we are willing to trade a small amount of reliability in exchange for real time performance. 3. 1 Network Protocols TCP [4] and UDP [5] are the dominant network protocols used for computer communication. TCP, a connection oriented, reliable, and full duplex protocol, uses an acknowledgement and retransmission scheme to guarantee delivery of data. If a segment is not acknowledged by the receiver, the sender will continue to ....
J. Postel. User datagram protocol. RFC 768, USC/Information Sciences Institute, Aug. 1980.
Real Time Streaming of Multi-channel Audio Data over Internet .. - Aoxiang Xu And (2000) (1 citation) (Correct)
....hosts on an Internet. The fundamental difference between AFDP and our application is that the former is not bound by real time constraints. For a streaming audio application, we are willing to trade a small amount of reliability in exchange for real time performance. 3. 1 Network Protocols TCP [4] and UDP [5] are the dominant network protocols used for computer communication. TCP, a connection oriented, reliable, and full duplex protocol, uses an acknowledgement and retransmission scheme to guarantee delivery of data. If a segment is not acknowledged by the receiver, the sender will ....
J. Postel. Transmission control protocol. RFC 793, USC/Information Sciences Institute, Sep. 1981.
Finding and Containing Enemies Within the Walls With.. - Ganger, Economou.. (2003) (1 citation) (Correct)
....things can be identified by its self securing NI, which sees what enters and leaves the host when. As a concrete example, this section describes a scanner for SYN bomb attacks. What the scanner looks for: A SYN bomb attack exploits a characteristic of the state transitions within the TCP protocol [29] to prevent new connections to the victim. The attack consists of repeatedly initiating, but not completing, the three packet handshake of initial TCP connection establishment, leaving the target with many partially completed sequences that take a long time to time out. Specifically, an attacker ....
J. Postel. Transmission Control Protocol, RFC--761. USC Information Sciences Institute, January 1980.
A Fail-Aware Datagram Service - Fetzer, Cristian (1998) (7 citations) (Correct)
....sometimes it is advantageous that processes also receive slow messages. Hence, we classify messages as slow or fast and leave it to the clients whether they drop slow messages. The fail aware datagram protocol we propose is implementable on top of a conventional datagram service, like UDP [18]. The calculation of the upper bound on the transmission delay of a message relies on the main idea which underlies probabilistic remote clock reading [1] namely that by measuring round trip message delays one can calculate upper bounds on one way transmission delays. 3 Each message that the ....
..... In our specification we do not want to exclude service implementations that drop some late messages to shed the load during high load situations. Another reason for not requiring that all late fa messages be delivered is that UDP does not guarantee that a message is delivered at most once [18]: to enforce at most once delivery semantics, the information that a message has already been delivered has to be kept for only time units when the service drops all messages . 8 Protocol In this section, we propose a protocol for the fail aware datagram service. The validity and ....
J. Postel. User datagram protocol. Technical Report RFC768, USC / Information Sciences Institute, 1980.
Anytime Information Theory - Sahai (2001) Self-citation (Institute) (Correct)
No context found.
J. Postel, \Transmission Control Protocol", RFC 793, USC/Information Sciences Institute, September 1981 (http://www.ietf.org/rfc/rfc0793.txt)
Anytime Information Theory - Sahai (2001) Self-citation (Institute) (Correct)
No context found.
J. Postel, \Transmission Control Protocol", RFC 793, USC/Information Sciences Institute, September 1981 (http://www.ietf.org/rfc/rfc0793.txt)
Unknown - Self-citation (Rfc) (Correct)
No context found.
Reynolds, J., and J. Postel. Assigned Numbers. RFC 870, USC/Information Sciences Institute, October, 1983.
Unknown - Self-citation (Datagram) (Correct)
No context found.
Postel, J. User Datagram Protocol. RFC 768, USC/Information Sciences Institute, August, 1980.
Darmstadt Un I Vers I Ty - Of Department Of Self-citation (Information) (Correct)
No context found.
Jon Postel, Transmission Control Protocol (TCP), USC/Information Sciences Institute, Request for Comments: 793, 1981
Unknown - Self-citation (Reynolds) (Correct)
No context found.
Postel, J., and J. Reynolds, "File Transfer Protocol (FTP), STD 9, RFC 959, USC/Information Sciences Institute, October 1985.
Unknown - Self-citation (Reynolds) (Correct)
No context found.
Postel, J., and J. Reynolds, "File Transfer Protocol (FTP), RFC 959, USC/Information Sciences Institute, October 1985.
Design and Implementation of Secure Tapping Alert Protocol - Ahn, Kim (2001) Self-citation (Protocol Information) (Correct)
No context found.
J. Postel, \Internet Protocol", RFC 760, USC/Information Sciences Institute, Jan. 1980.
A Multi-protocol Campus Time Server - Snow (1991) Self-citation (Protocol) (Correct)
No context found.
J. Postel, `Transmission control protocol, RFC-793, USC Information Sciences Institute, 1981.
Applications - Stanley Bielski Of (Correct)
No context found.
J. Postel. Transmission Control Protocol, RFC--761. USC Information Sciences Institute, January 1980.
Network Working Group J. Mindel - Request For Comments (Correct)
No context found.
Postel, J., and J. Reynolds, "File Transfer Protocol (FTP), STD 9, RFC 959, USC/Information Sciences Institute, October 1985.
Model Checking Large Network Protocol Implementations - Musuvathi, Engler (2004) (5 citations) (Correct)
No context found.
J. Postel. Transmission control protocol. RFC 793, USC/Information Sciences Institute, September 1981.
Unknown - (Correct)
No context found.
Postel, J. File Transfer Protocol. RFC 765, USC/Information Sciences Institute, June, 1980.
Network Working Group G. Kessler Request for Comments: 1739.. - Status Of This (Correct)
No context found.
Postel, J., and J. Reynolds, "File Transfer Protocol (FTP), STD 9, RFC 959, USC/Information Sciences Institute, October 1985.
Cmc: A Model Checker For Network Protocol Implementations - Musuvathi (2004) (Correct)
No context found.
J. Postel. Transmission Control Protocol. RFC 793, USC/Information Sciences Institute, September 1981.
Design and Implementation of Secure Tapping Alert Protocol - Ahn, Kim (2001) (Correct)
No context found.
J. Postel, \User Datagram Protocol", RFC 768, USC/Information Sciences Institute, Aug. 1980.
Design and Implementation of Secure Tapping Alert Protocol - Ahn, Kim (2001) (Correct)
No context found.
J. Postel, \Transmission Control Protocol", RFC 761, USC/Information Sciences Institute, Jan. 1980.
First 50 documents Next 50
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC