Hi,
I've just found a mistake in the text.
* An increase of Autonomous systems might not have as big of effect
on hardware requirements as one might think at first. Conservation
measures for cases presented in RFC1930 and *RFC2280 *and others
conserve only the AS number, and do not conserve the processing
power and memory needed to process the announced prefixes. When a
foreign prefix (e.g. PI) as announced (via e.g. private ASN) from
an AS (e.g. ISP) it still creates a separate entry in the routing
table.
Instead, I've meant RFC2270.
* An increase of Autonomous systems might not have as big of effect
on hardware requirements as one might think at first. Conservation
measures for cases presented in RFC1930 and *RFC2270 *and others
conserve only the AS number, and do not conserve the processing
power and memory needed to process the announced prefixes. When a
foreign prefix (e.g. PI) as announced (via e.g. private ASN) from
an AS (e.g. ISP) it still creates a separate entry in the routing
table.
Best,
Urban
-----
To unsubscribe from this mailing list or change your subscription options,
please visit:
https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the
email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
