User Tools

Site Tools


network_stuff:irr

This is an old revision of the document!


IRR SANITATION SEE THIS ABOUTMANRS
\\https://panda314159.duckdns.org/doku.php?id=network_stuff:irr&do=edit This is a hands-on guide and this is the HE algorithm explained step by step Link

  • IRR fields (from ripe):
    • THESE ARE OBJECTS (big blocks) AND HAVE FIELDS: as-block, as-set, aut-num, domain, filter-set, inet6num, inetnum, inet-rtr, irt, key-cert, mntner, organisation, peering-set, person, poem, poetic-form, role, route, route6, route-set, rtr-set

For new acquisitions, remember to:

  • Add field
    • Fix the ROE so our ASN is authorized to send those prefixes (this is needed any time we start announcing new subnets (more specific ones))
  • We don't want ISPs to filter our PI between them due to strict IRR prefix filters on their BGP sessions
  • Issues with the IRR record (RPKI):

RPKI NOTES:

  • Tecords of the organisations act as Certification Authorities (CAs) in this PKI.

—-

In RIPE

  • RIPE=RIPE NCC
    • LIR: members of the RIPE NCC.
    • RIPE database (one of the several IRR in the world)
      • Uses Routing Policy Specification Language (RPSL)
      • route objects: When creating a route object you must authenticate against multiple maintainers

DOCUMENTING IRR:

  • Be sure each different site subnet (eg: /24) has a route object in IRR, otherwise it might be filtered between ISPs
  • Also ASN needs to have its RR ( eg; AS200981 is already a member of our AS-SET, AS-HURRICANE. )
  • And the export/advcertise policy

  • If you cannot update your autnum with an export statement for AS6939 , update peeringdb.com with your AS-SET: Record your AS-SET in the IRR as-set/route-set field.

https://www.peeringdb.com/

network_stuff/irr.1598360330.txt.gz · Last modified: (external edit)