Ieee 802.1Ah Use Case; Egress Fc-Based Remarking; Figure 10: De Aware Pbb Topology - Alcatel-Lucent 7950 Quality Of Service Manual

IEEE 802.1ah Use Case

Figure 10
processing needs highlighted in the 802.1ad use case apply to the 802.1ah BVID, format and etype
being identical with the 802.1ad STAG. In addition the DE bit from the 802.1ah ITAG header may
need to be processed following the same rules as for the related field in the BVID/STAG: for
example, the DE bit from the BVID header represents the QoS associated with the "Ethernet
Tunnel" while the DE bit from the ITAG represent the service QoS.
CE UNI
PBB PE
In this example, the BVID is not used for a part of the network leaving only I-DEI bit from the
ITAG as the only option for a dedicated DE field. If both are included, then the QoS information
from the BVID is to be used.

Egress FC-Based Remarking

FC-based forwarding can be used in a network using core markings of dot1p and may not support
DE in all devices. The expectation is that devices beyond the network edge will continue to adhere
to the end-to-end QoS policies using dot1p in the packet. Dot1p marking is performed on egress
for all services and with respect to in-profile or out-of-profile context.
The following commands can be used to remark the dot1p values at a SAP egress:
CLI Syntax: sap-egress <policy-id> create
7950 XRS Quality of Service Guide
illustrates an example of a PBB topology where the DE feature can be used. The
PBBN
(CE aware using
B-SAP
802.1 a/b/d &/or
802.1afITAG)

Figure 10: DE Aware PBB Topology

fc <fc-name> create
profile <dot1p-value>}
<dot1p-value>
Service Egress and Ingress QoS Policies
7x50 PE1
MPLS
B-VPLS SDP
dot1p {<dot1p-value>|in-profile <dot1p-value> out-
dot1p-inner <dot1p-value>
dot1p-inner in-profile <dot1p-value> out-profile
dot1p-outer <dot1p-value>
dot1p-outer in-profile <dot1p-value> out-profile
7x50 PE2
MPLS
SDP B-VPLS I-SAP
Page 137
CE