Requested revision
| Standard: | 802.1Q-2011 | Clause: | 5.4.4, 5.16.3 |
| Clause title: | Multiple Stream Registration Protocol (MSRP) | ||
Rationale for revision
MSRPDUs are exchanged by using the "Individual LAN Scope group address,
Nearest Bridge group address", as stated in 35.2.2.1. The "Individual
LAN Scope group address, Nearest Bridge group address" is specified in
the tables 8-1, 8-2 and 8-3.
Clause 5.4.4 and 5.16.3 state, that MSRP uses "the group MAC addresses
reserved for use by MRP applications"/"the MSRP Application address"
specified in table 10-1. Table 10-1 specifies the "MRP application
addresses" for MMRP and MVRP, but not for MSRP. A separate "MSRP
Application address" does not exist.
Proposed text
Change (5.4.4)
"Exchange MRPDUs as required by those state machines, formatted in
accordance with the generic PDU format described in 10.8, and able to
carry application-specific information as defined in Clause 35, using
the group MAC addresses reserved for use by MRP applications, as defined
in Table 10-1."
to
"Exchange MRPDUs as required by those state machines, formatted in
accordance with the generic PDU format described in 10.8, and able to
carry application-specific information as defined in Clause 35, using
the "Individual LAN Scope group address, Nearest Bridge group address"
as defined in Table 8-1, Table 8-2 and Table 8-3 (C-VLAN, S-VLAN and
TPMR component Reserved addresses, respectively)."
Change (5.16.3)
"Exchange MPDUs as required by the MRP state machine(s) implemented,
formatted in accordance with the generic PDU format described in 10.8,
and able to carry application-specific information as defined in 35.2.2,
using the MSRP Application address as defined in Table 10-1."
to
"Exchange MPDUs as required by the MRP state machine(s) implemented,
formatted in accordance with the generic PDU format described in 10.8,
and able to carry application-specific information as defined in 35.2.2,
using the "Individual LAN Scope group address, Nearest Bridge group
address" as defined in Table 8-1, Table 8-2 and Table 8-3 (C-VLAN,
S-VLAN and TPMR component Reserved addresses, respectively)."
Impact on existing networks
As there is no seperate MSRP address in table 10-1 there should be no
impact on existing networks.
Originator
| Name: | Christian Boiger | Email: | christian.boiger@hdu-deggendorf.de |
| Affiliation: | Deggendorf University, Hirschmann Automation & | ||
| Submitted: | 2011-10-27 | ||