Hi Mostafa Ali, there isn't any common limit (aka fixed number) for a number of route objects an ISP can maintain/introduce in the RIPE DB. To be precise, there is a limited IP and AS resource pool and a limited number of integral pieces IP resource pool can be sliced into that makes for a limited number of IP range + AS number combinations. However, one has to pass a few checks to successfully create a new or modify an existing route object: http://www.ripe.net/info/faq/db/route-creation-checks.html http://www.ripe.net/info/faq/db/main.html#13 There is also a couple of route object related questions within an ISP FAQ: http://www.ripe.net/info/faq/rs/isp.html Keep in mind it's a good practise to aggregate route objects if possible (same AS origin and neighboring IP address space within power of two bounds) so as not to impose unnecessary burden on the routing table size. Best regards, Martin Stanislav On Tue, Aug 23, 2005 at 12:28:55PM +0300, Mostafa Ali wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear Colleagueas ,
I would like to know if there is a alimit for the number of route objects for an AS coreessponding to an ISP .
Mostafa Ali Nile Online , Cairo Office Egypt
-----BEGIN PGP SIGNATURE----- Version: PGP 5.5.5
iQA/AwUBQwrQMZvTGM8GJVhQEQLp/gCgwxk6XJ2RPFpS7qdtHP9bWpn3qL4An2Se hPxkdDlt413WSRrS48Rc8hwp =TNPD -----END PGP SIGNATURE-----