Requested revision
Standard: | IEEE Std 802.1Q, 2012 Edition | Clause: | 12.16.3, 12.16.5 (and MIBS) |
Clause title: | VIP configuration MO, CBP Configuration MO |
Rationale for revision
This item was triggered by looking into the T and R bits that
control multicast transmit and receive for BSI (I-SID) endpoints in SPBM.
At first it appeared these were driven from the Ingress and Egress bits
found in the management models (12.16.3.2.2:d and ieee8021PbbVipType for
VIP and 12.16.5.2.2:f and ieee8021PbbCBPServiceMappingType for CBP).
However, the 802.1aq editor indicated these (T/R and Ingress/Egress) are
different. That appears to be correct as the Ingress/Egress bits affect
all traffic and T/R are intended for multicast control (in SPBM).
There does not appear to be any management control for T/R bits in .1aq
(this is corrected in 802.1Qbp).
Further discussions indicated that the ingress/egress bits were at one
time included in the draft for PBB and later removed; however, they
appear to have remained in the managment model and MIB. Since there is
no mechnaism specified for ingress/egress controls in 6.10 or 6.11
these configuration objects should be removed or deprecated.
The MIB Textual Convention IEEE8021PbbIngressEgress is used for the
objects controlling the (unused) ingress/egress bits in the
IEEE8021-PBB-MIB; however, this TC has also been used in the
IEEE8021-SPB-MIB for read-only access to the T/R bits in the ISIS-SPB
topology database. Therefore, while the MIB objects for ingress/egress
should be deprecated, the TC should be kept to avoid disrupting the
SPB MIB. Some adjustment to MIB TC and object descriptions is needed
to clarify the situation.
Proposed text
Delete 12.16.3.1.3:f, 12.16.3.2.2:d, 12.16.5.1.3:f, and 12.16.5.2.2:f
In IEEE8021-PBB-MIB deprecate ieee8021PbbVipType and
ieee8021PbbCBPServiceMappingType and correct the Conformance sections,
if necessary.
Remove references to ieee8021PbbVipType in Clause 17
(Table 17-13, 17.4.8, 17.5.3.5.2, and 17.6.2.2.1)
Remove references to ieee8021PbbCBPServiceMappingType in Clause 17
(Table 17-13)
In Table 17-2 correct the references for IEEE8021PbbIngressEgress
In IEEE8021-TC-MIB change the description for IEEE8021PbbIngressEgress
from:
"A 2 bit selector which determines if frames on this VIP may
ingress to the PBBN but not egress the PBBN, egress to the
PBBN but not ingress the PBBN, or both ingress and egress
the PBBN."
to:
"A pair of {ingress, egress} flags for a Group Address
defining transmit, receive, or both at a node in an
SPB Region. When set, the ingress flag indicates that
frames with the Group Address will be transmitted from the
advertising node into the SPB Region. When set, the egress
flag indicates frames transmitted with the Group Address
must be delivered to the advertising node."
In IEEE-SPB-MIB change the description for
ieee8021SpbmTopSrvEntryIsidFlags from:
"A pair of flags defining the attributes of this
service. These specify independently whether
ingress frames to the SPBM region should be
transmitted within it, and whether frames
received from the SPBM region are required
egress it."
to:
"A pair of flags defining the transmit and receive
attributes for the I-SID Group Address of this
service. These specify independently whether the
advertising node will transmit I-SID group addressed
frames into the SPBM region, and whether I-SID group
addressed frames must be delivered to the advertising
node."
Impact on existing networks
Since there is no specification of any PIP or CBP behavior controlled
by the ingress/egress bits, removing these from the management model
should have no impact on existing networks. Changing descriptions in
the TC-MIB and SPB-MIB should not impact existing networks.
Originator
Name: | Ben Mack-Crane | Email: | ben.mackcrane@huawei.com |
Affiliation: | Huawei | ||
Submitted: | 2013-05-03 |