Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #27235

Closed (moved)
(moved)
Open
Created Aug 21, 2018 by nusenu@nusenu

add route_origin_rpki_validity field

motivation:

  • bring routing security awareness and indicators to relay operators
  • increase routing security by encouraging relay operators to ask their ISPs for properly configured prefixes

context: https://medium.com/@nusenu/how-vulnerable-is-the-tor-network-to-bgp-hijacking-attacks-56d3b2ebfd92

this field should contain the following information:

  • RPKI ROA validity state for IPv4 and IPv6 (enum: NotFound, Invalid, Valid)
  • invalid reason for IPv4 and IPv6 (enum: 'as', 'length')

validator software by RIPE (alternatively you can use RIPEstat, but running it yourself is likely a lot faster) https://www.ripe.net/manage-ips-and-asns/resource-management/certification/tools-and-resources

depends on: #27155 (moved)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking