Skip to content
rule 11 reader
  • about
    • about me
    • mailing list
    • author page
    • rss feeds
  • reading
    • technology books
    • skills books
    • fiction books
    • philosophy & culture books
    • christian books
    • papers
    • worth reading
  • categories
    • career
      • career
      • design skills
      • communication skills
      • education
      • soft skills
      • troubleshooting skills
    • coding
    • complexity
    • culture
    • ddos
    • ipv6
    • other technologies
    • research
    • reviews
    • routing
      • bgp
      • bgp security
      • eigrp
      • is-is
      • ospf
      • mpls
      • other routing
    • security
    • standards
    • worth reading
    • content type
      • long video
      • long audio
      • short video
      • written
    • other
      • governance
      • humor
    • archive
  • the hedge
  • history
  • resources
    • my goodreads
    • my feedly
    • network icons
  • photos

Rethinking BGP path validation (part 2)

This is the second post in the two part series on BGP path validation over on the LinkedIn Engineering blog.

We left off last time after having described the eight operational requirements that must be met for any system that reduces our reliance on transitive trust in relation to the AS Path. As a reminder, AS, or Autonomous Systems, is a set of routers which all follow a standard set of policies. A typical AS is run by a single organization, such as a company or an ISP. Now, let’s see how this kind of system might work in practice.

Related

Posted in BGP, ON THE NET, SECURING BGP, WRITTEN
← Should We Stop Encryption? Can We?Yokohama →
© 2023 rule 11 reader | Powered by Beaver Builder
Scroll To Top