[c-nsp] LDPv6 Census Check

Mark Tinka mark.tinka at seacom.mu
Thu Jun 11 12:55:50 UTC 2020

On 11/Jun/20 14:17, adamv0025 at netconsultings.com wrote:

> Well RPKI or DNSSEC is at least adding a value, even something you can brag about to your customers (we are part of the solution not part of the problem etc...).

Bragging doesn't bring in income, it's just PR :-).

> But running MPLS over IPv6 in addition to already running it over IPv4, gaining new functionality or features in the process that could be ultimately monetized in providing better service to customers? -maybe even exposing the network to a new set of bugs?  -I don't know, that doesn’t sound like a good use of company resources especially in these uncertain times . Maybe I'm being overly harsh here maybe if you could please explain the drivers or expected net value out of this exercise please?  

Oh dear, you sound like our Finance department now; "drivers" and "net
value" :-).

If I take your line of reasoning, deploying SRv6 likely requires new
hardware, which means $$. How much money will I charge customers for my
shiny new SRv6?

LDPv6 builds on LDPv4. Just like IPv6 builds on IPv4. At best, you can
remove BGPv6 from your core, which lowers your administration costs in
that part of the network even further, costing you less in human time
running it, resources you can otherwise re-deploy to other time- and
money-saving activities. At worst, you get IPv4/IPv6 feature parity, and
who doesn't like that :-).

And how much money did LDPv6 cost you to deploy? $0.


More information about the NANOG mailing list