Archive for bgp category:
IXP Bake Off Results
Comments Off
Here are some slides that present some research undertaken by a number of European Internet Exchange points (IXPs), which I presented at UKNOF15 last week. They may be of interest to networks which connect to IXPs who have been considering connecting to the local multi-lateral peering (MLP) service, but are unsure whether testing has proved [...]
IPv6 Track at NANOG
Leave a Comment
Greetings from Philadelphia! I am presenting as part of the IPv6 at NANOG46 (click here for info of how to watch) at 9:30PM UK time today, or download the IPv6 for Enterprises presentation here, or see information about the other speakers here..
The messages are clear and simple. Working now to get ready for the IPv6 [...]
IPv4 Run-out policies in Europe
Leave a Comment
There are a few policy suggestions pushing their way through the RIPE policy development process which discuss how the final remaining IPv4 addresses should be given to end users in the European region.
They all show that the effects of scarsity of IP addresses will be felt before the final few addresses become assigned to end [...]
18 months? And google are nimble?
Leave a Comment
Google recently announced that they’d done a front-to-back implementation of IPv6, using engineers’ spare time, in 18 months. Cue well over 100 comments on slashdot claiming that this goes to show how hard implementing any sort of v6 service is at all, given it takes a company known for hiring smart people as long as [...]
The internet is still broken, guys…
Leave a Comment
I complained on December 10th 2008 that The Internet was broken for 4-byte ASN speakers. Rob Shakir, Jonathan Oddy, and I have been researching in detail the mechanism by which a faulty announcement by an end-site network in the Ukraine was able to break BGP (the protocol that glues different networks on the internet together, [...]
Internet broken for ASN32 speakers today.
4 Comments
Not trying to point fingers or name-and-shame, just to raise the profile of a nasty little bug handling breaches of RFC4893. This post is basically shaped from a message I posted to nanog earlier.
AS196629 (3.21 in asdot) announce 91.207.218.0/23. Experienced eyes will notice that this is quite a large as number. It’s a ‘new’ 4-byte [...]
