Requested revision
Standard: | IEEE Std 802.1Q-2022 | Clause: | 46.2.2 |
Clause title: | Protocol integration |
Rationale for revision
Triggered by Comment #1 on P802.1Qdj D1.0 IEEE Std 802.1Q-2022 states on page 1672: " Each TSN configuration protocol shall use the StreamID of this clause (46.2.3.1) as the unique identifier of each Stream’s configuration. The StreamID identifies configuration, not data, so it has no formal relation to the data frame encoding for the Stream. " This lacks consideration for protocols, which also use StreamID to identify data (e.g. 1722). It is unclear if the two must be mapped or can be chosen separately, as no entity will look at data and configuration, but just either or, except maybe a talker.
Proposed text
Change above section to read: Specify how protocols which carry the StreamID in their header structure must behave - must StreamIDs match between configuration and data-transport or can they be independent? The reporter would want them to be identical!
Impact on existing networks
Make the use of StreamID more consistent between data and config.
Originator
Name: | Max Turner | Email: | max.turner@ethernovia.com<mailto:max.turner@ethernovia.com> |
Affiliation: | Ethernovia | ||
Submitted: | 2023-01-18 |