[address-policy-wg] About the /22 allocation limitation
- Previous message (by thread): [address-policy-wg] About the /22 allocation limitation
- Next message (by thread): [address-policy-wg] About the /22 allocation limitation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Ingvoldstad
frettled at gmail.com
Thu Apr 10 13:50:57 CEST 2014
On Thu, Apr 10, 2014 at 1:30 PM, Gert Doering <gert at space.net> wrote:Highly so. Depending on which vendor you used, "typical" gear deployed > about 5-7 years ago had a hard limit at 256.000 routes - and that came > quite close for a number of ISPs. The hardware upgrade to support 1 > million > routes did cost significant money (like, 10.000-50.000 EUR/router), and > it does not truly support "1 million IPv4" routes, if you also have IPv6 > and MPLS in your network - more like 700.000 IPv4 routes in typical > deployments. Now, before the big discussion starts: there is other > gear in the market that scales up to 2 million, etc., but I wanted to > point out that these are real-world hard limits, and the amount of > "headroom" > we have between "what is out there today" (500k) and "what some of the > fairly widely deployed core routers can do today" (700k) is not so big > that we want to risk an explosion by factor 2. > Ah, that was worse than I thought it was, by far. Thanks for the clarification! -- Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/address-policy-wg/attachments/20140410/0e8abffe/attachment.html>
- Previous message (by thread): [address-policy-wg] About the /22 allocation limitation
- Next message (by thread): [address-policy-wg] About the /22 allocation limitation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]