This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] New NWI for geofeed?
- Previous message (by thread): [db-wg] New NWI for geofeed?
- Next message (by thread): [db-wg] New NWI for geofeed?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Massimo Candela
massimo at us.ntt.net
Thu May 6 20:27:00 CEST 2021
Hi Hank, On 06/05/2021 07:18, Hank Nussbacher via db-wg wrote: > What if you have a /16 as recorded by inetnum: as well as an RPKI > certificate for that /16 but within the /16 there is a /24 that has been > assigned to some other ASN? Can you publish a geofeed file for the /16? > What if there is no inetnum: listed for that /24 yet in the global BGP > tables there is an announcement of that /24 from a different ASN - would > you still accept the geofeed announcement for the /16 based on inetnum: > and RPKI cert? ASNs and BGP announcements do not come into play. If a /16 inetnum has a geofeed link, the pointed file can specify entries covering the /16. If a /24 inetnum with geofeed link exists, this takes priority for that /24 portion. RPKI signature (optional) can be used -after- the inetnum hierarchy is resolved to verify ownership of the prefix. Ciao, Massimo
- Previous message (by thread): [db-wg] New NWI for geofeed?
- Next message (by thread): [db-wg] New NWI for geofeed?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]