2006
DOI: 10.1007/11942634_116
|View full text |Cite
|
Sign up to set email alerts
|

Analyzing Correlation Between Flow Data and AS Paths in BGP Routing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2011
2011
2011
2011

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 3 publications
0
2
0
Order By: Relevance
“…Even if short signatures where used (e.g., 200 bits) and the average end-to-end autonomous system hop count of 5 [46] existed within the overlay, every e-mail packet would end up with an additional 200 byte overhead, by the time it reached its destination.…”
Section: A Zero-trust Non-repudiation Protocolmentioning
confidence: 99%
“…Even if short signatures where used (e.g., 200 bits) and the average end-to-end autonomous system hop count of 5 [46] existed within the overlay, every e-mail packet would end up with an additional 200 byte overhead, by the time it reached its destination.…”
Section: A Zero-trust Non-repudiation Protocolmentioning
confidence: 99%
“…Given that the Autonomous System (AS) Number is 32 bits long, this would add 32 + 119 = 151 bits to the packet per hop. With a common AS path length of about 5 [25], this yields 246 + (5 * 119) = 841 bits, or 106 bytes. The destination mail servers have to store these packets for a certain period of time, to be able to facilitate a complaint under the peer-to-peer protocol.…”
Section: Overheadmentioning
confidence: 99%