Thread (9 messages) flat view 9 messages, 5 authors, 2014-07-15

Re: [PATCH 1/2 net-next] vxlan: Be liberal on receive and only require the I bit to be set

From: Nicolas Dichtel <hidden>
Date: 2014-07-15 07:18:05

Le 14/07/2014 10:18, Thomas Graf a écrit :
On 07/13/14 at 03:08pm, Tom Herbert wrote:
quoted
On Fri, Jul 11, 2014 at 9:59 AM, Thomas Graf [off-list ref] wrote:
quoted
The VXLAN receive code is currently conservative in what it accepts and
will reject any frame that uses any of the reserved fields. The VXLAN
draft specifies that "reserved fields MUST be set to zero on transmit
and ignored on receive." though.

Be liberal in only requiring the I bit to allow for VXLAN extensions
to be implemented.
This is not robust (this is a problem in the VXLAN spec not your
patch). There is no requirement that the VXLAN bits are optional. For
example, if a receiver accepts a GPE packet but doesn't implement it
the packet will be misinterpreted. I've already pointed this out to
the VLXAN folks on nvo3 list. Dropping packets with unknown bits set
is the only sane approach.
I agree, it's a mess.
+1
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help