2000
DOI: 10.17487/rfc2757
|View full text |Cite
|
Sign up to set email alerts
|

Long Thin Networks

Abstract: In view of the unpredictable and problematic nature of long thin networks (for example, wireless WANs), arriving at an optimized transport is a daunting task. We have reviewed the existing proposals along with future research items. Based on this overview, we also recommend mechanisms for implementation in long thin networks.Our goal is to identify a TCP that works for all users, including users of long thin networks. We started from the working recommendations of the IETF TCP Over Satellite Links (tcpsat) wor… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
36
0

Year Published

2001
2001
2012
2012

Publication Types

Select...
4
4
2

Relationship

0
10

Authors

Journals

citations
Cited by 69 publications
(36 citation statements)
references
References 17 publications
0
36
0
Order By: Relevance
“…The calculated BDP values are around 2 kB and 7 kB for 31.5 kbit s −1 and 158 kbit s −1 data rates, respectively. With those BDP values, L-DACS 1 can be classified as a "Long Thin Network" [38]. The table also shows the protocol overhead for TCP (20 B), IPv6 (40 B), and L-DACS 1 (7 B) for different MSS values.…”
Section: Bandwidth Delay Product Calculationmentioning
confidence: 99%
“…The calculated BDP values are around 2 kB and 7 kB for 31.5 kbit s −1 and 158 kbit s −1 data rates, respectively. With those BDP values, L-DACS 1 can be classified as a "Long Thin Network" [38]. The table also shows the protocol overhead for TCP (20 B), IPv6 (40 B), and L-DACS 1 (7 B) for different MSS values.…”
Section: Bandwidth Delay Product Calculationmentioning
confidence: 99%
“…Vendors are encouraged to follow the algorithms in RFC 2988 [26] when implementing TCP retransmission timers. Vendors of systems designed for low-bandwidth, high-delay links should consult RFCs 2757 and 2488 [24], [25]. Designers of applications targeted to operate on mobile nodes should be sensitive to the possibility of timer-related difficulties.…”
Section: Code Values For Mobile Ip Registration Reply Messagesmentioning
confidence: 99%
“…When the peer specifies its own IP address, that address MUST NOT be assumed to be a foreign agent care-of address or the IP address of a home agent. [28,1]. Designers of applications targeted to operate on mobile nodes should be sensitive to the possibility of timer-related difficulties.…”
Section: B Link-layer Considerationsmentioning
confidence: 99%