CiteSeerX — Table search results

Results 1 - 10 of 8,996

TABLE II SYSLOG MESSAGES MOST RELEVANT TO BGP SESSION FAILURE

in Understanding BGP Session Failures in a Large ISP

by Lan Wang, Malleswari Saranu

Table 3: Message size. The increase numbers are based on the message size by original BGP.

in Evaluating the Performance Impact of PKI on BGP Security

by Meiyuan Zhao, Sean W. Smith, David M. Nicol

"... In PAGE 9: ... S- BGP is next, again, because of shorter signature length. Our experiment results, shown in Table3 , confirm that S- A generates the longest messages. For both S-BGP and S- A, number of signatures in messages grows as the length of path increases.... ..."

Table 3: Message size. The increase numbers are based on the message size by original BGP.

in Evaluating the Performance Impact of PKI on BGP Security Abstract

by Meiyuan Zhao, Sean W. Smith, David M. Nicol

Table 1. BGP synchronization convergence

in Parallel Network Simulation under Distributed Genesis

by Boleslaw K. Szymanski, Yu Liu, Rashim Gupta 2003

"... In PAGE 6: ... We measured the convergence of the synchronization in Genesis for BGP networks with 10, 15 and 20 AS domains. Table1 shows the number of re- iterations needed in Genesis to converge during the BGP message burst, and the number of BGP messages exchanged by each AS simulator. It should be noted that the number of needed iterations grows sublinearly with the number of domains, so slower then the number of messages, which are... ..."

Cited by 14

Table 2. The average BGP convergence time and the average number of update messages for various numbers of reusable MRAI timers.

in The duration of the Minimal Route Advertisement

by unknown authors

"... In PAGE 7: ...ig. 5. Effect of MRAI on the down phase: (a) convergence time and (b) the number of update messages. The average BGP convergence time and the average number of reusable MRAI timers for the down phase are shown in Table2 . The number of reusable MRAI timers determines the granularity of MRAI and the minimum duration of the adaptive MRAI round.... ..."

TABLE II PROCESSING ORDER OF THE IBGP MESSAGES INSIDE AS1 AFTER THE TRANSMISSION OF A BGP WITHDRAW

in Achieving Sub-50 Milliseconds Recovery Upon BGP Peering Link Failures

by unknown authors

Table 3: BGP updates with non-monotonic preference changes. Stage Routing tables New messages Preference

in Damping BGP route flaps

by Zhenhai Duan, Jaideep Chandrashekar, Jeffrey Krasky, et al. 2004

"... In PAGE 4: ... After all the nodes enter a steady state regarding the route to node a25 , edge a56 a80a82a74a105a25a39a57 is down. Table3 presents the subsequent BGP updates sent from node a104 to node a106 , in a format similar to [8]. The table has four columns.... ..."

Cited by 1

Table 3: Information about BGP data collected from net- works where eight of our testbed hosts are located.

in Measuring the Effects of Internet Path Faults on Reactive Routing

by Nick Feamster, David G. Andersen, Hari Balakrishnan, M. Frans Kaashoek 2003

"... In PAGE 3: ... 2.3 BGP data collection The eight testbed hosts shown in boldface in Table3 collected BGP messages. The hosts ran Zebra 0.... ..."

Cited by 60

Table 3: Information about BGP data collected from net- works where eight of our testbed hosts are located.

in Measuring the Effects of Internet Path Faults on Reactive Routing

by Nick Feamster, David G. Andersen, Hari Balakrishnan, M. Frans Kaashoek

"... In PAGE 3: ... 2.3 BGP data collection The eight testbed hosts shown in boldface in Table3 collected BGP messages. The hosts ran Zebra 0.... ..."

Table III describes our cache hit ratios. The cache that stores COMMUNITY information from the raw BGP update messages has a 99% hit rate. The resulting file size was only 100K instead of the expected 126M. This clearly indicates the importance of using a cache.

in BGP-Inspect - Extracting Information from Raw BGP Data

by Dionysus Blazakis 2006

Cited by 3

Results 1 - 10 of 8,996

Tools

TABLE II SYSLOG MESSAGES MOST RELEVANT TO BGP SESSION FAILURE

Table 3: Message size. The increase numbers are based on the message size by original BGP.

Table 3: Message size. The increase numbers are based on the message size by original BGP.

Table 1. BGP synchronization convergence

Table 2. The average BGP convergence time and the average number of update messages for various numbers of reusable MRAI timers.

TABLE II PROCESSING ORDER OF THE IBGP MESSAGES INSIDE AS1 AFTER THE TRANSMISSION OF A BGP WITHDRAW

Table 3: BGP updates with non-monotonic preference changes. Stage Routing tables New messages Preference

Table 3: Information about BGP data collected from net- works where eight of our testbed hosts are located.

Table 3: Information about BGP data collected from net- works where eight of our testbed hosts are located.

Table III describes our cache hit ratios. The cache that stores COMMUNITY information from the raw BGP update messages has a 99% hit rate. The resulting file size was only 100K instead of the expected 126M. This clearly indicates the importance of using a cache.