well this is not so simple. The accepted prefix length depends on the address range. It reflects more or less the registry assignements. Be aware however, that each AS is first of all autonomous. So in principle you could to whatever you like with respect to IP routing, aggregation and the like. There are however some best practices and also good will is needed otherwise internet is not operational ;-)
In case you want to look for yourself into BGP routers of different ISPs then have a look at traceroute.org and follow the link to Route Servers.
best practice is to announce the IP address blocks the way you get them from the registry. So 100.100.0.0/16 would be announced to the peering partners.
This will not cause any harm to the customer, because you will not be able to announce Sprint IP addresses through another (decent) ISP anyhow. And within the sprint network the detailed routes are present in BGP. Aggregation is done when peering "to the internet".
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...