2004
DOI: 10.1109/mcom.2004.1362553
|View full text |Cite
|
Sign up to set email alerts
|

Internet protocol header compression, robust header compression, and their applicability in the global information grid

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
31
0

Year Published

2005
2005
2021
2021

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 30 publications
(33 citation statements)
references
References 7 publications
0
31
0
Order By: Relevance
“…To summarize, there is one small-scale FSM (Finite State Machine) describing the operation of the compression algorithm, while there is (another) large-scale FSM driving the movement between different modes. The interested reader is referred to [12], [13] for a more detailed treatment of these subjects.…”
Section: Header Compression Methodologymentioning
confidence: 99%
“…To summarize, there is one small-scale FSM (Finite State Machine) describing the operation of the compression algorithm, while there is (another) large-scale FSM driving the movement between different modes. The interested reader is referred to [12], [13] for a more detailed treatment of these subjects.…”
Section: Header Compression Methodologymentioning
confidence: 99%
“…However, our proposal does not formally use header compression techniques [3], but it only removes NOCHANGE fields. The compression of DELTA fields is not considered, since it would only provide a marginal increase of the savings, at the cost of the appearance of compressed headers with a variable size, the processing required for the compression and decompression of these fields, and the potential context desynchronization.…”
Section: A Removing Header Fields Present In the Openflow Tuplementioning
confidence: 99%
“…Header compression techniques able to save bandwidth for long-term flows using small packets through the public Internet were developed long ago [3]. They are based on the fact that many header fields are the same for every packet in a flow (NOCHANGE fields).…”
Section: Introductionmentioning
confidence: 99%
See 2 more Smart Citations