On 10/Sep/20 21:09, aar...@gvtc.com wrote:
> Thanks for the heads up Mark... I see docs showing SRv6 not supported until
> XR 6.6, I put XR7 in my lab to start testing it...
I wasn't talking about SRv6... I am talking about SR-MPLS, signaled via
and supported for IPv6, in the IGP.
Mark.
>> Does anyone know the scope on why we have 2 names for this ?
>
> SPRING is the IETF working group name - Source Packet Routing in Networking
> Segment Routing is under SPRING
Yeah, sorry, this was my fault. Gotta have a catchy name.
As to "SPRINGv4" as others have said, this is not a
I found these threads about BGP Prefix-SID decoded needed for Wireshark.
Anyone know what wireshark version fixes this ? I just installed 3.2.6 and
that doesn’t seem to do it
https://www.wireshark.org/lists/wireshark-bugs/201603/msg00621.html
: sr - spring - what's the deal with 2 names
SR could be instantiated with 2 data planes, MPLS and IPv6 - SR-MPLS and SRv6
respectively.
MPLS data plane could be instantiated over either IPv4 or IPv6 (similarly to
LDP6), MPLSoUDP->SRoUDP allows transport of SR-MPLS over IP/UDP(RFC8
Thanks for the heads up Mark... I see docs showing SRv6 not supported until XR
6.6, I put XR7 in my lab to start testing it...
I have what seems to be a good test for vpnv4 mpls l3vpn over SRv6 IS-IS in core
This is my first go at this so still learning. Srv6 has a strange locator
thing with
I have described what SR is, not what vendors (for variety of reasons) do with
it, hence “could” ;-)
As a side note - SRoUDP works seamlessly over either v4 or v6.
Regards,
Jeff
> On Sep 10, 2020, at 12:35, Mark Tinka wrote:
>
>
>
>> On 10/Sep/20 10:40, Jeff Tantsura wrote:
>>
>> MPLS
On 10/Sep/20 10:40, Jeff Tantsura wrote:
> MPLS data plane could be instantiated over either IPv4 or IPv6
> (similarly to LDP6),
Be mindful of sketchy (or non-existent) IPv6 support in SR for IS-IS and
OSPF across all vendors.
Mark.
SR could be instantiated with 2 data planes, MPLS and IPv6 - SR-MPLS and SRv6
respectively.
MPLS data plane could be instantiated over either IPv4 or IPv6 (similarly to
LDP6), MPLSoUDP->SRoUDP allows transport of SR-MPLS over IP/UDP(RFC8663) and
could be used to build innovative, end2end
On Thu, Sep 10, 2020, at 08:08, aar...@gvtc.com wrote:
> Interesting... I've never heard of SPRINGv4
Neither did I until a few days ago.
> I wonder if SPRINGv4 is like SRv6, meaning, SPRING(SR) over IPv4 dataplane?
> Or, am I reading way too much into that SPRINGv4 acronym?
Like SR-VXLAN ?
Interesting... I've never heard of SPRINGv4
https://www.juniper.net/us/en/products-services/routing/ptx-series/datasheet
s/1000538.page
I found it in the bottom section
I wonder if SPRINGv4 is like SRv6, meaning, SPRING(SR) over IPv4 dataplane?
Or, am I reading way too much into that SPRINGv4
On Sun, Sep 6, 2020, at 10:14, Jeff Tantsura via NANOG wrote:
> Out of curiosity - if you are interested in SR, where are you getting
> your information from if not IETF (SPRING)?
Much beloved vendor claims support for "SPRINGv4" feature for a certain family
of products (I personally expect
Aaron,
Out of curiosity - if you are interested in SR, where are you getting your
information from if not IETF (SPRING)?
As for history - we (at Redback) have published 1st draft describing SR-MPLS
data plane in 2003 (LDP control plane).
Regards,
Jeff
> On Sep 6, 2020, at 09:53, Saku Ytti via
Hey,
On Sun, 6 Sep 2020 at 04:26, Aaron Gould via NANOG wrote:
> Does anyone know the scope on why we have 2 names for this ? Seriously, was
> it one of those things where a vendor started doing it first (pre-standard)
> as sr, and then ietf started standardizing it as spring ? …or was it
Please forgive if this has already been spoken to. if so, you can simply
send the link to old mail list entries and that will suffice. otherwise.
Does anyone know the scope on why we have 2 names for this ? Seriously, was
it one of those things where a vendor started doing it first
14 matches
Mail list logo
