How does it work?

There are DPE route servers which hold details of the routes exchanged at the DPE. These servers filter routes in two ways:

1. Incoming announcements are checked against individual filter lists for each peer.
   
2. Outgoing announcements are filtered to make sure that routes are not announced for RFC1918 addresses and other bogon or martian addresses.

The filter lists and other details of the route server configuration are built automatically from an RPSL database using the RtConfig tool from the IRRToolset. If you need to change the prefixes you want to announce you can use the Change DPE Route filters tool.

More information on using RPSL is available from the APNIC page About the APNIC Routing Registry. For a number of reasons we run our own Route Registry Database at present. The NZIX Route Registry data is available either by using a standard whois client connected to:

• whois.DPE.net.nz:43

or using a web based interface:

• NZIX Route Registry Database

You can examine the DPE routing policy by looking up the details for AS9560

A list of the Autonomous Systems connected to the route servers are given in the RPSL as-set object AS9560:AS-PUBLIC. These AS numbers have been assigned by one of the Regional Internet Registries such as APNIC.

Each AS has a list of networks they announce to the route servers given in an RPSL route-set object. For example, the numbers that CityLink announce to the DPE are given by AS9560:RS-ROUTES:AS23754 and incoming announcements are checked against filters constructed from these lists. If you are a DPE peer, you can check the list of networks that you are allowed to announce to the DPE by looking up the relevant route-set AS9439:RS-ROUTES:AS<YOUR_AS>. Please get in touch with us with any corrections.

The list of exported routes is checked against an RPSL filter-set called fltr-bogons which is constructed from two other filter-sets fltr-martian and fltr-unallocated Thanks to Rob Thomas at Team Cymru for these filters.