On the other hand, verify is cheaper. My crappy laptop will do ~320k RSA-2048 verifications per second...
350 per core per second... you are way off at 100k/s.
If there is such a thing I'd really like to see setup to get it running / try it out myself as well.
do note there are ways to cache ssl data so connections are resumed / avoid handshake again for same user
60k/second across 24 cores, admittedly on very fast hardware (though not using all the cores that hardware has). Pretty much the same number on 16 cores.
In general, telling someone they're "way off" about performance and citing 6 year old benchmarks isn't a winning plan.
In any case, it's immaterial to what we're discussing. My slow laptop could verify all the signatures for a busy day of updates in a couple seconds, and it's clearly -possible- to put a big fraction of this horsepower in a router.
Apologize for the 'way off', its reach-able.
And agree its immaterial to signature checks, but since it was brought up...
Either way, there is probably something holding routers back from reaching that, would be fun to speculate.
The BGPSEC theory is there but not sure if we can make a workable system.
https://www.potaroo.net/ispcol/2011-07/bgpsec.pdf