Rand, D., "PPP Reliable Transmission", RFC 1663, July 1994.  Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
IP-in-IP Tunneling to Enable the Simultaneous Use of.. - Phatak, Goff.. (2003) (Correct)
....in varying contexts and for different applications and scenarios, distinct from those considered in this paper. For instance, multilink PPP [1, 2, 3] is designed to aggregate multiple logical data channels into one. Since PPP was intended to operate at the data link layer, below the IP level [4, 5, 6], the multi link PPP extension bundles multiple data link level channels into a single logical link. In the scenario we are considering, links have different IP addresses assigned and controlled by completely independent Internet Service Providers (ISPs) It is highly unlikely that independent ....
D. Rand, PPP Reliable Transmission, July 1994. RFC 1663.
Unified Transport Layer Support for Data Striping and Host.. - Goff, Phatak (2003) (Correct)
....in varying contexts and for scenarios and applications distinct from those considered in this paper. For instance, multi link PPP [10] 11] is designed to aggregate multiple logical data channels into one. Since PPP was intended to operate at the data link layer, below the IP level [12] 13] [14], the multi link PPP extension bundles multiple data link level channels into a single logical link. So called layer two tunneling using L2TP [15] does allow PPP to operate over packet switched networks. IP and TCP can then operate over the bundled logical PPP channel, which accomplishes the same ....
D. Rand, PPP Reliable Transmission, July 1994, rFC 1663.
Inverse Multiplexing for Reliable Transport in Wide-Area Wireless .. - Snoeren (1999) (Correct)
....evidence shows the selection of an appropriate transport mechanism is critical to achieving acceptable performance. The fundamental design decision is whether to provide reliable transport and or congestion control. This can be done through a reliable PPP connection, built using Numbered Mode [Ran94], or by tunneling PPP over a reliable transport protocol. While arguments can be made for either choice, we claim an unreliable mechanism is superior in the multi link environment, as it allows us to dispense with link layer congestion control, and reduces jitter in packet reassembly. This follows ....
....not retransmitting duplicate fragments after an occasional loss event. We return, then, to an unreliable transport layer. 4.1.2 Retransmission Instead, we present a scheme to realize the savings of link layer retransmission in the absence of a reliable transport mechanism. In PPP Numbered Mode [Ran94], the multiplexor tags each fragment with an identifier. We propose to extend it with a hash of the flow ID and TCP sequence number, allowing the demultiplexor to associate it with a particular TCP packet even if reassembly fails. Then, when the end to end TCP requests a packet retransmission, the ....
D. Rand. PPP Reliable Transmission. July 1994. RFC 1663.
Unknown - Self-citation (Rand) (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, July 1994.
Network Working Group D. Rand Request for Comments: 1962.. - Status Of This Self-citation (Rand) (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, July 1994.
Network Working Group K. Schneider Request for Comments: 1967 .. - Status Of This (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, Novell, July 1994.
Network Working Group G. Meyer Request for Comments: 1968.. - Status Of This (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, Novell, July 1994.
Unknown - Status Of This (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, July 1994.
Network Working Group G. Pall Request for Comments: 2118.. - Status Of This (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, Novell, July
Unknown - (1990) (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, Novell, July 1994
Unknown - (1993) (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, Novell, July
Unknown - Status Of This (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, July 1994.
Network Working Group R. Friend Request for Comments: 1974.. - Status Of This (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, Novell, July 1994. Chair's Address The working group can be contacted via the current chair:
Unknown - (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", PPP Extensions Working Group, Work in Progress.
Unknown - (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, July 1994.
Unknown - (Correct)
No context found.
Rand, D., "PPP Reliable Transmission", RFC 1663, July 1994. Chair's Address The working group can be contacted via the current chair: Karl Fox Ascend Communications 3518 Riverside Drive, Suite 101 Columbus, Ohio 43221 EMail: karl@ascend.com Authors' Addresses Questions about this memo should be directed to:
An Architecture for Adaptable Wireless Networks - Rao (2000) (Correct)
No context found.
D. Rand, RFC 1663, "PPP Reliable Transmission", Networking Working Group, 1994.
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