[c-nsp] LDPv6 Census Check
Mark Tinka
mark.tinka at seacom.mu
Thu Jun 11 07:04:43 EDT 2020
On 11/Jun/20 12:54, Robert Raszuk wrote:
> No doubt.
>
> However one network is not equal the other. Especially SP/ISP network
> requirements and any to any traffic patterns there are very different
> from typical hub and spoke connectivity in the content or service
> serving enterprise.
Totally agree, which is why I said if you are building a backbone across
all continents, the ability of your hardware is the least of your problems.
You'll probably spend more time dealing with backbone and license issues.
>
> So if I am to put 1000 routers in the flat network, reduce OSPF timers
> and inject all 1000 BGP next hops with label to all 999 PEs while I
> only need 999 PEs to ever reach 10 next hops I would keep to argue
> flat IGP is not the right choice.
While I don't use OSPF, that almost sounds like something you'd do at an
EBC with a vendor in the lab.
Real networks may operate slightly less over-zealously :-).
But who knows, only time will tell. The problem is each time we seem to
reach the peak of what control planes can do, they up the ante.
If I was having this discussion with you 10 years ago, I'd be in total
agreement.
>
> Moreover as one of the best industry IGP developer and expert I highly
> respect stated very recently the end to end flooding time should stay
> below 200 ms. That is not your ICMP RTT ... that is time to receive
> the LSA/LSP to local RE, install in LSDB and send it back. That
> determines the flooding radius you should try not to exceed. And the
> time packet takes to even get from LC to RE is very platform dependent
> as I am sure most of you know very well :)
I won't diss the IGP developers, they help us to eat. But after being in
the game this long, I've often found that caution and real life don't
always align.
Naturally, we will take the considerations, and see what feedback we get
from the actual network, and adjust accordingly.
Mark.
More information about the cisco-nsp
mailing list