From: Vincent JARDIN <vincent.jardin@6wind.com>
To: "Алексей Болдырев" <devel-net-ne-vlezay80@yandex.ru>,
netdev <netdev@vger.kernel.org>
Cc: David Lamparter <equinox@diac24.net>,
Amine Kherbouche <amine.kherbouche@6wind.com>
Subject: Re: MPLS Pseudowire (RFC3985) linux kernel support and development
Date: Thu, 6 Jul 2017 15:21:43 +0200 [thread overview]
Message-ID: <6b8ca117-ae0f-3cb9-0377-5ccb623155d5@6wind.com> (raw)
In-Reply-To: <1739851499332436@web8m.yandex.ru>
Le 06/07/2017 à 11:13, Алексей Болдырев a écrit :
> Is there any plan for developing mpls pseudowire dliver for linux. And also, is it possible to write a driver for MPLS pseudowire on the basis of tun / tap?
>
We are working on a RFC patch that should be available soon.
They'll be tested with FRR.
best regards,
next prev parent reply other threads:[~2017-07-06 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 9:13 MPLS Pseudowire (RFC3985) linux kernel support and development Алексей Болдырев
2017-07-06 13:21 ` Vincent JARDIN [this message]
2017-07-06 13:54 ` Алексей Болдырев
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=6b8ca117-ae0f-3cb9-0377-5ccb623155d5@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=amine.kherbouche@6wind.com \
--cc=devel-net-ne-vlezay80@yandex.ru \
--cc=equinox@diac24.net \
--cc=netdev@vger.kernel.org \
/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