Owen, Paying for IPv4 space definitely raises the capital requirements for any new provider startup. It's not so bad right now, when deals are plentiful in the $10k to $20k range for /24s. But when a /24 hits $100K, bootstrapping a new ISP will be impossible. -mel beckman
On Jul 8, 2015, at 12:32 PM, Owen DeLong <owen@delong.com> wrote:
I think the “THING” that people are starting to worry about is how to deploy a network when you can’t get IPv4 space for it at a reasonable price.
Owen
On Jul 8, 2015, at 11:47 , Mark Tinka <mark.tinka@seacom.mu> wrote:
On 8/Jul/15 17:59, Mel Beckman wrote: Greg,
After investigating what a previous poster said about Cisco and Juniper, I'm getting the feeling that not all major impediments to running MPLS over IPv6-only networks have been addressed.
Your comment mentions LDP IPv6 support. Do you now handle all the major gaps identified the the IETF MPLS IPv6 Gap Analysis (RFC7439) from this last January?
https://tools.ietf.org/html/rfc7439#section-3
It seems like their are still gaps in the MPLS spec itself before IPv6 has parity with IPv4 in MPLS.
The LDPv6 support is just the control plane portion to get labels assigned to IPv6 addresses. This should get you basic forwarding of encapsulation and forwarding of IPv6 traffic in MPLS. The immediate use-case would be removal of IPv6 BGP routing in the core, if that is your thing.
Otherwise, yes, there are still a bunch of MPLS gaps that need to be fixed for those additional services to run natively over an IPv6-only network. Baby steps...
Mark.