IEEE
AMENDMENT 16: PROVIDER BRIDGING
—REMOTE CUSTOMER SERVICE INTERFACES Std 802.1Qbc-2011
Copyright © 2011 IEEE. All rights reserved.
7
12. Bridge management
12.13 Provider Bridge management
Change 12.13 as shown:
The conformance requirements of Provider Bridges are specified in 5.10. The S-VLAN component and the
externally accessible ports of all Provider Bridges, including Provider Edge Bridges, are managed using the
managed objects defined in 12.4 through 12.12. This subclause defines additional managed objects specific
to the operation of Provider Bridges.
The internal ports, LANs, and
C-VLAN components, and Port-mapping S-VLAN components of a Provider
Edge Bridge are not managed directly using the managed objects defined in 12.4 through 12.12. Their
operation is controlled and monitored through managed objects defined in this subclause.
Each externally accessible Bridge Port on a Provider Bridge is designated as a Provider Network Port,
Customer Network Port, or
Customer Edge Port, or Remote Customer Access Port. Designating a port as a
Customer Edge Port implies Provider Edge Bridge functionality and, specifically, the existence of a C-
VLAN component associated with that port. This C-VLAN component is uniquely identified within the
Bridge by the port number of the associated Customer Edge Port. The management of the forwarding
process, filtering data base, and C-VLANs of the C-VLAN component and the internal connections are
achieved through the Customer Edge Port Configuration managed object defined here (12.13.3).
Designating a port as a Remote Customer Access Port implies the existence of a Port-mapping S-VLAN
component associated with that port. The Port-mapping S-VLAN component is uniquely identified within
the Bridge by the port number of the associated Remote Customer Access Port. Designating an internal port
on the Port-mapping S-VLAN component as a C-Tagged RCSI implies a C-VLAN component with a
Customer Edge Port connected via an internal LAN to that internal port (Provider Access Port). This C-
VLAN component and internal connection are uniquely identified by the port number of the Remote
Customer Access Port and the S-VID associated with the Provider Access Port or by the port number of the
internal Customer Edge Port. Designating an internal port on the Port-mapping S-VLAN component as a
Port-based RCSI or a Provider Network Port implies an internal LAN connecting this port with a Customer
Network Port or Provider Network Port respectively. These ports and internal connections are uniquely
identified by the port number of the Remote Customer Access Port and the S-VID associated with the
Provider Access Port or by the port number of the Customer Network Port or Provider Network Port. The
management of the forwarding process, filtering data base, and S-VLANs of Port-mapping S-VLAN
components and their internal connections are achieved through the Remote Customer Access Port
Configuration managed object defined here (12.13.4).
An internal connection between a CNP on the S-VLAN component and a PEP on the C-VLAN component
is instantiated for each service instance. The CNP is identified by the CEP identifier and the S-VID value
used for the PVID of the CNP. The PEP is identified by the CEP identifier and the C-VID value used for the
PVID of the PEP. These PVID values and the connection between the CNP and PEP are established by
reciprocal entries in the C-VID Registration Table (12.13.3.2) and the Provider Edge Port Configuration
Table (12.13.3.4) as follows:
a) An entry in the C-VID Registration Table is created for each C-VLAN supported in the C-VLAN
component associated with a CEP. The CEP identifier and C-VID combination identify a PEP. The
entry contains (among other parameters) an S-VID value corresponding to the PVID of the CNP,
which associates the PEP with a specific CNP. Note that the CEP/C-VID combination identifies a
single PEP, however multiple CEP/C-VID combinations can identify the same PEP if the entries for
those CEP/C-VID combinations contain the same S-VID value. This many-to-one mapping of CEP/
C-VID to PEP permits "bundling", i.e. mapping multiple C-VLANs to the same service instance.
Authorized licensed use limited to: DUKE UNIVERSITY. Downloaded on May 04,2012 at 07:14:27 UTC from IEEE Xplore. Restrictions apply.