PBB I-VPLS

• port level

  All existing Ethernet encapsulation types are supported (for example, null, dot1q, qinq).

• SAPs

  The following describes SAP support for PBB I-VPLS:

  • The I-VPLS SAPs can coexist on the same port with SAPs for other business services, for example, VLL, VPLS SAPs.

  • All existing Ethernet encapsulation are supported: null, dot1q, qinq.

• SDPs

  GRE and MPLS SDP are spoke-sdp only. Mesh SDPs can just be emulated by using the same split horizon group everywhere.

Existing SAP processing rules still apply for the I-VPLS case; the SAP encapsulation definition on Ethernet ingress ports defines which VLAN tags are used to determine the service that the packet belongs to:

• For null encapsulations defined on ingress, any VLAN tags are ignored and the packet goes to a default service for the SAP

• For dot1q encapsulations defined on ingress, only the first VLAN tag is considered.

• For qinq encapsulations defined on ingress, both VLAN tags are considered; wildcard support is for the inner VLAN tag.

• For dot1q/qinq encapsulations, traffic encapsulated with VLAN tags for which there is no definition is discarded.

• Any VLAN tag used for service selection on the I-SAP is stripped before the PBB encapsulation is added. Appropriate VLAN tags are added at the remote PBB PE when sending the packet out on the egress SAP.

I-VPLS services do not support the forwarding of PBB encapsulated frames received on SAPs or spoke SDPs through their associated B-VPLS service. PBB frames are identified based on the configured PBB Ethertype (0x88e7 by default).