It is important to understand that Active Destination MAC and VLAN Stream identification can identify a stream's frames with two methods:
1. An input frame can have a stream_handle assigned to it by 6.4, 6.5 or 6.7. If the output side stream_handle matches the stream_handle defined by the Active Destination MAC/VLAN managed objects we have a match. See Figure C-5 for an example of this.
2. If an input frame has a MAC/VLAN that matches those defined by the parameters in 9.1.2 (as part of the 9.1.2 + 9.1.4 set) we have a match. An example of this usage is a Listener proxy or shim that wants to replace the AVB related multicast MAC address with the Talker's original unicast MAC address; assuming a Talker proxy had already done the reverse unicast-to-multicast replacement to make it an AVB stream.
***FIRST PROPOSED CHANGE ***
Replace these two sentences in second paragraph of 6.6:
"The replacement values for frames transmitted down the stack to the ActiveDestination MAC and VLAN Stream identification, and used to recognize frames passed up the stack to the Active Destination MAC and VLAN Stream identification function, are those listed in 9.1.2. The replacement values for frames passed up the stack (not including the priority parameter) are in 9.1.4."
With these two sentences:
"The managed objects for Active Destination MAC and VLAN Stream identification for frames passed up the stack are described in 9.1.2. The replacement values for frames passed up or down the stack are described in 9.1.4."
I crafted the first sentence to more closely match similar single sentence paragraphs found in 6.4, 6.5 and 6.7.
Note that I also removed the "(not including the priority parameter)" text since 9.1.4.4 and 9.1.4.8 define the down and up replacement priority values.
***SECOND PROPOSED CHANGE ***
I also suggest reworking the first paragraph of 9.1.2 since that only references 6.4. However, 9.1.2 is also used by 6.6.
Replace the first paragraph in 9.1.2:
"When instantiating an instance of the Null Stream identification function (6.4) fora particular input Stream, the managed objects in the following subclauses serve as the tsnStreamIdParameters managed object (9.1.1.7)."
With this paragraph:
"When instantiating an instance of the Null Stream identification function (6.4), or the Active Destination MAC and VLAN Stream identification (6.6), for a particular input Stream, the managed objects in the following subclauses serve as the tsnStreamIdParameters managed object (9.1.1.7)."
However,realizing that when 9.1.2 is used with Active MAC/VLAN (6.6) that the objects defined in 9.1.2 are only a subset of the required objects (since 9.1.4 objects are also required), it may be better to leave the first paragraph as-is and insert a new second paragraph:
"When instantiating an instance of the Active Destination MAC and VLAN Stream identification function (6.6) for a particular input Stream, the managed objects in the following subclauses along with those described in 9.1.4, serve as the tsnStreamIdParameters managed object (9.1.1.7)."
***THIRD PROPOSED CHANGE ***
Table 9-1 (Stream identification types) associates the Stream identification functions with the Controlling parameters. The Active Destination MAC and VLAN Stream identification row references 9.1.4. It should also reference 9.1.2.
***FOURTH PROPOSED CHANGE ***
Table 6-1 (Stream identification functions) has a similar change for the Active Destination MAC and VLAN Stream identification row. Change the "6.6,9.1.4" reference to "6.6, 9.1.2, 9.1.4".
***FIFTH OPTIONAL PROPOSED CHANGE ***
Regarding Figure C-5. Note that the Active Destination MAC and VLAN Stream identification box is missing "(6.6)"; this is similar to the use of"(6.7)" in the IP Stream identification box to the left.
Add"(6.6)" to the box. Realize that this will make the box a bit taller.
The only reason I found this is I got tired of typing in the search term"Active Destination MAC and VLAN Stream identification" and started searching for 6.6; which missed Figure C-5.