Gyan, In SR-MPLS, either over IPv4 or IPv6 the data-plane is MPLS (rfc8660) If MPLS is tunneled over IP, e.g MPLS over GRE, MPLS over UDP, etc, then data-plane is that of outer encapsulation - rfc8663 as the best example, e.g outer header would be IPv4/IPv6+UDP Since bindings (SIDs) need to be distributed, you’d need a label distribution protocol, with IPv6 that would be IS-IS, OSPFv3 or BGP (or controller based). Vendor support for that is rather limited, I don’t recall any. Other option to distribute label bindings over IPv6 would be LDPv6 + v6 IGP, I recall Junos implementation, there could be more. There’s quite interesting discussion on NANOG - https://mailman.nanog.org/pipermail/nanog/2020-June/208111.html
Hope this helps Cheers, Jeff On Jun 23, 2020, 1:52 PM -0700, Gyan Mishra <hayabusa...@gmail.com>, wrote: > > > Thanks Ron! > > Gyan > > > On Tue, Jun 23, 2020 at 3:51 PM Ron Bonica <rbon...@juniper.net> wrote: > > > Gyan, > > > > > > You can signal SR-MPLS over a network that has IPv6 enabled, but does not > > > have IPv4 enabled. > > > > > > Ron > > > > > > > > > > > > Juniper Business Use Only > > > From: spring <spring-boun...@ietf.org> On Behalf Of Gyan Mishra > > > Sent: Tuesday, June 23, 2020 1:20 PM > > > To: SPRING WG <spring@ietf.org> > > > Subject: [spring] Spring SR question?? > > > > > > [External Email. Be cautious of content] > > > > > > > > > All > > > > > > SR-MPLS utilizes IPv4 data plane and and can service v4 v6 edges 6to4 > > > softwire mesh framework from the VPN overlay aspect.. > > > > > > Can SR-MPLS use IPV6 data plane? > > > > > > Reason why I am asking is that it is very simple to get from LDPv4 core > > > to SR-MPLS core. > > > > > > However if you have an existing brown field SP core and your end goal is > > > to get to SRv6 - how can you easily get there. > > > > > > So my thoughts are you can use SR-MPLS as a stepping stone so to speak to > > > get to SRv6. > > > > > > To that end you could use Greg Mirsky draft of tunneling SR-MPLS in SRV6 > > > interoperability and use other inter operability drafts. > > > > > > But let’s say you prefer to get from point A go point B seamlessly and > > > native naturally without any translation. > > > > > > An analogy would be migratory to IPV6 instead of using translation > > > technology tunnels you dual stand the entire network and use ds-lite or > > > LSN or 6RD to close the gap. > > > > > > So my thoughts on getting to the “end state” SRv6 are we follows: > > > > > > MPLS LDPv4 > > > > > > MPLS LDPv6 > > > > > > SR-MPLS v6 > > > > > > Once you have a v6 core and you have decommissioned LDPv6 you now have > > > the v6 data plan ready to go to get to SRv6 > > > > > > SRv6 > > > > > > Only caveat with this idea is I am not sure if SR-MPLS supports IPv6 data > > > plane v6 label binding. > > > > > > > > > Kind Regards > > > > > > Gyan > > > > > > -- > > > Gyan Mishra > > > Network Solutions Architect > > > M 301 502-1347 > > > 13101 Columbia Pike > > > Silver Spring, MD > > > > -- > > Gyan Mishra > Network Solutions Architect > M 301 502-1347 > 13101 Columbia Pike > Silver Spring, MD > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
