802.1 Tools
  • Home
  • Maintenance
    • All items
    • Open items
    • Closed items
    • Items for review
    • Status
  • Meetings
  • Help
  • Log in
Requested revision
Standard:802.1CB-2017Clause:9.1.2.1
Clause title:tsnCpeNullDownDestMac
Rationale for revision
This maintenance request is a fork of request 0311 to register the request against IEEE Std 802.1CB. The original rational is: 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
Add text to 9.1.2.1 that indicates a particular value for tsnCpeNullDownDestMac indicates a wildcard value. Consider using the value 0, but only if it would never otherwise naturally appear across the EISS. Alternatively, define a value of 'all' for the variable.
Impact on existing networks
Supporting the new wildcard value is optional. Backward compatibility can be retained in both aforementioned options.
Originator
Name:Paul CongdonEmail:paul.congdon@tallac.com
Affiliation:Huawei
Submitted:2021-08-12