https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/L2SWITCH-37 l2switch <p>The yang definitions for Ethernet packet have only the (mostly) Cisco specific Q-n-Q nested tag definition. </p> <p>This is a pre-standard form for provider bridging, the standard is different. </p> <p>As a result, this will not work versus Linux and may or may not work versus white box silicon and other vendors which comply to the Ethernet 802.1ad standard as specified in 802.1ad.</p> <p>The yang model should also include the ad tag for nested vlans - 0x88a8.</p> <p>Operating System: All<br/> Platform: All</p> L2SWITCH-37

Missing ID for IEEE standard 802.1ad

Bug Resolved Done Unassigned Anton Ivanov Wed, 18 Mar 2015 10:37:44 +0000 Thu, 19 Oct 2017 21:28:15 +0000 Wed, 9 Sep 2015 13:43:37 +0000 unspecified General 0 0 <p>After re-reading the model, this is a bit more convoluted.</p> <p>1. There is an ethertype for 802.1ad mentioned in the yang model, however it is not in use. It is not part of the header8021q-type definition.</p> <p>2. header8021q-type misses the mentioning of 802.1ad ethertype</p> <p>3. The model is too weak - it does not enforce header field order.</p> <p> 3.1. The first header is either a 802.1ad or 802.1q. If it is 802.1q there are no subsequent headers<br/> 3.2. If the first header is 802.1ad and the standard is followed strictly the second header must be 802.1q (some equipment allows multiple stacking).</p> <p>4. The partial easy fix is to add 802.1ad to the enum - this will enable it in the packet handler. I will submit a patch to that effect shortly.</p> <p>5. We need to tighten up the model a bit in order for builders, etc to function correctly and as expected (based on model) by the consumers.</p> <p>Partial fix.</p> <p>The yang model is too lose to enforce some of the finer points of Ethernet header ordering so we only allow the correct header type here. We do not limit it to perform ordering checks (f.e. - 802.1q can presently be insterted before an ad header which is an incorrect combination).</p> Development External issue ID 2865 External issue URL Rank 0|i01z5j: