From: David Miller <davem@davemloft.net>
To: tom@herbertland.com
Cc: laforge@gnumonks.org, tom@quantonium.net, pablo@netfilter.org,
aschultz@tpip.net, netdev@vger.kernel.org, rohit@quantonium.net
Subject: Re: [PATCH v7 net-next 00/13] gtp: Additional feature support - Part I
Date: Sun, 29 Oct 2017 10:49:31 +0900 (KST) [thread overview]
Message-ID: <20171029.104931.279145966336908779.davem@davemloft.net> (raw)
In-Reply-To: <CALx6S35R5hK8DMndXRcTHmapavdCFs5YDtdbca3yTznagNXqig@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Sat, 28 Oct 2017 11:37:51 -0700
> Customers are using IPv6!
Customers aren't using GTP with ipv6 the way you have implemented it.
Please stop weasel-wording the situation to frame it in a way that
purely benefits you and your objectives.
Also, just because "nobody has done the work", doesn't mean it's OK to
do the work improperly and then force that implementation upon people.
Harald is right, calling something GTP/ipv6 sets a certain expectation
with people who actually use GTP with ipv6 and have a deployment. No
matter if you mark it EXPERIMENTAL or whatever, the effect is the
same.
Therefore, I fully agree with Harald.
next prev parent reply other threads:[~2017-10-29 1:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 0:09 [PATCH v7 net-next 00/13] gtp: Additional feature support - Part I Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 01/13] vxlan: Move gro_cells_init to ndo_init Tom Herbert
2017-10-28 0:58 ` Eric Dumazet
2017-10-28 0:09 ` [PATCH v7 net-next 02/13] iptunnel: Add common functions to get a tunnel route Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 03/13] vxlan: Call common functions to get tunnel routes Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 04/13] gtp: Call common functions to get tunnel routes and add dst_cache Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 05/13] iptunnel: Generalize tunnel update pmtu Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 06/13] gtp: Change to use gro_cells Tom Herbert
2017-10-28 1:00 ` Eric Dumazet
2017-10-28 0:09 ` [PATCH v7 net-next 07/13] gtp: Use goto for exceptions in gtp_udp_encap_recv funcs Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 08/13] gtp: udp recv clean up Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 09/13] gtp: Call function to update path mtu Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 10/13] gtp: Eliminate pktinfo and add port configuration Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 11/13] gtp: Experimental encapsulation of IPv6 packets Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 12/13] gtp: Experimental support encpasulating over IPv6 Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 13/13] gtp: Allow configuring GTP interface as standalone Tom Herbert
2017-10-28 8:09 ` [PATCH v7 net-next 00/13] gtp: Additional feature support - Part I Harald Welte
2017-10-28 16:16 ` Tom Herbert
2017-10-28 16:47 ` Harald Welte
2017-10-28 18:37 ` Tom Herbert
2017-10-29 1:49 ` David Miller [this message]
2017-11-12 20:56 ` Harald Welte
2017-11-13 0:25 ` Tom Herbert
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=20171029.104931.279145966336908779.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aschultz@tpip.net \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rohit@quantonium.net \
--cc=tom@herbertland.com \
--cc=tom@quantonium.net \
/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