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] getting second IPv6 PA as a LIR
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Lenz
slz at baycix.de
Wed May 4 10:06:39 CEST 2011
Hay, Am 04.05.2011 um 09:49 schrieb <poty at iiat.ru> <poty at iiat.ru>: [...] > Sascha Lenz [SLZ-RIPE] > ---------------------- > Small companies start with small routers, PC based Linux Quagga Boxes, > or Routerboards, > or Juniper J-Series or whatever - not really much costs here (see other > replies). > -------------- > > They will not be able to "start with small routers", because calculating > constantly changing routes (presumable from several sources) costs > processing power, routing decisions with huge routing table cost > processing power, even receiving and sending plain packets costs > processing power. And all this costs money. PC-based routers are not > able to do all of this at once and in this anount. > The "selfish" small ISPs could easily drive himself into trap of trouble > when they have to spent much more money for equipment (and made all > others do it) rather than using PA from LIR. > > do you have any numbers on that? because i don't see it. Even my old Pentium4 route servers do very nicely with that. And look at the processing power of the Route Engines of the hardware routers... wow are they slow! So, where does this come from? Will there be a break even point where current CPUs won't handle that anymore? My bigger problem with that actually is FORWARDING, not route calculation. The only reason i have hardware routers with ASICS is the wirespeed throughput, they still all have low-end CPU route engines for route calculation.... (But yes, slower CPUs == bringing up a BGP session takes 20min or so, we know that) And unfortunately i just now notices that this drifts a bit off topic. -- Mit freundlichen Grüßen / Kind Regards Sascha Lenz [SLZ-RIPE] Senior System- & Network Architect
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]