netdev - Re: [PATCH] vlan: Make it possible to add vlan with id 4095

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.01.1211122128300.24241@nerf07.vanv.qr>
Date:	Mon, 12 Nov 2012 21:37:48 +0100 (CET)
From:	Jan Engelhardt <jengelh@...i.de>
To:	Ben Greear <greearb@...delatech.com>
cc:	David Miller <davem@...emloft.net>, paulius.zaleckas@...il.com,
	kaber@...sh.net, netdev@...r.kernel.org
Subject: Re: [PATCH] vlan: Make it possible to add vlan with id 4095


On Monday 2012-11-12 20:01, Ben Greear wrote:
>>>
>>> Awesome, we don't need VXVLAN any more after this fix.
>>
>> You mean because the special 0xfff value could indicate "here's more
>> headers"? Sounds like a plan.
>
> You can't just use reserved values...

Indeed not; I was just implicitly thinking of the 802.1Q standard
comittee getting an impetus from the public disgust against VXVLAN to
define 0xfff with extensions that allow for e.g. stacking, making
VXVLAN redundant and obsolete. :)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html