||12 Jul 2021 Plenary
||The discussion pointed out that it is possible to address the issue using Mask and Match capability along with a second stream filter for untagged traffic (e.g. use two filters). However, there is concern that requiring Mask and Match may be burdensome for certain implementations and it may be advantageous to make a change in 802.1CB to one of the basic stream filters by adding optional examination parameter. The preference in the group seems to be to make a change to 802.1CB to solve this problem rather than change 802.1Q. The group agrees a solution is desired, but there is some question whether this is a bug or enhancement request. A note in 802.1Q-2018 page 195 Note 2 implies this capability was expected, initial development of stream filters in 802.1Q intended them to be per-port, but this was changed later. This implies the issue is a bug, so processing this as a maintenance request is appropriate. The next vehicle for this is likely during SA ballot for CBcv and/or CBdb. The editors of those documents would prefer a complete solution, well documented, so it can easily be included during SA ballot. The group agreed to the following solution and actions: 1. Add optional wildcarding to 188.8.131.52 of IEEE Std 802.1CB.
2. Add warning to the aforementioned that full wildcarding is only useful for Qci.
3. Add a warning in IEEE Std 802.1Q to that wildcarded stream_handle with non-wildcarded priority matches frames from any port. Final proposed text to be developed within Maintenance and offline.
||Technical experts review