<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>BGPsec on Nalar</title>
    <link>https://nalar.dev/tags/bgpsec/</link>
    <description>Recent content in BGPsec on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/bgpsec/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BGPsec Signs the AS Path Hop by Hop</title>
      <link>https://nalar.dev/bgpsec-signs-the-as-path-hop-by-hop/</link>
      <pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/bgpsec-signs-the-as-path-hop-by-hop/</guid>
      <description>&lt;p&gt;BGP route origin authorization protects one narrow statement: which AS may originate a prefix. It does not cryptographically protect every AS hop that appears after the origin. BGPsec, standardized in RFC 8205, addresses that separate boundary by carrying signed path information in BGP UPDATE messages.&lt;/p&gt;&#xA;&lt;p&gt;The mechanism changes more than the validation rule. A BGPsec UPDATE uses &lt;code&gt;BGPsec_PATH&lt;/code&gt; instead of the conventional &lt;code&gt;AS_PATH&lt;/code&gt;, and participating ASes extend a chain of Secure_Path and Signature Segments as the route moves between BGPsec-capable external peers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
