<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
<channel>
<title>BGPexpert</title>
<link>http://www.bgpexpert.com/</link>
<language>en</language>
<description>News, opinions and resources from the inter-domain routing and IPv6 worlds</description>

<item>
  <title>32-bit AS numbers in the wild</title>
  <description>In january, Geoff Huston wrote to the &lt;a href="http://www.nanog.org/">NANOG&lt;/a> list:

&lt;blockquote>
George Michaelson, Randy Bush and myself have successfully tested the
implementation of 4Byte AS BGP on a public Internet transit. The 
above BGP RIB snapshot was taken at a 4Byte BGP speaker in North 
America, showing a transit path across AS 1221, AS 4637, AS 1239 and
AS 3130 , with correct reconstruction of the originating AS at the 
other (4Byte AS) end.
&lt;/blockquote>

At the time of this writing, their prefix is no longer visible in the global BGP table...</description>
  <link>http://www.bgpexpert.com/article.php?article=114</link>
  <pubDate>Sun, 10 Jun 2007 12:59:03 GMT</pubDate>
  <guid isPermaLink="false">114</guid>
</item>

<item>
  <title>BGP security: learning an old dog new tricks</title>
  <description>After lots of talk about S-BGP and soBGP over the past years, more recently, work in the IETF on making
inter-domain routing more secure has shifted to a different approach.
The relatively new secure inter-domain routing (sidr)
working group is now working on providing a public key infrastructure that makes it possible to link an IP prefix
to an origin AS with certificates. In the future, this mechanism may be used in S-BGP, soBGP or a similar mechanism, but
in the mean time, it allows generating and validating filters.</description>
  <link>http://www.bgpexpert.com/article.php?article=113</link>
  <pubDate>Sun, 10 Jun 2007 13:07:44 GMT</pubDate>
  <guid isPermaLink="false">113</guid>
</item>

<item>
  <title>Quagga</title>
  <description>As Zebra progress has been glacial, a group of people created a fork under the name &lt;a href=:"http://www.quagga.net/">Quagga&lt;/a>. Quagga is more community-based and a somewhat better choice than Zebra in an operational environment....</description>
  <link>http://www.bgpexpert.com/article.php?article=112</link>
  <pubDate>Tue, 30 Jan 2007 13:39:08 GMT</pubDate>
  <guid isPermaLink="false">112</guid>
</item>

<item>
  <title>OpenBGPD</title>
  <description>&lt;a href="http://www.openbsd.org/">OpenBSD&lt;/a>, the security conscious sibling in the BSD operating system family, has its own BGP daemon implementation: &lt;a href="http://www.openbgpd.org/">OpenBGPD&lt;/a>....</description>
  <link>http://www.bgpexpert.com/article.php?article=111</link>
  <pubDate>Tue, 30 Jan 2007 13:33:56 GMT</pubDate>
  <guid isPermaLink="false">111</guid>
</item>

<item>
  <title>IPv4 address use in 2006</title>
  <description>2006 was another busy year for the five Regional Internet Registries: together, they gave out 161.48 million IPv4 addresses, just shy of the 165.45 million given out in 2005 as measured on january first 2006.

Lots more information in the &lt;a href="http://bgpexpert.com/addrspace2006.php">2006 IPv4 Address Use Report&lt;/a>....</description>
  <link>http://www.bgpexpert.com/article.php?article=110</link>
  <pubDate>Mon, 01 Jan 2007 16:36:17 GMT</pubDate>
  <guid isPermaLink="false">110</guid>
</item>

<item>
  <title>32-bit AS numbers are here</title>
  <description>If you want to use the BGP routing protocol, you need an Autonomous System number. These AS numbers were 16 bits in size until now, allowing for around 64000 ASes, and more than half of those have been given out already. To avoid problems when we run out of AS numbers, the IETF came up with modifications to BGP to allow for 32-bit AS numbers, as I explained in &lt;a href="http://www.bgpexpert.com/article.php?id=105">a posting&lt;/a> about a year ago.
&lt;p>

Obviously, at some point someone has to bite the bullet and start using one of these new AS numbers. This bullet biting may happen fairly soon, as...</description>
  <link>http://www.bgpexpert.com/article.php?article=109</link>
  <pubDate>Fri, 29 Dec 2006 13:17:23 GMT</pubDate>
  <guid isPermaLink="false">109</guid>
</item>

<item>
  <title>Changing BGP TCP MD5 passwords</title>
  <description>The BGP TCP MD5 password mechanism
(&lt;a href="http://www.ietf.org/rfc/rfc2385.txt">RFC 2385&lt;/a>)
is very useful to protect BGP sessions from attempts at unpleasantness by third parties. However, it is rather simplistic.
One of the flaws is that there are no provisions for changing the password. In the old days, setting a new password for a
neighbor would cause Cisco routers to tear down and reestablish the BGP session. Today, the session survives if the password
or key is changed at more or less the same time at both ends. This requires a good deal of coordination. I must say that I can't
remem...</description>
  <link>http://www.bgpexpert.com/article.php?article=108</link>
  <pubDate>Sat, 30 Sep 2006 21:16:59 GMT</pubDate>
  <guid isPermaLink="false">108</guid>
</item>

<item>
  <title>Provider Independent IPv6 addresses</title>
  <description>Last week, &lt;a href="http://www.arin.net/">ARIN&lt;/a>, the organization in charge of distributing IP addresses in North America, changed its IPv6 address policy so it's now possible to get Provider Independent (PI) IPv6 address space.
&lt;p>

According to the &lt;a href="http://www.arin.net/policy/nrpm.html#six58">ARIN Number Resource Policy Manual&lt;/a>:
&lt;p>

&lt;hr>
To qualify for a direct assignment, an organization must:
&lt;p>
&lt;ol type=a>
&lt;li>not be an IPv6 LIR; and
&lt;li>qualify for an IPv4 assignment or allocation from ARIN under the IPv4 policy currently in effect.
&lt;/ol>
&lt;hr>
&lt;p>

This is both good news,...</description>
  <link>http://www.bgpexpert.com/article.php?article=107</link>
  <pubDate>Tue, 05 Sep 2006 10:30:41 GMT</pubDate>
  <guid isPermaLink="false">107</guid>
</item>

</channel>
</rss>
