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/address-policy-wg@ripe.net/
[address-policy-wg] PI vs PA in routing table
- Previous message (by thread): [address-policy-wg] PI vs PA in routing table
- Next message (by thread): [address-policy-wg] RIPE NCC NRO Number Council Candidates Announced
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Max Tulyev
president at ukraine.su
Thu Sep 28 16:51:27 CEST 2006
Iljitsch van Beijnum wrote: > Ok a bit late but maybe this is useful: > > - there is no easy way to distinguish between a PI and a PA prefix RIPE (and other RIRs) DB? > - increase in RIR delegations last year was about 6%, increase in > advertised prefixes around 16% > > - there are less than 20000 AS numbers and some 180000 prefixes, so at > least 160000 of these prefixes aren't the result of multihoming as such > (although multihomers can also advertise more than one prefix for > traffic engineering reasons or no reason at all of course) > > (If multihoming is going to be a problem then look at AS numbers, the > ASes used by ISPs won't be significant in that case) This is not PI specific, as I can see. There is a lot of PA holders (LIRs) having just one uplink channel. -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- Previous message (by thread): [address-policy-wg] PI vs PA in routing table
- Next message (by thread): [address-policy-wg] RIPE NCC NRO Number Council Candidates Announced
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]