Requested revision
Standard: | IEEE Std 802.1Q-2018 and IEEE Std 802.1Qcr-2020 | Clause: | 6.8.5.3 |
Clause title: | Stream filtering |
Rationale for revision
Stream filters with wildcard stream_handle specification and a
non-wildcard priority specification only allow definition of such stream
filters on a per Bridge component resolution due to the definition of
the managed objects (12.31).
Any Port association from the 802.1CB stream identification and indirectly
available via the stream_handle is lost for such stream filters, which
makes the definition of such stream filters questionable.
The only reason I can imagine for such stream filters would be some sort
of per class isolation for undersized switch fabrics, but this
a) was not the intent of PSFP and
b) is not an issue that needs to be addressed by IEEE Std 802.1Q.
However, just re-defining semantics could break backwards compatibility, so
this might not be an option.
Proposed text
Two options to DISCUSS, maybe more:
a) Support port + priority based stream identification in 802.1CB.
b) add a reception port specification to stream filters, that is either
a wildcard, meaning any port can match, or a port number.
Impact on existing networks
Backward compatibility can be retained in both aforementioned options.
Originator
Name: | Johannes Specht | Email: | johannes.specht.standards@gmail.com |
Affiliation: | Self | ||
Submitted: | 2021-02-22 |