From: Jiri Benc <jbenc@redhat.com>
To: netdev@vger.kernel.org
Cc: Yi Yang <yi.y.yang@intel.com>, Eric Garver <e@erig.me>,
Jan Scheurich <jan.scheurich@ericsson.com>,
Ben Pfaff <blp@ovn.org>
Subject: Re: [PATCH net-next 3/4] net: add NSH header structures and helpers
Date: Tue, 29 Aug 2017 19:10:49 +0200 [thread overview]
Message-ID: <20170829191049.2d7f53e1@griffin> (raw)
In-Reply-To: <4abd24a9ec958622186efacb4e46d709831fbaae.1503948295.git.jbenc@redhat.com>
On Mon, 28 Aug 2017 21:43:23 +0200, Jiri Benc wrote:
> This patch adds NSH header structures and helpers for NSH GSO
> support and Open vSwitch NSH support.
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-sfc-nsh/
One thing to know before applying this to the kernel: NSH is still a
draft. It's not standardized yet. And the draft evolves, compare the
version from February to the latest one:
https://tools.ietf.org/html/draft-ietf-sfc-nsh-12#section-3.2
https://tools.ietf.org/html/draft-ietf-sfc-nsh-19#section-2.2
There's really no guarantee there won't be further changes.
This patchset by itself is harmless as there's no user and everything
can be changed. We should think through any uAPIs we're going to merge,
though. We don't want to repeat the problems with VXLAN and changed UDP
port.
Again, this patchset is harmless and can be applied even if the draft
changes. Further patches may not be and need to be designed very
carefully.
Jiri
next prev parent reply other threads:[~2017-08-29 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 19:43 [PATCH net-next 0/4] nsh: headers, GSO Jiri Benc
2017-08-28 19:43 ` [PATCH net-next 1/4] ether: add NSH ethertype Jiri Benc
2017-08-28 19:43 ` [PATCH net-next 2/4] vxlan: factor out VXLAN-GPE next protocol Jiri Benc
2017-08-28 19:43 ` [PATCH net-next 3/4] net: add NSH header structures and helpers Jiri Benc
2017-08-29 17:10 ` Jiri Benc [this message]
2017-08-28 19:43 ` [PATCH net-next 4/4] nsh: add GSO support Jiri Benc
2017-08-29 22:17 ` [PATCH net-next 0/4] nsh: headers, GSO David Miller
2017-08-30 5:23 ` Yang, Yi
2017-08-30 7:20 ` Jiri Benc
2017-08-30 7:19 ` Yang, Yi
2017-08-30 7:44 ` Jiri Benc
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=20170829191049.2d7f53e1@griffin \
--to=jbenc@redhat.com \
--cc=blp@ovn.org \
--cc=e@erig.me \
--cc=jan.scheurich@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=yi.y.yang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.