From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Stefano Salsano <stefano.salsano@uniroma2.it>,
Andrea Mayer <andrea.mayer@uniroma2.it>,
netdev@vger.kernel.org
Cc: "David S . Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Paolo Lungaroni <paolo.lungaroni@uniroma2.it>,
Ahmed Abdelsalam <ahabdels@cisco.com>,
Justin Iurman <justin.iurman@6wind.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next 0/3] seg6: SRv6 L2 VPN with End.DT2U and srl2 device
Date: Tue, 31 Mar 2026 16:00:59 +0200 [thread overview]
Message-ID: <b586ea61-8a70-4367-b26e-a88644d944d7@6wind.com> (raw)
In-Reply-To: <56dca998-220c-4c29-bf3d-2a94292d6d32@uniroma2.it>
Le 27/03/2026 à 02:09, Stefano Salsano a écrit :
[snip]
>> What is the gain of having two interfaces?
>> In term of scalability, it is interesting to have only one interface.
>
> among our medium-term design goals we have:
>
> 1) achieving the feature parity with vxlan
> 2) being at least isomorphic with vxlan in terms of exposed CLI mechanisms
>
> in this way we can port the existing vxlan based solution for cloud
> infrastructures and container networking to srv6
>
> on top of this, we can design srv6 specific machinery for higher efficiency
>
> therefore, the bridge+sr6 solution has to be supported to achieve feature
> parity/isomorphism with vxlan
>
> on top of this, we also include a solution that does not need the bridge and
> terminates an L2 tunnel directly into a single sr6 interface characterized by a
> mac address (this is for the decap side)
Make sense, thanks for the details.
>
> for the encap side, we are considering per-mac solutions (see our answer to
> Justin) in a way which is aligned with vxlan design for the reasons mentioned above
Ok.
Regards,
Nicolas
prev parent reply other threads:[~2026-03-31 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 0:05 [RFC PATCH net-next 0/3] seg6: SRv6 L2 VPN with End.DT2U and srl2 device Andrea Mayer
2026-03-22 0:05 ` [RFC PATCH net-next 1/3] seg6: add support for the SRv6 End.DT2U behavior Andrea Mayer
2026-03-22 0:05 ` [RFC PATCH net-next 2/3] seg6: add SRv6 L2 tunnel device (srl2) Andrea Mayer
2026-03-24 16:08 ` Justin Iurman
2026-03-24 16:24 ` Justin Iurman
2026-03-25 13:43 ` Justin Iurman
2026-03-26 17:29 ` Stefano Salsano
2026-03-26 16:44 ` Nicolas Dichtel
2026-03-31 0:59 ` Andrea Mayer
2026-03-22 0:05 ` [RFC PATCH net-next 3/3] selftests: seg6: add SRv6 srl2 + End.DT2U L2 VPN test Andrea Mayer
2026-03-24 16:00 ` [RFC PATCH net-next 0/3] seg6: SRv6 L2 VPN with End.DT2U and srl2 device Justin Iurman
2026-03-25 7:10 ` Stefano Salsano
2026-03-25 8:35 ` Justin Iurman
2026-03-26 16:30 ` Nicolas Dichtel
2026-03-26 17:30 ` Stefano Salsano
2026-03-26 16:32 ` Nicolas Dichtel
2026-03-27 1:09 ` Stefano Salsano
2026-03-31 14:00 ` Nicolas Dichtel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b586ea61-8a70-4367-b26e-a88644d944d7@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=ahabdels@cisco.com \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=justin.iurman@6wind.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paolo.lungaroni@uniroma2.it \
--cc=stefano.salsano@uniroma2.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox