An IRR database commonly contains route objects of several different types, each serving a distinct purpose. The RIPE database operated by the
RIPE NCC mainly uses the primary object types listed below, containing information regarding Internet resources and forming the primary purpose of the IRR. Apart from these, the database also defines several less commonly used primary object types, and secondary object types, which contain administrative information. Other IRR databases use the same or equivalent object types. • AUT-NUM: Represents an
Autonomous System (AS) number. Also includes the AS-level routing policy defined by the AS, which may be used to perform BGP path validation. • AS-SET:
AS Sets, mainly used for simplifying routing policies defined in AUT-NUM objects. • INETNUM: Represents an
IPv4 prefix, and includes information on which organization this prefix is assigned or allocated to. • INETNUM6: Represents an
IPv6 prefix. • ROUTE: Associates IPv4 prefixes (INETNUM objects) with ASNs. This association is used as the basis for BGP route origin validation based on IRR data. • ROUTE6: Associates IPv6 prefixes (INETNUM6 objects) with ASNs. • DOMAIN: Contains the
authoritative name servers handling the
reverse DNS delegation for an IP prefix, along with related information. ==See also==